From Fedora Project Wiki

(new procedure around meeting keyword)
m (Another monday -> friday change)
(46 intermediate revisions by 17 users not shown)
Line 5: Line 5:
== Pre-meeting ==
== Pre-meeting ==


1 "business day" before the meeting is scheduled, do the following tasks: (So, Friday if meetings are Monday, etc)
On Wednesday (or at least Thursday!) before the Friday meeting, do the following tasks:


1. First, check the trac "All Active Tickets" report:
1. First, check for any open issues:


https://fedorahosted.org/fesco/report/1
https://pagure.io/fesco/issues


2. For each issue:
*  Make sure to check with and invite stakeholders who may not be CC'd in the issue. Consider deferring issue if stakeholders have not had adequate notice and are not available for discussion.
*  When an issue should be discussed in the meeting, click on 'Edit Metadata' and add the 'meeting' tag. Please note that only members of [https://pagure.io/group/fesco fesco] group on pagure can add the 'meeting' tag.
* When an issue is older than a week and was already voted upon by enough FESCo members, close it appropriately and remember it for the digest section in the meeting announcement


2. For each ticket, make sure to check with and invite stakeholders who may not be CC'd in the ticket. Consider deferring issue if stakeholders have not had adequate notice and are not available for discussion.
3. Also check for tickets that were closed after last meeting with an in-ticket vote to mention them in the respective section


3. When a ticket is ready for discussion, add the 'meeting' keyword.
4. You may want to ping the Change Wrangler to ask if there are any new Changes to discuss


4. You may want to ping the Feature Wrangler to ask if there are any new features to discuss
5. Go through the report of 'meeting' issues, and add them to a copy of the template below.


5. Go through the report of 'meeting' tickets, and add them to a copy of the template below.
https://pagure.io/fesco/report/meeting_agenda


https://fedorahosted.org/fesco/report/9
.
6. Generate an email to the devel@lists.fedoraproject.org list with the following template:  
6. Generate an email to the devel@lists.fedoraproject.org list with the following template:  
<pre>
Schedule for Wednesday's FESCo Meeting (YYYY-MM-DD)
</pre>
(Replace "Wednesday's" with the day of week for the meeting)
<pre>


Following is the list of topics that will be discussed in the FESCo
{{#tag:pre|
meeting Wednesday at 17:00UTC in #fedora-meeting on irc.freenode.net.
Schedule for Friday's FESCo Meeting ({{#time:Y-m-d|friday}})
}}
 
{{#tag:pre|
 
Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.


To convert UTC to your local time, take a look at
To convert UTC to your local time, take a look at
Line 36: Line 40:


or run:
or run:
   date -d 'YYYY-MM-DD 17:00 UTC'
   date -d '{{#time:Y-m-d|friday}} 15:00 UTC'




Links to all tickets below can be found at:  
Links to all issues to be discussed can be found at:  
https://fedorahosted.org/fesco/report/9
https://pagure.io/fesco/report/meeting_agenda
 
= Discussed and Voted in the Ticket =
Title of issue
https://pagure.io/fesco/issue/###
DECISION (+X, Y, -Z)


= Followups =
= Followups =


#topic #NNN Title of ticket
#topic #NNN Title of issue
.fesco NNN
.fesco NNN
https://fedorahosted.org/fesco/ticket/NNN
https://pagure.io/fesco/issue/NNN


= New business =
= New business =


#topic #NNN Title of ticket
#topic #NNN Title of issue
.fesco NNN
.fesco NNN
https://fedorahosted.org/fesco/ticket/NNN
https://pagure.io/fesco/issue/NNN


= Open Floor =  
= Open Floor =  


For more complete details, please visit each individual ticket.  The
For more complete details, please visit each individual
report of the agenda items can be found at
issue.  The report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9
https://pagure.io/fesco/report/meeting_agenda


If you would like to add something to this agenda, you can reply to
If you would like to add something to this agenda, you can
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
reply to this e-mail, file a new issue at
e-mail me directly, or bring it up at the end of the meeting, during
https://pagure.io/fesco, e-mail me directly, or bring it
the open floor topic. Note that added topics may be deferred until
up at the end of the meeting, during the open floor topic. Note
the following meeting.  
that added topics may be deferred until the following meeting.  
</pre>
}}


Replace NNN with the ticket numbers and add in Title of tickets.
Replace NNN with the issue numbers and add in Title of issues.




Line 74: Line 83:


<pre>
<pre>
Schedule for Monday's FESCo Meeting (2012-01-23)
Schedule for Friday's FESCo Meeting (2014-10-01)


Following is the list of topics that will be discussed in the FESCo
Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 17:00UTC in #fedora-meeting on irc.freenode.net.
meeting Friday at 15:00UTC in #fedora-meeting on irc.freenode.net.


To convert UTC to your local time, take a look at
To convert UTC to your local time, take a look at
Line 83: Line 92:


or run:
or run:
   date -d '2012-01-23 HH:MM UTC'
   date -d '2014-10-01 15:00 UTC'


Links to all tickets below can be found at:  
Links to all issues below can be found at:  
https://fedorahosted.org/fesco/report/9
https://pagure.io/fesco/report/meeting_agenda


= Followups =
= Followups =
Line 92: Line 101:
#topic sponsor request - sdake
#topic sponsor request - sdake
.fesco 724
.fesco 724
https://fedorahosted.org/fesco/ticket/724
https://pagure.io/fesco/issue/724


#topic Working Group Status Reports
#topic Working Group Status Reports
.fesco 1221
.fesco 1221
https://fedorahosted.org/fesco/ticket/1221
https://pagure.io/fesco/issue/1221


= New business =
= New business =
Line 102: Line 111:
#topic F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET
#topic F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET
.fesco 751
.fesco 751
https://fedorahosted.org/fesco/ticket/751
https://pagure.io/fesco/issue/751


#topic F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD
#topic F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD
.fesco 752
.fesco 752
https://fedorahosted.org/fesco/ticket/752
https://pagure.io/fesco/issue/752


#topic F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication
#topic F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication
.fesco 754
.fesco 754
https://fedorahosted.org/fesco/ticket/754
https://pagure.io/fesco/issue/754


#topic F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool
#topic F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool
.fesco 755
.fesco 755
https://fedorahosted.org/fesco/ticket/755
https://pagure.io/fesco/issue/755


#topic F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster
#topic F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster
.fesco 756
.fesco 756
https://fedorahosted.org/fesco/ticket/756
https://pagure.io/fesco/issue/756


= Open Floor =  
= Open Floor =  


For more complete details, please visit each individual ticket.  The
For more complete details, please visit each individual issue.  The
report of the agenda items can be found at
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9
https://pagure.io/fesco/report/meeting_agenda


If you would like to add something to this agenda, you can reply to
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
this e-mail, file a new issue at https://pagure.io/fesco/,
e-mail me directly, or bring it up at the end of the meeting, during
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the open floor topic. Note that added topics may be deferred until
Line 139: Line 148:
2. Generate a text file from the following template:  
2. Generate a text file from the following template:  


<pre>
 
#startmeeting FESCO (YYYY-MM-DD)
{{#tag:pre|
#startmeeting FESCO ({{#time:Y-m-d|friday}})
#meetingname fesco
#meetingname fesco
#chair dgilmore jwb kalev mattdm mitr mmaslano nirik sgallagh t8m thozza
#chair nirik, bowlofeggs, jforbes, zbyszek, bookwar, sgallagh, contyk, mhroncok, otaylor
#topic init process
#topic init process
#topic #NNN TICKET TITLE
#topic #NNNN TICKET TITLE
.fesco NNNN
https://pagure.io/fesco/issue/NNNN
#agree DECISION (+X, Y, -Z)
...
...
#topic Next week's chair
#topic Next week's chair
#action NAME will chair next meeting
#topic Open Floor
#topic Open Floor
#endmeeting
#endmeeting
</pre>
}}


Note mmaslano is a FESCo liaison for Environment and Stacks WG, not a voting FESCo member.
Note that mmaslano and stickster are FESCo liaisons for the Environment and Stacks and Workstation WGs, respectively, and not voting FESCo members.


You can copy and paste in lines from this file as the meeting progresses.  
You can copy and paste in lines from this file as the meeting progresses.  


3. Start an email replying to the agenda post. Rename the subject to: Summary/Minutes for today's FESCo meeting (YYYY-MM-DD)
3. Start an email replying to the agenda post. Change the subject to: <tt>Summary/Minutes for today's FESCo meeting ({{#time:Y-m-d|monday}})></tt>
 
4. Also, CC: meetingminutes@lists.fedoraproject.org


== Meeting time ==
== Meeting time ==
Line 165: Line 177:
2. Wait a few for people to show up. Confirm there are at least (5) voting members present for Quorum. If not, cancel meeting.  
2. Wait a few for people to show up. Confirm there are at least (5) voting members present for Quorum. If not, cancel meeting.  


3. Go through each topic. Watch time on each and if 15minutes are reached, ask if people want to keep discussing that topic or move on.  
3. Go through each topic. Watch time on each and if 15 minutes are reached, one of the following actions may be taken:
 
* If there is a vote to continue, then discussion continues for an additional 15 minutes.
 
* If there is no vote to continue the discussion after the initial 15 minutes, ask those members who are discussing the issue to clearly write up their thoughts and position on a wiki page for consideration at the next meeting. Each view point can list their thoughts as a separate proposal, or work off-line with others, to come up with a single proposal acceptable to them all. The wiki page is used in the next meeting to guide discussions and voting.


== Post meeting ==
== Post meeting ==


1. When #endmeeting runs it displays links for the logs. Use the .txt and then .log.txt files in your email created above. Send out right after meeting. (If you wait, it's very easy to forget). (Make sure and CC: meetingminutes@lists.fedoraproject.org too) 
1. When #endmeeting runs it displays links for the logs. Use the .txt and then .log.txt files to send an e-mail as a reply to the meeting schedule e-mail.
The subject should be:


The subject should be:
{{#tag:pre|Summary/Minutes from today's FESCo Meeting ({{#time:Y-m-d|friday}})
}}


<pre>
Send the e-mail right after the meeting to not forget it.
Summary/Minutes from today's FESCo Meeting (YYYY-MM-DD)
</pre>


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


[[Category:FESCo]] [[Category:FESCo policy]]
[[Category:FESCo]] [[Category:FESCo policy]]

Revision as of 14:59, 10 May 2019

FESCo meeting process

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

Pre-meeting

On Wednesday (or at least Thursday!) before the Friday meeting, do the following tasks:

1. First, check for any open issues:

https://pagure.io/fesco/issues

2. For each issue:

  • Make sure to check with and invite stakeholders who may not be CC'd in the issue. Consider deferring issue if stakeholders have not had adequate notice and are not available for discussion.
  • When an issue should be discussed in the meeting, click on 'Edit Metadata' and add the 'meeting' tag. Please note that only members of fesco group on pagure can add the 'meeting' tag.
  • When an issue is older than a week and was already voted upon by enough FESCo members, close it appropriately and remember it for the digest section in the meeting announcement

3. Also check for tickets that were closed after last meeting with an in-ticket vote to mention them in the respective section

4. You may want to ping the Change Wrangler to ask if there are any new Changes to discuss

5. Go through the report of 'meeting' issues, and add them to a copy of the template below.

https://pagure.io/fesco/report/meeting_agenda

6. Generate an email to the devel@lists.fedoraproject.org list with the following template:

 
Schedule for Friday's FESCo Meeting (2024-03-29)
 

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2024-03-29 15:00 UTC'


Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =
Title of issue
https://pagure.io/fesco/issue/###
DECISION (+X, Y, -Z)

= Followups =

#topic #NNN Title of issue
.fesco NNN
https://pagure.io/fesco/issue/NNN

= New business =

#topic #NNN Title of issue
.fesco NNN
https://pagure.io/fesco/issue/NNN

= Open Floor = 

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or 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. 

Replace NNN with the issue numbers and add in Title of issues.


Sample:


Schedule for Friday's FESCo Meeting (2014-10-01)

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 15:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2014-10-01 15:00 UTC'

Links to all issues below can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic sponsor request - sdake
.fesco 724
https://pagure.io/fesco/issue/724

#topic Working Group Status Reports
.fesco 1221
https://pagure.io/fesco/issue/1221

= New business =

#topic F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET
.fesco 751
https://pagure.io/fesco/issue/751

#topic F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD
.fesco 752
https://pagure.io/fesco/issue/752

#topic F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication
.fesco 754
https://pagure.io/fesco/issue/754

#topic F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool
.fesco 755
https://pagure.io/fesco/issue/755

#topic F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster
.fesco 756
https://pagure.io/fesco/issue/756

= Open Floor = 

For more complete details, please visit each individual issue.  The
report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can reply to
this e-mail, file a new issue at https://pagure.io/fesco/,
e-mail me directly, or 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.

Day of meeting

1. Send out a reminder IRC message a bit before the meeting to the #fedora-devel IRC channel.

2. Generate a text file from the following template:


 
#startmeeting FESCO (2024-03-29)
#meetingname fesco
#chair nirik, bowlofeggs, jforbes, zbyszek, bookwar, sgallagh, contyk, mhroncok, otaylor
#topic init process
#topic #NNNN TICKET TITLE
.fesco NNNN
https://pagure.io/fesco/issue/NNNN
#agree DECISION (+X, Y, -Z)
...
#topic Next week's chair
#action NAME will chair next meeting
#topic Open Floor
#endmeeting

Note that mmaslano and stickster are FESCo liaisons for the Environment and Stacks and Workstation WGs, respectively, and not voting FESCo members.

You can copy and paste in lines from this file as the meeting progresses.

3. Start an email replying to the agenda post. Change the subject to: Summary/Minutes for today's FESCo meeting (2024-04-01)>

Meeting time

1. Use the lines up to 'init process' to start the meeting.

2. Wait a few for people to show up. Confirm there are at least (5) voting members present for Quorum. If not, cancel meeting.

3. Go through each topic. Watch time on each and if 15 minutes are reached, one of the following actions may be taken:

  • If there is a vote to continue, then discussion continues for an additional 15 minutes.
  • If there is no vote to continue the discussion after the initial 15 minutes, ask those members who are discussing the issue to clearly write up their thoughts and position on a wiki page for consideration at the next meeting. Each view point can list their thoughts as a separate proposal, or work off-line with others, to come up with a single proposal acceptable to them all. The wiki page is used in the next meeting to guide discussions and voting.

Post meeting

1. When #endmeeting runs it displays links for the logs. Use the .txt and then .log.txt files to send an e-mail as a reply to the meeting schedule e-mail. The subject should be:

Summary/Minutes from today's FESCo Meeting (2024-03-29)

Send the e-mail right after the meeting to not forget it.

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