From Fedora Project Wiki

m
(A few more facts)
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
= Fedora Council Meetings =
 
= Fedora Council Meetings =
  
The [https://docs.fedoraproject.org/fedora-project/council/charter.html Fedora Council] holds weekly meetings. Every other week we have an ''Open Floor'' meeting, where the agenda is set by attendees at the beginning of the hour. On the ''other'' weeks, we alternate between ''Tickets and Ongoing'' meetings and video-based ''Subproject reports''.
+
The [https://docs.fedoraproject.org/fedora-project/council/charter.html Fedora Council] holds meetings every other week. They're held in the <tt>#fedora-meeting</tt> channel on Freenode. These meetings have two components: an ''Open Floor'' section where the agenda is set by attendees at the beginning of the hour, and a ''Tickets and Ongoing'' section where the Fedora Program Manager goes through crucial [https://pagure.io/Fedora-Council/tickets/issues open tickets] to make sure each gets attention. We don't want to be entirely ticket-driven (since that's a reactive process), but this helps keep important issues from slipping through the cracks.  
  
 
You can see our upcoming meeting schedule in [https://apps.fedoraproject.org/calendar/list/council/ Fedocal].
 
You can see our upcoming meeting schedule in [https://apps.fedoraproject.org/calendar/list/council/ Fedocal].
Line 9: Line 9:
 
This guide explains how to manage and run a Council IRC meeting. Many of the steps here could well apply to other groups that hold regular IRC meetings as well.  
 
This guide explains how to manage and run a Council IRC meeting. Many of the steps here could well apply to other groups that hold regular IRC meetings as well.  
  
== ''Tickets and Ongoing'' Meetings ==
+
== Pre-meeting ==
 
 
''Tickets and Ongoing'' meetings happen every four weeks. They're held in the <tt>#fedora-meeting-1</tt> channel on Freenode. We don't want to be entirely ticket-driven (since that's a reactive process), but this helps keep important issues from slipping through the cracks.
 
 
 
=== Pre-meeting (Tickets and Ongoing)===
 
  
 
1. Go through [https://pagure.io/Fedora-Council/tickets/issues open tickets] and select several that seem timely or otherwise worth real-time discussion.This is also a good time to poke forward any issues that don't really need to be at the meeting but need further action, or to close issues that are resolved — or which won't be resolved. We want to keep the open tickets reflective of actual work in progress, not merely things we hope to get to someday. (Ticket system or not, there's an infinite pool of potential work for the Council, and keeping open tickets which we have no practical plan to work on is a recipe for sadness all around.)
 
1. Go through [https://pagure.io/Fedora-Council/tickets/issues open tickets] and select several that seem timely or otherwise worth real-time discussion.This is also a good time to poke forward any issues that don't really need to be at the meeting but need further action, or to close issues that are resolved — or which won't be resolved. We want to keep the open tickets reflective of actual work in progress, not merely things we hope to get to someday. (Ticket system or not, there's an infinite pool of potential work for the Council, and keeping open tickets which we have no practical plan to work on is a recipe for sadness all around.)
Line 22: Line 18:
  
 
{{#tag:pre|  
 
{{#tag:pre|  
Subject: Schedule for Wednesday's Tickets and Ongoing Fedora Council Meeting ({{#time:Y-m-d|wednesday}})
+
Subject: Schedule for the Fedora Council Meeting ({{#time:Y-m-d|thursday}})
 
}}
 
}}
  
 
{{#tag:pre|  
 
{{#tag:pre|  
The Fedora Council will hold our regular Tickets and Ongoing meeting
+
The Fedora Council will hold our regular meeting at
at 10:00am US/Eastern in #fedora-meeting-1 on irc.freenode.net.
+
1:00pm US/Eastern in #fedora-meeting on irc.freenode.net.
 
All are welcome!
 
All are welcome!
  
 
To convert to your local time, run:
 
To convert to your local time, run:
  
   TZ=US/Eastern date -d '10am {{#time:Y-m-d|wednesday}}'
+
   TZ=US/Eastern date -d '1pm {{#time:Y-m-d|thursday}}'
  
  
Line 48: Line 44:
 
}}
 
}}
  
=== During the Meeting (Tickets and Ongoing) ===
+
=== During the Meeting ===
  
 
You can copy and paste in lines from this template as the meeting proceeds. You may find it helpful to copy this to a file in advance, so you can pre-fill the <tt>topic</tt> lines.
 
You can copy and paste in lines from this template as the meeting proceeds. You may find it helpful to copy this to a file in advance, so you can pre-fill the <tt>topic</tt> lines.
  
 
{{#tag:pre|  
 
{{#tag:pre|  
#startmeeting Council ({{#time:Y-m-d|wednesday}})
+
#startmeeting Council ({{#time:Y-m-d|thursday}})
 
#meetingname council
 
#meetingname council
#chair amsharma ausil bex dperpeet pbrobinson jkurik jwboyer langdon mattdm robyduck tyll bcotton
+
#chair jwf riecatnor dcantrell dgilmore mattdm x3mboy bookwar bcotton pbrobinson asamalik
 
#topic Introductions, Welcomes
 
#topic Introductions, Welcomes
 
#topic Today's Agenda
 
#topic Today's Agenda
Line 71: Line 67:
 
2. Wait for a majority of the Council to show up.
 
2. Wait for a majority of the Council to show up.
  
3 We've found that our meetings and discussions are small and informal enough that we don't need special etiquette markers (like <tt>!</tt> to ask for permission to talk). If we ever do have a particularly contentious and popular topic, we may introduce rules like that temporarily but, usually, it's just not necessary.
+
3. Set the agenda include the tickets from the FPgM, and then use the open floor meeting agenda process:
  
4. Keep an eye on the clock — if a topic is using more than the expected time, sometimes that's okay, and other times it's best to ask that discussion continue in tickets and on the mailing list and move on.
+
* Ask for topics
 +
* Gauge popularity, sort topics
 +
* Ask if everyone is okay with the sorted list
  
5. Make liberal use of [[Zodbot]] commands like <tt>#topic</tt>, <tt>#info</tt>, and <tt>#help</tt>, to populate the meeting minutes.
+
4. We've found that our meetings and discussions are small and informal enough that we don't need special etiquette markers (like <tt>!</tt> to ask for permission to talk). If we ever do have a particularly contentious and popular topic, we may introduce rules like that temporarily — but, usually, it's just not necessary.  
  
=== Post meeting (Tickets and Ongoing) ===
+
5. Keep an eye on the clock — if a topic is using more than the expected time, sometimes that's okay, and other times it's best to ask that discussion continue in tickets and on the mailing list and move on.
  
1. The meeting minutes are automatically collected in [https://meetbot.fedoraproject.org/sresults/?group_id=council&type=team Møte] and emailed to [https://lists.fedoraproject.org/archives/list/meetingminutes@lists.fedoraproject.org/ meetingminutes]. It might be nice to find this and also mail it to the list. (Ideally, we'd enhance meetbot to automatically send these minutes to the appropriate list. <tt>#help</tt>, please!)
+
6. Make liberal use of [[Zodbot]] commands like <tt>#topic</tt>, <tt>#info</tt>, and <tt>#help</tt>, to populate the meeting minutes.
 
 
2. Process through tickets comment/close them as appropriate.
 
 
 
3. If you have any action items you can handle quickly, now is really a good time for it. Otherwise, don't forget to add these to your personal todo list.
 
 
 
== ''Open Floor'' Meetings ==
 
 
 
''Open Floor'' meetings happen every four weeks. As with ''Tickets and Ongoing'' meetings, they are held in the <tt>#fedora-meeting-1</tt> channel on Freenode. They do not have a preset agenda. Instead, we spend the first few minutes of the meeting deciding what topics will be discussed. If attendees — Council members and otherwise — have several topics of general interest, the primary meeting chair (usually the FPL or FCAIC) will put them in order, and after a certain amount of time discussing the first, ask if it's time to move on.
 
 
 
=== Pre-meeting (Open Floor) ===
 
 
 
The beauty of this is that it requires very little preparatory work. An automated calendar message will be sent to the list the day before, containing basic information about the meeting.
 
 
 
=== During the Meeting (Open Floor) ===
 
 
 
 
 
 
 
You can copy and paste in lines from this template as the meeting proceeds.
 
  
 
+
=== Post meeting (Tickets and Ongoing) ===
{{#tag:pre|
 
#startmeeting Council ({{#time:Y-m-d|wednesday}})
 
#meetingname council
 
#chair mattdm jkurik jwb langdon robyduck bexelbie dperpeet Amita dgilmore pbrobinson tyll bcotton
 
#topic Introductions, Welcomes
 
#topic Today's Open Floor Agenda
 
#topic (first topic decided on)...
 
#topic (next topic decided on)...
 
...
 
#endmeeting
 
}}
 
 
 
 
 
1. Use the lines up to 'Introductions, Welcomes' to start the meeting.
 
 
 
2. Wait a few for people to show up.
 
 
 
3. Follow the Open Floor meeting procedure:
 
#. Ask for topics
 
#. Gauge popularity, sort topics
 
#. Ask if everyone is okay with the sorted list
 
#. Move to the first topic
 
#. After ten minutes, or if discussion wanes, ask if people want to keep talking on the current topic or move on.
 
#. Sometimes, a little encouragement to get to further topics is a good idea. :)
 
 
 
4. Make liberal use of [[Zodbot]] commands like <tt>#topic</tt>, <tt>#info</tt>, and <tt>#help</tt>, to populate the meeting minutes.
 
 
 
=== Post meeting (Open Floor) ===
 
  
 
1. The meeting minutes are automatically collected in [https://meetbot.fedoraproject.org/sresults/?group_id=council&type=team Møte] and emailed to [https://lists.fedoraproject.org/archives/list/meetingminutes@lists.fedoraproject.org/ meetingminutes]. It might be nice to find this and also mail it to the list. (Ideally, we'd enhance meetbot to automatically send these minutes to the appropriate list. <tt>#help</tt>, please!)
 
1. The meeting minutes are automatically collected in [https://meetbot.fedoraproject.org/sresults/?group_id=council&type=team Møte] and emailed to [https://lists.fedoraproject.org/archives/list/meetingminutes@lists.fedoraproject.org/ meetingminutes]. It might be nice to find this and also mail it to the list. (Ideally, we'd enhance meetbot to automatically send these minutes to the appropriate list. <tt>#help</tt>, please!)
  
 
2. Process through tickets comment/close them as appropriate.
 
2. Process through tickets comment/close them as appropriate.
 
  
 
3. If you have any action items you can handle quickly, now is really a good time for it. Otherwise, don't forget to add these to your personal todo list.
 
3. If you have any action items you can handle quickly, now is really a good time for it. Otherwise, don't forget to add these to your personal todo list.
 
== Subproject Reports ==
 
 
TBD: expand this section. These are currently done with Jitsi and published to Youtube afterward.
 
 
[[Category:Council]] [[Category:Council policy]]
 

Latest revision as of 15:51, 24 August 2020

Fedora Council Meetings

The Fedora Council holds meetings every other week. They're held in the #fedora-meeting channel on Freenode. These meetings have two components: an Open Floor section where the agenda is set by attendees at the beginning of the hour, and a Tickets and Ongoing section where the Fedora Program Manager goes through crucial open tickets to make sure each gets attention. We don't want to be entirely ticket-driven (since that's a reactive process), but this helps keep important issues from slipping through the cracks.

You can see our upcoming meeting schedule in Fedocal.

Council Meeting Process

This guide explains how to manage and run a Council IRC meeting. Many of the steps here could well apply to other groups that hold regular IRC meetings as well.

Pre-meeting

1. Go through open tickets and select several that seem timely or otherwise worth real-time discussion.This is also a good time to poke forward any issues that don't really need to be at the meeting but need further action, or to close issues that are resolved — or which won't be resolved. We want to keep the open tickets reflective of actual work in progress, not merely things we hope to get to someday. (Ticket system or not, there's an infinite pool of potential work for the Council, and keeping open tickets which we have no practical plan to work on is a recipe for sadness all around.)

2. Consider other topics that might benefit from real-time discussion in order to move forward. Again, we don't want to block issues on waiting for "everyone in the room" conversations (when we have mailing lists and lazy consensus), but we've found that regular discussion is important.

3. An automated calendar message should appear on council-discuss@lists.fedoraproject.org list the day before the meeting. Reply to this message with the following template:

 
Subject: Schedule for the Fedora Council Meeting (2020-12-03)
 
The Fedora Council will hold our regular meeting at
1:00pm US/Eastern in #fedora-meeting on irc.freenode.net.
All are welcome!

To convert to your local time, run:

  TZ=US/Eastern date -d '1pm 2020-12-03'


Expected discussion items include:


YOUR AGENDA ITEMS HERE


If you would like to add something to this agenda, you can reply to
this email, e-mail me directly, file a new ticket at
https://pagure.io/Fedora-Council/tickets/issues, or if time permits,
bring it up at the end of the meeting, during the open floor topic.
Note that added topics may be deferred until the following meeting.

During the Meeting

You can copy and paste in lines from this template as the meeting proceeds. You may find it helpful to copy this to a file in advance, so you can pre-fill the topic lines.

 
#startmeeting Council (2020-12-03)
#meetingname council
#chair jwf riecatnor dcantrell dgilmore mattdm x3mboy bookwar bcotton pbrobinson asamalik
#topic Introductions, Welcomes
#topic Today's Agenda
(paste agenda from previous email)
#topic first topic...
#topic next topic...
...
#topic Open Floor
#endmeeting


1. Use the lines up through 'Introductions, Welcomes' to start the meeting.

2. Wait for a majority of the Council to show up.

3. Set the agenda — include the tickets from the FPgM, and then use the open floor meeting agenda process:

  • Ask for topics
  • Gauge popularity, sort topics
  • Ask if everyone is okay with the sorted list

4. We've found that our meetings and discussions are small and informal enough that we don't need special etiquette markers (like ! to ask for permission to talk). If we ever do have a particularly contentious and popular topic, we may introduce rules like that temporarily — but, usually, it's just not necessary.

5. Keep an eye on the clock — if a topic is using more than the expected time, sometimes that's okay, and other times it's best to ask that discussion continue in tickets and on the mailing list and move on.

6. Make liberal use of Zodbot commands like #topic, #info, and #help, to populate the meeting minutes.

Post meeting (Tickets and Ongoing)

1. The meeting minutes are automatically collected in Møte and emailed to meetingminutes. It might be nice to find this and also mail it to the list. (Ideally, we'd enhance meetbot to automatically send these minutes to the appropriate list. #help, please!)

2. Process through tickets comment/close them as appropriate.

3. If you have any action items you can handle quickly, now is really a good time for it. Otherwise, don't forget to add these to your personal todo list.