Communication and Meetings
Items to be discussed in meetings should be tagged with the Meeting tag. While preparing the agenda, review the issue board for items that should be tagged for the meeting. At least a day or two prior to the meeting, the chair should post a thread with the agenda on the forums. Team members may suggest additional topics in these threads.
Follow this general script for the meeting.
#topic Roll call
Wait 3–5 minutes to see who is present.
|In case you need to step away or get disconnected, add other chairs (e.g. board members) with: #chair <NICK>
List the agenda for the meeting:
#info Review action items
#info <topic 1>
#info <topic 2>
Start with any important announcements. (e.g. Release Notes that need to be written, upcoming deadlines, a link to the issue board, etc.)
Next, review action items from previous meetings.
Get updates when there are updates to get.
If an action item is still open,
#action command to assign it again.
This keeps chairs from having to search many previous meetings.
#topic Previous action items
#info <nick> was to <action>
Proceed through the other agenda topics.
#topic to change the topic.
Make frequent use of
#link commands to add context to the minutes.
If someone needs to act,
#action <nick> to <action> to note it in the minutes.
Note agreements with the
|Most of the time, something that is #agreed should be recorded elsewhere after the meeting. For example, in the resolution of a ticket or as a new policy/procedure in the documentation.
|Should we add a regular content-related topic? Peter Boy suggested this.
If time permits, open the floor for other discussion.
#topic Open floor
|Do not make decisions in the open floor section. Decisions should, at a minimum, be made after appearing on the meeting agenda in advance. In most cases, decisions should happen asynchronously.
When time is up or there are no more topics to discuss, end the meeting.
Paste the links to the minutes and logs in the Discussion thread you used for the agenda. Note any important outcomes. Update tickets or discussion threads with actions, agreements, etc.
Want to help? Learn how to contribute to Fedora Docs ›