(→Agenda) |
|||
| Line 11: | Line 11: | ||
And needs to contain the following information: | And needs to contain the following information: | ||
Location, day, date and time | Location, day, date and time | ||
<pre> | |||
example | |||
--- | |||
Bug Triage Meeting | |||
irc.freenode.net #fedora-meeting | |||
Tuesday 22 September 15:00 UTC (11 AM EST) | |||
</pre> | |||
As well as the items to be covered in the meeting and any special notices or announcements. | As well as the items to be covered in the meeting and any special notices or announcements. | ||
Revision as of 06:23, 29 September 2009
BugZapper Meeting SOP
This is an outline of the process used by the BugZappers to create the agenda, administrate and document the weekly meetings.
Agenda
The agenda is sent out the to fedora-test-list 12 to 24 hours before the scheduled meetings.
The subject line of the agenda email should read: BugZappers Meeting Agenda for <year>-<month>-<day>
And needs to contain the following information: Location, day, date and time
example --- Bug Triage Meeting irc.freenode.net #fedora-meeting Tuesday 22 September 15:00 UTC (11 AM EST)
As well as the items to be covered in the meeting and any special notices or announcements.
Items for the meeting agenda are gathered from four sources,
- Minutes from the last meeting.
- The meeting agenda list at meeting-agenda-list.
- The Triage Tracs instance at https://fedorahosted.org/triage/.
- Members of the project via the fedora-test-list.
and added to the agenda as topics for discussion during the meeting.
Meeting
To be added.
Documentation
Once the meeting is complete (up to 24 hours after), an email recapping the meeting minutes is sent to fedora-test-list, and a link is created on the BugZappers meeting wiki page linking to the fedora-meetbot log of the meeting minutes.