The Fedora Program Manager is responsible for conducting elections for various bodies within Fedora. After each release, the Fedora Council, Mindshare Committee, and Fedora Engineering Steering Committee run elections. Other teams may request elections if they have a need.

The Fedora Community Action and Impact Coordinator (FCAIC) is the backup elections wranger. The FCAIC & FPgM cannot be candidates for elected positions.

FESCo has a separate election policy that requires more candidates than open seats.


The wiki-based voting process is a giant pain. Perhaps you would like to extend the voting app to allow nomination and election interviews.
  • Make sure an "I Voted" badge has been created for this election cycle.

  • Edit the Elections docs page

  • Open a ticket with each group to see if they want to change the questions

    • Update the templates/* files in the repo (ssh://git@pagure.io/tickets/fedora-project-schedule.git) with the new questions

  • Update wiki pages for each election: update the leaving members and clear the candidates

  • Open the nominations by announcing to the mailing lists

  • Candidates will post interviews in private issues on the poorly-named fedora-project-schedule repo.

  • Convert interviews to community blog

    • One post per-candidate

    • Include FAS acocunt, IRC, wiki page (see previous examples)

    • Set the candidate as the author

  • Write a wrap-up post (look at 2017 elections interview as example). link to interview post and user wiki

Get the FCAIC to review posts to make sure nothing is misspelled or mis-copied, etc.
At one time, we were hoping to have the Fedora Podcast conduct interviews with candidates as well, but that has fizzled.
A long time ago, we conducted IRC town halls with candidates. We stopped doing that.

Voting setup

The elections app runs on elections.fedoraproject.org.

  • maximum range: # of candidates

  • URL: link to wiki page with nominations

  • Admin groups: automatically includes the elections group

  • When adding users, add link to interview on commblog

The “Candidates are FAS users?” validation check is buggy, don’t use it. Ben Cotton hopes to have this fixed before the Fedora 32 elections.
The logic to enforce FESCo’s CLA+1 requirement is too strict. Council and Mindshare do not have that requirement. Ben Cotton hopes to have this fixed before Fedora 32 elections.

After elections

  1. Post the results to the Community Blog

  2. Send results with a link to the Community Blog to the announce mailing list

  3. Send individual election results to the council-discuss, devel-announce, and mindshare mailing lists

  4. Update Pagure groups, wiki pages, mailing lists as described below


FESCo (Engineering)


Convincing teams to give you admin access to things will make life easier. Also, if I document these things better, that would make life easier, too. Maybe for Fedora 31.