(update for move to friday) |
(change to new time 17:00 UTC) |
||
Line 30: | Line 30: | ||
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 | meeting friday at 17: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 36: | ||
or run: | or run: | ||
date -d '{{#time:Y-m-d|friday}} | date -d '{{#time:Y-m-d|friday}} 17:00 UTC' | ||
Line 77: | Line 77: | ||
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 | meeting Friday at 17: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 83: | ||
or run: | or run: | ||
date -d '2014-10-01 | date -d '2014-10-01 17:00 UTC' | ||
Links to all tickets below can be found at: | Links to all tickets below can be found at: |
Revision as of 17:15, 8 January 2016
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 the trac "All Active Tickets" report:
https://fedorahosted.org/fesco/report/1
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. When a ticket is ready for discussion, add the 'meeting' keyword.
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' tickets, and add them to a copy of the template below.
https://fedorahosted.org/fesco/report/9
6. Generate an email to the devel@lists.fedoraproject.org list with the following template:
Schedule for Friday's FESCo Meeting (2024-08-16)
Following is the list of topics that will be discussed in the FESCo meeting friday at 17: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-08-16 17:00 UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #NNN Title of ticket .fesco NNN https://fedorahosted.org/fesco/ticket/NNN = New business = #topic #NNN Title of ticket .fesco NNN https://fedorahosted.org/fesco/ticket/NNN = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 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, 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 ticket numbers and add in Title of tickets.
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 17: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 17:00 UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic sponsor request - sdake .fesco 724 https://fedorahosted.org/fesco/ticket/724 #topic Working Group Status Reports .fesco 1221 https://fedorahosted.org/fesco/ticket/1221 = New business = #topic F17 Feature: DIET - https://fedoraproject.org/wiki/Features/F17_DIET .fesco 751 https://fedorahosted.org/fesco/ticket/751 #topic F17 Feature: Rework Live CD - https://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD .fesco 752 https://fedorahosted.org/fesco/ticket/752 #topic F17 Feature: ABRT Backtrace Deduplication - https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication .fesco 754 https://fedorahosted.org/fesco/ticket/754 #topic F17 Feature: Font Configuration Tool - https://fedoraproject.org/wiki/Features/FontConfigurationTool .fesco 755 https://fedorahosted.org/fesco/ticket/755 #topic F17 Feature: English Typing Booster - https://fedoraproject.org/wiki/Features/english-typing-booster .fesco 756 https://fedorahosted.org/fesco/ticket/756 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 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, 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-08-16) #meetingname fesco #chair maxamillion dgilmore number80 jwb nirik paragan jsmith kalev sgallagh #topic init process #topic #NNN TICKET TITLE ... #topic Next week's chair #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-08-16)>
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 15minutes are reached, ask if people want to keep discussing that topic or move on.
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).
The subject should be:
Summary/Minutes from today's FESCo Meeting (2024-08-16)
2. Process through tickets comment/close them as appropriate.