Contents

Meeting Schedule

In addition to the email lists on which the Board will conduct its business, there will conference calls at least twice per month. The Board endeavors to hold a public meeting twice a month; right now they are held via IRC .

Board meetings are typically at 2 PM ET on Mondays. IRC meetings are typically on Fridays at 2 PM ET.

Secretary HOWTO for Phone Meetings

Take Meeting Minutes:

The Fedora Project Leader will send connection details for both the phone and Gobby sessions for the meeting at least a couple of hours before the meeting. Using these details, log into the Gobby session 5-10 minutes before the meeting start time.

Make sure zodbot is present in the channel, and when it is time to start the meeting, type #startmeeting into the channel to start logging.

Use the #topic command to set the first topic for discussion.

For example, #topic New Fedora T-Shirts will set the topic to 'New Fedora T-Shirts' in both the channel and in the IRC log.

As the meeting runs:

Maintain A Speaking Queue

Keep a Gnote or other text editor window open to maintain a speaking queue.

If someone types ? into the channel, add them to the end of the queue in the order in which the ? was typed. Note they have a question.

If someone types ! into the channel, also add them to the end of the speaking queue. Note they have a statement.

When it is a speaker's turn to talk, allow them to talk and wait for them to type eof. When they type eof, remove their name from the top of the queue and call on the next person in the speaking queue.

Log proposals

Make sure that whenever anyone presents a proposal to the board that it is logged using the #idea tag.

For example, #idea Fedora should do x

When a proposal is seconded, set the proposal as the topic using #topic and open the queue to discussion of that proposal.

Keep the topic updates

When it's time to change topics please note the topic the meeting is changing to with the #topic command.

Note Vote Results

When the result of a proposal is clear, record the result as being agreed with meetbot (e.g. "#agreed Proposal: Eat more bacon was approved (+1: 6, 0: 0, -1: 1)")