|The elections process for the Fedora 35 cycle has begun. See the schedule below for key dates.|
Fedora has several elected bodies that regularly conduct elections every release cycle. In addition, Fedora teams can request one-off elections from the Fedora Program Manager when trying to select new leadership or otherwise reach a decision through a formal voting process.
From the set of collected questions for nominees to FESCo (Engineering), Fedora Council, and Mindshare|Mindshare teams, top 3 questions are selected, based on Council decision. The selected questions will be given to each candidate to answer before the voting period begins as part of campaign.
The top selected questions for each body are put in teamplates in the elections-interviews repo (
During this period people may self-nominate to open seats. If they wish to nominate someone else, please consult with that person ahead of time.
Nominees are requested to answer the selected questions using a private issue in Pagure. In this way, only the Program Manager and Fedora Action and Impact Coordinator (as election wrangler substitute) are allowed to see these answers.
It is the responsibility of the Program Manager to validate the eligibility of nominees for elections. In compliance with Fedora Council decision #135, nominees not having completed their interviews (as aprivate issue in Pagure]) are excluded from the list of nominees.
The Fedora Elections Guide has information on the voting method used in the Fedora elections and detailed instructions on how to cast your vote.
If you are familiar with the voting process, you may go straight to the elections application to cast your votes.
Eligible Voters Voting eligibility is determined by a community member’s Fedora Account System (FAS) memberships.
See the Elections archive for historical results.