While Aoife Moloney is out of office until May 18, 2026, the roles and duties of Council secretary, including chairing Fedora Council meetings, will be led by Justin Wheeler, the Fedora Community Architect. See Fedora Operation Architect docs page for more information.
The Fedora Council holds meetings every other week. They're held in the #meeting:fedoraproject.org room on Matrix (e.g. chat.fedoraproject.org). These meetings have two components:
- Tickets and Ongoing: Where the Fedora Operations Architect goes through crucial open tickets to make sure timely topics get attention
- Open Floor: Where the agenda is set by Council members in attendance at the beginning of the meeting
You can see our upcoming meeting schedule in Fedocal.
Council Meeting Process
This guide explains how to manage and run a Council Matrix meeting. Many of the steps here could well apply to other groups that hold regular Matrix meetings as well.
Pre-meeting
Update the Next Meeting Agenda section below at least 48 hours before the meeting by:
1. Going through open tickets and selecting several that seem timely or otherwise worth real-time discussion.This is also a good time to poke forward any issues that don't really need to be at the meeting but need further action, or to close issues that are resolved — or which won't be resolved. We want to keep the open tickets reflective of actual work in progress, not merely things we hope to get to someday. (Ticket system or not, there's an infinite pool of potential work for the Council, and keeping open tickets which we have no practical plan to work on is a recipe for sadness all around.)
2. Consider other topics that might benefit from real-time discussion in order to move forward. Again, we don't want to block issues on waiting for "everyone in the room" conversations (when we have mailing lists and lazy consensus), but we've found that regular discussion is important.
3. Request input from other council members by linking this page in the #council room on matrix
When this is complete:
1. Post the agenda to the Council Workspace on discussion.
Use the following template:
Here’s the agenda for the Council meeting June 18, 2025 3:00 PM→ 4:00 PM (Dublin): 2025-06-18 Topics * Your item here * Your item here * Any other business All are welcome to join us in #meeting:fedoraproject.org
2. An automated calendar reminder message should be sent to council-members [at] fedoraproject [dot] org the day before the meeting with a link to the meeting wiki page and agenda posting on discussion.fedoraproject.org.
During the Meeting
You can copy and paste in lines from this template as the meeting proceeds. You may find it helpful to copy this to a file in advance, so you can pre-fill the topic lines.
!startmeeting Fedora Council (2026-02-18) !meetingname council !group members council !topic Intros, welcomes, hellos !info Welcome to another Fedora Council meeting! If you are present and intend to follow along with today's meeting, please identify yourself by typing `!hi` in the chat. Council members in attendance will have their attendance noted before moving to the agenda. !info Council members present: @fasuser1, @fasuser2, … !topic Meeting Agenda !link https://fedoraproject.org/wiki/Council_Meetings#Next_Meeting_Agenda !topic #XYZ: ticket title !link https://pagure.io/Fedora-Council/tickets/issue/XYZ !topic Open Floor !endmeeting
1. Use the 'Intros, welcomes, hellos' topic to start the meeting.
2. Allow 3-5 minutes for a majority of the Council to show up.
3. Set the agenda — include the tickets from the FOA, and then use the open floor meeting agenda process:
- Ask for topics
- Gauge popularity, sort topics
- Ask if everyone is okay with the sorted list
4. We've found that our meetings and discussions are small and informal enough that we don't need special etiquette markers (like ! to ask for permission to talk). If we ever do have a particularly contentious and popular topic, we may introduce rules like that temporarily — but, usually, it is not necessary.
5. Keep an eye on the clock — if a topic is using more than the expected time, sometimes that's okay, and other times it is best to ask that discussion continue in tickets and on the mailing list and move on.
6. Make liberal use of Zodbot commands like !info, !link, !action, !idea and !agreed, to populate the meeting minutes.
Post-meeting
1. The meeting minutes are automatically collected in Meetbot Logs. Share these links and a meeting summary after the meeting discussion agenda post.
2. Process through tickets by commenting on outcomes from the meeting, link the minutes and close them as appropriate.
3. If you have any action items you can handle quickly, now is really a good time for it. Otherwise, don't forget to add these to your personal todo list.
Next Meeting Agenda
This section is a rolling section updated regularly with the next Fedora Council meeting agenda. Any Fedora Council member may add topics below. However, make sure the Fedora Operations Architect is informed about any changes made to the agenda in advance of the meeting.
2026-02-25 Meeting Agenda
This is a special Video Meeting to present the outcomes and key takeaways from the 2026 Strategy Summit from 3-5 February 2026.
- Ticket #555: Council Strategy Summit 2026 – 2-6 February 2026 – Tirana, Albania
- Jef Spaleta: Presentation on outcomes and key takeaways from Strategy Summit
- Justin Wheeler: Preview of the Miro board from the Strategy Summit
- Open Floor & Q&A
