From Fedora Project Wiki

Revision as of 17:00, 10 November 2016 by Tibbs (talk | contribs) (Use my proper nick.)

Sometime before the meeting

  1. Check the New/reopened ticket report and move things to the meeting status so that they appear on the meeting agenda. This report should generally stay completely empty; otherwise we're not acting on tickets.
  2. Check needinfo tickets (need to write this report) to see if they should still be in needinfo. Ping old ones, close really old ones, and move answered to meeting status if ready for discussion.

Day before the meeting

  1. Read the Meeting agenda report and announce agenda to the devel mailing list.

On the day of the meeting

  1. Have a copy of the agenda open (in email or otherwise to cut and paste from).
  2. Paste the following into IRC (#fedora-meeting-1)
    #startmeeting fpc
    #meetingname fpc
    #topic Roll Call
  3. ping FPC members about the meeting and chair them as they say they're available:
    geppetto limburgher mbooth orionp racor Rathann SmootherFr0gZ tibbs tomspur: FPC ping
    #chair REPLY
    /msg geppetto,limburgher,mbooth,orionp,racor,Rathann,SmootherFr0gZ,tibbs,tomspur FPC: /join #fedora-meeting-1
  4. See who is present. For quorum we need to have five members. Three or more members can sometimes have productive meetings to discuss drafts and come up with questions for tickets and even partial voting (with the remainder of votes to come in tickets). You have to have a rough feeling for the state of the tickets to know if this will be worthwhile.
  5. For each agenda item, paste the #topic line and the link to the fpc ticket. Note that the zodbot doesn't have a command for fpc tickets so .fpc NNN won't do anything.
    #topic #NNN - Summary
    • It's good to stick close to the order of items in the agenda so people reading the agenda can know whether their issue is likely to come up, however, you may want to deviate if an item is important (example: necessary for a Fedora Change or blocking a FESCo decision) or if the submitter of a ticket is present at the meeting.
    • Also -- if we have many tickets, meetings tend to last for two hours but not everyone can stay that long. try to put important business into the first hour.
  6. When you get close to two hours or do not have enough members to hold a good discussion about tickets it's time to end the meeting.
  7. Do an open floor in case someone has something to bring up.
    #topic Open Floor
  8. End the meeting
  9. Summarize all discussions in the fpc tickets

After the meeting

  • Check the Tickets pending write-up report, pick any unassigned ticket, update the wiki accordingly, add a short announcement to the ticket and set its state to 'announce'. Note that for bundled library requests, most tickets need only to be moved to the "Bundled Library Tracking" component, and be closed with resolution "accepted".
  • Check the Tickets pending announcement report, concatenate the announcement info in each, and post to the devel-announce list.