QA:SOP Matrix meeting process: Difference between revisions

Revision as of 11:42, 18 July 2011

This guide explains how to manage and run a Fedora QA IRC meeting. Many of the steps here could well apply to other groups that hold regular IRC meetings as well. In fact, this page was initially borrowed from FESCo_meeting_process.

Pre-meeting

One or more days before the meeting is scheduled ...

Create a wiki page to allow for collaborative edits of the proposed meeting agenda. This page must be linked from QA/Meetings. The page name typically follows the format QA/Meetings/20240426. Use the content format ...

# Fedora Quality Assurance Meeting
# Date: 2024-04-26
# Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

This is a reminder of the upcoming QA meeting.  Please add any topic suggestions to
meeting wiki page at
https://fedoraproject.org/wiki/QA/Meetings/20240426.

The current proposed agenda is include below.  If no additional topics are suggested, 
the meeting will be canceled.

== Proposed Agenda Topics ==
 1. Previous meeting follow-up

... <any active meeting topics> ...

 2. Open Discussion - <your topic here>

Using the above template, send an email to the test@lists.fedoraproject.org

Day of meeting

Double check the meeting agenda drafted earlier. Ideally, additional topics have been posted, some wiki formatting may be required prior to the meeting.

No topics, no meeting
If no meeting topics were suggested prior to the meeting, and there is no important business to discuss, it is acceptable to cancel the meeting. If the meeting is canceled, please follow-up to the proposed agenda email noting that the meeting has been canceled. Please notify participants as early as possible, preferably a day in advance, if a meeting will be canceled. After canceling a meeting, update the meeting calendar with a link to the exact cancellation email.
Send out a reminder IRC message ~20 minutes before the meeting to the following IRC channels: #fedora-qa, #fedora-test-day, #fedora-bugzappers and #fedora-devel

Meeting time

Okay it's time to get down to business. The following steps guide you through hosting the meeting.

Join #fedora-meetingon irc.freenode.net...
```
/join #fedora-meeting
```

Start the meeting...

#startmeeting Fedora QA meeting
#meetingname fedora-qa

Ask participants to say hello by taking a roll call...
```
#topic Roll Call
```
For each of the proposed agenda topics, set the topic using the #topic command. For each topic, make liberal use of meetbot commands to record information. Refer to Zodbot#Meeting_Functions for a list of commands.
Remind participants about the next scheduled meeting time (typically the same time the following week, refer to QA/Meetings). Also, use this as an opportunity to ask who would like to #chair the next meeting...
```
#topic Next meeting
#info Friday, April 26 2024
#info FOO has agreed to #chair the next meeting 
```
After discussing all proposed topics, open up the meeting for additional discussion...
```
#topic Open Discussion - <your topic here>
```
Thank participants for their time, and close out the meeting...
```
#endmeeting
```

Post meeting

When the meetbot #endmeeting command completes, it displays links for the logs. Include the .txt file in the email created above.

Minutes:        http://meetbot.fedoraproject.org/fedora-meeting/2024-04-26/fedora-qa.2024-04-26-13.00.html
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2024-04-26/fedora-qa.2024-04-26-13.00.txt
Log:            http://meetbot.fedoraproject.org/fedora-meeting/2024-04-26/fedora-qa.2024-04-26-13.00.log.html

Send the meeting minutes email immediately following the meeting. The longer one waits to send the minutes, the easier it is to forget. A sample meeting recap is available for reference.
Update the QA Meeting calendar page to include a link to the meeting minutes. This is very helpful for maintaining a search-able history of meeting minutes.

Search