(meeting SOP draft page) |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
This is an outline of the process used by the BugZappers to create the agenda, administrate and document the weekly meetings. | This is an outline of the process used by the BugZappers to create the agenda, administrate and document the weekly meetings. | ||
== Agenda == | == Meeting Agenda == | ||
The agenda is sent out the | The meeting agenda is sent out on the [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list] mailing list 12 to 24 hours before the scheduled meetings. | ||
The subject line of the | The subject line of the email should read: BugZappers Meeting Agenda for <year>-<month>-<day> | ||
And | And 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. | ||
| Line 21: | Line 24: | ||
Items for the meeting agenda are gathered from four sources, | Items for the meeting agenda are gathered from four sources, | ||
# Minutes from the last meeting. | # Minutes from the [[BugZappers/Meetings | last meeting]]. | ||
# The meeting agenda list at [[BugZappers:meeting-agenda-list | meeting-agenda-list]]. | |||
# The meeting agenda list at | # The Triage Tracs instance at [https://fedorahosted.org/triage/ https://fedorahosted.org/triage/]. | ||
# Members of the project via the [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-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. | and added to the agenda as topics for discussion during the meeting. | ||
== Meeting Administration == | |||
To be added. | |||
== Meeting Documentation == | |||
== Meeting | |||
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 | Once the meeting is complete (up to 24 hours after), an email recapping the meeting minutes is sent to [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list], and a link is created on the [[BugZappers/Meetings | BugZappers meeting wiki page]] linking to the meetbot log of the meeting minutes. | ||
Latest revision as of 06:31, 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.
Meeting Agenda
The meeting agenda is sent out on the fedora-test-list mailing list 12 to 24 hours before the scheduled meetings.
The subject line of the email should read: BugZappers Meeting Agenda for <year>-<month>-<day>
And 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 Administration
To be added.
Meeting 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 meetbot log of the meeting minutes.