Interviews for the Fedora elections.
This repository supports the interview process for candidates running in Fedora's regular elections. When a candidate self-nominates for an elected position, they answer a set of interview questions by filing a private issue in this repository. The election wrangler(s) then process, review, and schedule the interviews for publication on the Fedora Community Blog before the voting period begins.
The Fedora Operations Architect is the primary election wrangler. The Fedora Community Architect (FCA) serves as the backup. Transparency and strict adherence to the published process are essential — the elections process is central to Fedora's community governance model.
Fedora conducts regular elections for the following governing bodies:
Elections for FESCo occur after each Fedora Linux release. Council, Mindshare, and EPEL elections occur once per year. Other teams may request elections at any time.
Nominations open according to the election schedule for each Fedora Linux release cycle. The nomination period and question selection period run concurrently. Each elected body's nomination wiki page is updated, and announcements are sent to mailing lists and Fedora Discussion.
Questions are finalized with each committee. If a committee does not provide updated questions by the deadline, the previous cycle's questions are reused. The top three questions for each body are selected based on Council decision #156. The finalized questions are stored as issue templates in this repository.
Candidates submit interviews as private issues using the appropriate template. Only the election wrangler(s) can see the responses before publication.
The election wrangler processes each submission:
- Acknowledges the candidate's submission in the ticket
- Verifies the candidate has a Community Blog account (adds login needed tag if not)
- Tags the issue with interview and assigns the release milestone
- Links the issue to the relevant election tracking issue via the "Blocking" field
- Creates a Community Blog post with the interview content and schedules it for publication
Interviews are published on the Community Blog at staggered times before voting opens: - Council interviews: 15 minutes before the voting period - FESCo interviews: 10 minutes before the voting period - Mindshare interviews: 5 minutes before the voting period
Candidates review a public preview of their blog post before it goes live.
Candidates who do not submit an interview by the deadline are excluded from the ballot, per Fedora Council decision #135.
This repository provides issue templates for each elected body:
| Template | Body |
|---|---|
Council-Election.md |
Fedora Council |
FESCo-Election.md |
Fedora Engineering Steering Committee |
Mindshare-Election.md |
Mindshare Committee |
EPEL-Election.md |
EPEL Steering Committee |
Each template instructs candidates to mark their issue as private before submitting, and lists the interview questions for that cycle. Questions are reviewed and may be updated each election cycle in coordination with the respective committee.
The Interviews board tracks each interview through the processing pipeline:
| Column | Description |
|---|---|
| Submitted | Candidate has filed a private issue with their responses |
| Processing | Election wrangler is creating the Community Blog post |
| Ready for Review | Blog post is drafted; candidate has been notified to review the preview |
| Queued-Published | Interview is scheduled or published; issue is closed |
The following public issues illustrate how this repository is used:
Individual interview submissions are private issues visible only to the election wrangler(s).
Each Fedora release cycle that includes elections has a corresponding milestone (e.g., F35, F36, F42).
Milestones group all interview and tracking issues for a given cycle.
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »
© Red Hat, Inc. and others.