English Persian
More significant decisions are made through a process of *full consensus*. In order to pass, these decisions need three positive votes (+3) and _no_ negative votes (-1). A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concerns about the proposal, and suggestions for what could be changed in order to make the proposal acceptable. A vote of “0” is sometimes used to indicate a disagreement but willingness to stand aside; this should also be accompanied with an explanation.
This model matches Fedora's “Friends” foundation, which calls for finding acceptable consensus to serve the interests of advancing free software. It works because we work together in a community of mutual respect even when we disagree.
In general, the Council conducts business in public discussion, and any Fedora project member can make negative or positive votes. It is the duty of the Council to take concerns raised in this way into serious consideration, but only Council members' votes are binding in the final tally.
When consensus can't be reached, the Council may ask the Fedora Project Leader to decide on a resolution. Such a request can be made when issues leading to negative votes are outstanding and all Council members agree that the Council is deadlocked, or if the dispute is unresolved after fourteen days and a simple majority of Council members are in favor of the request.
Objective Leads
On an ongoing basis, including sessions at Flock and in public online meetings, the Council will identify two to four key https://docs.fedoraproject.org/en-US/project/objectives/[community objectives] with a timeframe of approximately eighteen months, and appoint *Objective Leads* for each goal. These will serve as auxiliary Council members, with binding votes only over concerns relevant to their particular area.
Each objective will be documented with measurable goals, and the objective lead is responsible for coordinating efforts to reach those goals, evaluating and reporting on progress, and working regularly with all relevant groups in Fedora to ensure that progress is made.
The Council also includes four representative seats, an *Engineering Representative*, a *Mindshare Representative*, and two *Elected Representatives*.
“Engineering” and “Mindshare” are broad areas roughly encompassing two of the major areas of activity in Fedora. _Engineering_ is the technical work related to building and releasing the Fedora operating system and the infrastructure related to that. _Mindshare_ includes marketing, design, and Fedora Ambassadors — largely activities that happen between Fedora and the world at large, with the distribution release cycle serving as a fuel source, not the thing that's being worked on.
The engineering and mindshare representatives' responsibility is to represent their areas collectively, _not_ to be just an individual voice that happens to be voted-in by some subset of Fedora. They are selected by contributors working in those areas, under the rules of the xref:fesco::Fedora_Council_Engineering_Rep.adoc[Fedora Engineering Steering Committee (FESCo)] and the xref:mindshare-committee::procedures/council_rep.adoc[Mindshare Committee], respectively.
The elected positions cover all Fedora subprojects that are not under the engineering or mindshare banners, and the community at large. One specific responsibility is to represent the voice of individual contributors to the Fedora project. Each representative will also work on specific goals which she or he brings to the Council as highlighted during the election process.
Elections are held twice a year, in concert with the joint Fedora election cycle. One seat is selected at each election, and each position has a two-election (approximately one year) term. No person who currently holds another Council seat can be elected. If a seat becomes vacant, the Council will arrange for a temporary replacement.
Appointed Leadership Positions
*Fedora Project Leader*
The xref:fpl.adoc[Fedora Project Leader] serves as the chair of the Council, organizing discussion agendas, bringing issues to the table, and facilitating the consensus process. He or she is accountable for success in all areas of the project, but is not a dictator, benevolent or otherwise. The FPL often serves as the public face and collective voice of the project, and has a corresponding duty to listen to, understand, and fairly represent the collective views and needs of project contributors and stakeholders.
The Fedora Project Leader is hired by Red Hat with the advice and consent of the Council.
*Fedora Community Action and Impact Coordinator*
The xref:fcaic.adoc[Fedora Community Action and Impact Coordinator (FCAIC)] initiatives to grow the Fedora user and developer communities, and to make Red Hat / Fedora interactions even more transparent and positive. The Fedora community budget comes to us through the Red Hat Open Source Program Office, and this position facilitates decision-making on how to best focus that to meet our collective objectives.