From Fedora Project Wiki

(→‎Day of meeting: jforbes is a new FESCo member :))
(→‎Day of meeting: Another missed tuesday)
(45 intermediate revisions by 9 users not shown)
Line 5: Line 5:
== Pre-meeting ==
== Pre-meeting ==


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


1. First, check for any open issues:
1. First, check for any open issues:
Line 11: Line 11:
https://pagure.io/fesco/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.
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


3. When an issue is ready for discussion, 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.
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
4. You may want to ping the Change Wrangler to ask if there are any new Changes to discuss
Line 24: Line 27:


{{#tag:pre|  
{{#tag:pre|  
Schedule for Friday's FESCo Meeting ({{#time:Y-m-d|friday}})
Schedule for Monday's FESCo Meeting ({{#time:Y-m-d|monday}})
}}
}}


Line 30: Line 33:


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


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


or run:
or run:
   date -d '{{#time:Y-m-d|friday}} 16:00 UTC'
   date -d '{{#time:Y-m-d|monday}} 19:00 UTC'




Links to all issues below can be found at:  
Links to all issues to be discussed can be found at:  
https://pagure.io/fesco/report/meeting_agenda
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 issue
#NNN Title of issue
.fesco NNN
https://pagure.io/fesco/issue/NNN
https://pagure.io/fesco/issue/NNN


= New business =
= New business =


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


Line 75: Line 82:


<pre>
<pre>
Schedule for Friday's FESCo Meeting (2014-10-01)
Schedule for Monday's FESCo Meeting (2021-06-21)


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 Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.
meeting Monday at 19:00UTC in #fedora-meeting on irc.libera.chat.


To convert UTC to your local time, take a look at
To convert UTC to your local time, take a look at
Line 84: Line 91:


or run:
or run:
   date -d '2014-10-01 16:00 UTC'
   date -d '2021-06-21 19:00 UTC'


Links to all issues below can be found at:  
Links to all issues below can be found at:  
Line 91: Line 98:
= Followups =
= Followups =


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


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


= New business =
= New business =


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


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


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


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


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


Line 142: Line 142:


{{#tag:pre|  
{{#tag:pre|  
#startmeeting FESCO ({{#time:Y-m-d|friday}})
#startmeeting FESCO ({{#time:Y-m-d|monday}})
#meetingname fesco
#meetingname fesco
#chair maxamillion dgilmore jwb nirik jforbes jsmith kalev sgallagh Rathann
#chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, defolos, mboddu, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor
#topic init process
#topic init process
#topic #NNN TICKET TITLE
#topic #NNNN TICKET TITLE
.fesco 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
}}
}}
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. Change the subject to: <tt>Summary/Minutes for today's FESCo meeting ({{#time:Y-m-d|friday}})></tt>
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>


== Meeting time ==
== Meeting time ==
Line 165: Line 166:
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).
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|  
{{#tag:pre|Summary/Minutes from today's FESCo Meeting ({{#time:Y-m-d|monday}})
Summary/Minutes from today's FESCo Meeting ({{#time:Y-m-d|friday}})
}}
}}
Send the e-mail right after the meeting to not forget it.


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 17:42, 19 June 2021

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 Friday before the Monday 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 Monday's FESCo Meeting (2024-04-01)
 

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 19:00UTC in #fedora-meeting on
irc.libera.chat.

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

or run:
  date -d '2024-04-01 19: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 =

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

= New business =

#NNN Title of issue
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 Monday's FESCo Meeting (2021-06-21)

Following is the list of topics that will be discussed in the FESCo
meeting Monday at 19:00UTC in #fedora-meeting on irc.libera.chat.

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

or run:
  date -d '2021-06-21 19:00 UTC'

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

= Followups =

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

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

= New business =

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

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

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

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

#756 F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster
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-04-01)
#meetingname fesco
#chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, defolos, mboddu, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor
#topic init process
#topic #NNNN TICKET TITLE
.fesco NNNN
#agree DECISION (+X, Y, -Z)
...
#topic Next week's chair
#action NAME will chair next meeting
#topic Open Floor
#endmeeting

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-04-01)

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

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