From Fedora Project Wiki
No edit summary
 
(One intermediate revision 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 to fedora-test-list 12 to 24 hours before the scheduled meetings.  
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 agenda email should read: BugZappers Meeting Agenda for <year>-<month>-<day>
The subject line of the email should read: BugZappers Meeting Agenda for <year>-<month>-<day>


And needs to contain the following information:
And contain the following information:
Location, day, date and time
Location, day, date and time
example


Bug Triage Meeting
<pre>
irc.freenode.net #fedora-meeting
example
Tuesday 29 September 15:00 UTC (11 AM EST)
---
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 28: Line 31:
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 ==
== Meeting Administration ==


To be added.
To be added.


== Documentation ==
== 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 fedora-meetbot log of the meeting minutes.
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.
 
 
https://fedoraproject.org/wiki/BugZappers/Meetings

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,

  1. Minutes from the last meeting.
  2. The meeting agenda list at meeting-agenda-list.
  3. The Triage Tracs instance at https://fedorahosted.org/triage/.
  4. 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.