Fedora Council Charter
The Fedora Council is our top-level community leadership and governance body. It is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora Community.
The Council is composed of a mix of representatives from different areas of the project, named roles appointed by Red Hat, and a variable number of seats connected to medium-term project goals. Decisions are made by a consensus process, in which we work together as a common team to find shared solutions and address concerns, with a focus on giving voice rather than on balance of power.
The Council is ultimately accountable for the Fedora Project as a whole, and is responsible for providing advice to and oversight of other Fedora governance bodies and teams as needed.
The Council is responsible for issues of strategic importance for Fedora that require leadership and coordination across the various teams and subprojects to achieve.
Its primary role is to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them. This is done in consultation with the entire Fedora community through transparent, public discussion.
The Council governs Fedora’s financial resources, working with our sponsor(s) to establish an annual budget allocated to support Fedora initiatives, including Fedora Ambassadors, Fedora-managed events, and other activities which advance the project’s goals.
The Council also decides on issues regarding use of the Fedora trademarks, is responsible for final arbitration of complaints related to project policies and for settling disputes escalated from other committees or subgroups, and may handle sensitive legal or personnel issues which require research and discussion to protect the interests of the Fedora Project or its sponsor(s).
Many basic decisions are made through a process known as “lazy approval”, in which general consent is assumed unless valid objections are raised within a period of time — generally three to seven days, although the timeframe should be stated each time and should be proportionate to the impact of the action. This process is used for decisions with short-term consequences and which can be easily reversed. Any project member can ask for the deadline to be extended or the decision escalated to require full consensus.
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.
On an ongoing basis, including sessions at Flock and in public online meetings, the Council will identify two to four key Community Initiatives with a timeframe of approximately eighteen months, and appoint Community Initiative Leads for each goal. These will serve as Council members.
Each Community Initiative will be documented with measurable goals, and the Community Initiative 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 five representative seats, an Engineering Representative, a Mindshare Representative, a DEI Advisor 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 Fedora Engineering Steering Committee (FESCo) and the Mindshare Committee, respectively.
The Fedora Diversity, Equity, & Inclusion (DEI) Advisor is a liaison between the Fedora Council and the Fedora community on topics and issues related to diversity, equity, and inclusion in Fedora. The DEI Advisor works with Fedora Council leadership to represent perspectives and voices of the Fedora community in decision-making and project discussions. Additionally, they also lead initiatives to assess and promote equity and inclusion in collaboration with the Fedora DEI Team.
This position is appointed by members of the Fedora DEI Team, with the approval of the Council.
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.
Fedora Project Leader
The 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 Architect
The Fedora Community Architect (FCA) works 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.
Fedora Program Manager
The FPgM coordinates the planning and scheduling of Fedora releases, and tracks changes and features during the development and testing cycle. He or she also assists with the creation, maintenance, and execution of formal, repeatable Fedora processes. Additionally, the FPgM serves as record keeper and secretary for Fedora Council Meetings.
This position is funded by and hired for by Red Hat, with the approval of the Council.
The Fedora Council is not driven by meetings or by tickets, but does hold regular public meetings (via a chat system or video call). The Council discusses current issues, clear through anything outstanding which can be quickly resolved, and to ensure that nothing urgent is left pending. All members are expected to regularly communicate what is going on in their area, through blog posts or other public updates.
The Council holds a multi-day, face-to-face meeting annually. All members should strive to attend in person (travel funding is available). We also often meet for a day before or after other significant Fedora-related conferences (Flock, DevConf.cz). These meetings are not public, but minutes and summary documents will be provided.
Additionally, the Fedora Project Leader will set aside regular times to meet with the community. Attendance is not mandatory for all Council members but is encouraged.
The general policy of the Fedora Council is to default to open. Most meetings are held in public channels, and open to all Fedora users and contributors. Discussion is held in a public forum open to all, and formal decisions will be recorded in a public ticket tracking system.
Occasionally, when personal, private, or sensitive issues need to be discussed, a video call might be used. A private mailing list and ticket tracking instance also exist for these situations, but will also only be used when dealing with these uncommon issues.
Serving on the Fedora Council is a significant commitment of time and energy. Workload for the various roles will vary, but each will require a number of hours every week, and in most cases, the more, the better a Council member is able to do the job fully.
We recognize that most Fedora community members do not have the luxury of working on Fedora full-time or as part of a paid position. The time commitment required for these roles comes simply from what is required to lead a large project like Fedora, and is not intended to be an artificial limit on who can participate. We know that that it can be a pragmatic limit, and for that reason, the Council is responsible for extra effort to receive, recognize, be responsive to, and meaningfully reward the input of contributors offering their individual time.
To advance free software, we need to provide a sustainable integration of free software without cutting corners. By providing a positive first impression before and during installation and real use, we support Fedora’s reputation as a leading and reliable product that attracts future users and contributors. To provide that integration and experience we must have a clear set of priorities to help all contributors decide how to allocate resources and resolve conflicts. These priorities are not meant to be exclusive, or to keep contributors from working on the parts of Fedora that matter to them.
These priorities will sometimes expose gaps where contributors need additional assistance, and allow them to seek it both within the community and by bringing in additional contributors to help, exclusively on their particular interest area if desired. While narrowing our focus in some areas, though, we must provide opportunities for exploration to all contributors within the framework of our core values and without impeding progress.
The previous previous governance structure (Fedora Board) had five members directly appointed by Red Hat and five elected at large. The current structure is more complicated but has a much greater proportion of members selected by the community by election or merit. In the previous board structure, the Fedora Project leader had a special veto power; in the current model, all voting members can block on issues, with a valid reason. The FPL does not have a special veto, but does have a limited power to “unstick” things if consensus genuinely can’t be reached and a decision needs to be made.
Former membership on the Fedora Council, along with membership on the previous Fedora Board, is documented on the History of Council Membership page.
This charter was approved by the Fedora Project Board on Oct. 9th, 2014 and is in effect as of Nov. 26th, 2014. Any other significant changes will be noted here; smaller changes (minor wording or formating, etc., without impact on meaning) can be found in the git repository for Council documents.
2023-05-04: Rename Fedora Community Action and Impact Coordinator to Fedora Community Architect
2023-04-28: Equalize the auxiliary positions based on ticket #447
2023-02-07: Change name of Objectives to Community Initiatives. See Community Initiatives History & Future.
2023-02-02: Update Diversity & Inclusion Team Representative to DEI Advisor, remove auxiliary status and designate as a full voting member.
2017-11-15: Update Diversity Advisor to Diversity & Inclusion Team Representative
2017-10-20: Move current membership list and contact info to separate docs.
2017-04-05: Switched “Outreach” to Mindshare. (ticket)
2014-11-26: Initital approval by the Fedora Project Board (ticket)
Want to help? Learn how to contribute to Fedora Docs ›