Docs team meetings
Items to be discussed in meetings should be tagged with the meeting tag in the docs-fp-o repository. 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.
|The above is temporary. We hope to move to using a GitLab dashboard soon.|
Follow this general script for the meeting.
#startmeeting docs #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 with: #chair <NICK>|
List the agenda for the meeting:
#topic Agenda #info Review action items #info <topic 1> #info <topic 2> #info …
Start with a review of 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.