From Fedora Project Wiki

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-05-24

Meeting Time

Participants

This week's CommOps Meeting will be led by decause.

  • The participants will be posted after the meeting.

Meeting Protocol

  • To help improve the flow of the meeting, using the IRC Meeting Protocol is encouraged, as modeled by the EMEA Ambassadors.
  • Please follow the Meeting Protocol where possible.

Agenda

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-05-24)
  • #meetingname commops
  • #nick commops
  • #chair <given to approved members of FAS group at meeting>



  • #topic Roll Call / Q&A
    • #info Name; Timezone; Sub-projects/Interest Areas
    • If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.


  • #topic Announcements
    • #info === "Flock 2016 schedule is now out" ===
      • #link https://fedoramagazine.org/flock-2016-schedule-now/
      • #info Flock is Fedora's annual contributor conference where Fedorans across the world get together for talks, sprints, workshops, and more. The schedule for this year's Flock was recently published and you can find out what talks and workshops there will be for this year. Some CommOpsers are giving talks this year!
    • #info === Google Summer of Code "All-Hands", 2016-05-25, 15:00 UTC ===
      • #info The Google Summer of Coding All-Hands meeting will be on Wednesday at 15:00 UTC in #fedora-meeting. This will be the big kick-off, officially, for the summer!
    • #info === Fedora @ PyCon US ===
      • #info There will be Fedora sprints at PyCon this year. They're from Thursday, 2016-06-02 to Sunday, 2016-06-05.
      • #info decause will be going to PyCon 2016-05-27 to 2016-06-02 and be harder to get a hold of than usual (until the sprints).


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-17/commops.2016-05-17-16.02.html
    • #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
    • #info === [COMPLETE] commops add the 'how it works' link above to the etherpad under resources ===
    • #info === [COMPLETE] decause send out timeslot requests for GSoC ===
    • #info === decause add money dollars to limesurvey due:Friday ===
    • #info === decause talk to spot about scheduling an EDU FAD after budget gets settled ===
    • #info === [INCOMPLETE] jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad ===
      • #action jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad
    • #info === [INCOMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
      • #action jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
    • #info === [INCOMPLETE] jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
      • #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
    • #info === [INCOMPLETE] jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
      • #action jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
    • #info === [COMPLETE] jflory7 Ship F24 Party article today ===
    • #info === [IN PROGRESS] jflory7 Remove Ticket #74 from meeting agenda, add info about where to find the pull request for the ticket ===
      • #action jflory7 Add info about where to find the pull request for Ticket #74
    • #info === decause / commops stop by the docs office hours tomo to discuss release notes -> release announce flow ===
    • #info === decause add conf schedule to Fedocal ===
    • #info === [COMPLETE] dhanesh95 Fork a wiki page for the Education FAD from the template linked previously and begin templating the details for the Education FAD to take place over this summer ===






  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting