Meeting:CommOps 2016-05-31

Fedora CommOps Team Meeting Minutes 2016-05-31

Meeting Time

• 2016-05-31 16:00 UTC
• #fedora-meeting on freenode

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

CommOpsers, update this agenda with your latest items before the meeting has started.

• #startmeeting Fedora CommOps (2016-05-31)
• #meetingname commops
• #nick CommOps
• #chair <given to approved members of FAS group at meeting>

• #topic Agenda
  • #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-31
  • #info (1) Roll Call / Q&A
  • #info (2) Announcements
  • #info (3) Action items from last meeting
  • #info (4) Tickets
  • #info (5) Wiki Gardening
  • #info (6) Community Blog
  • #info (7) Release Schedule
  • #info (8) Open Floor

• #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 === "Fedora <3's PyCon 2016" ===
    • #link https://communityblog.fedoraproject.org/fedora-loves-pycon-2016/
    • #link https://us.pycon.org/2016/
    • #info PyCon US 2016 is this week, and many members of the Fedora contributor community can be found there this week. There will be Fedora sprints coming up later on in the week, so stay tuned for any news from the team there. If you're at PyCon, stop by the Fedora table and say hello!
  • #info === Developing the story of Fedora 24 ===
    • #link https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/HZLH2L27LQTUA6FGDGRKGUN52ALJMPO7/
    • #info There is ongoing discussion about how to develop the "story" of Fedora 24 for this past release cycle. This discussion is going to be used in the release announcement for F24. If you have ideas about how to develop this story, chime in on the mailing list thread and add your thoughts! F24 is growing closer fast!

• #topic Action items from last meeting
  • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-24/commops.2016-05-24-15.58.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] cprofitt File a ticket for wiki gardening the Python SIG page (others who have noticed things can also chime in, cc: LinuxHippie / dhanesh95) ===
    • #link https://fedorahosted.org/fedora-commops/ticket/77
  • #info === [IN PROGRESS] decause follow-up with tatica and diversity team about limesurvey avaiability ===
    • #action decause Follow up with tatica and diversity team about LimeSurvey availability
    • #info tatica has been offline due to illness, so might be a slight delay in getting this one done
  • #info === [IN PROGRESS] 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 Email draft is started, will be sent out by end of day
  • #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 === [CLOSED] jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
    • #info Article has gone past its prime publishing period (event was in early April); there are individual Ambassador reports for the event, so this should suffice for the time being.
  • #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 ===
    • #link jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
  • #info === [IN PROGRESS] decause work with jzb to possibly organize a release party in RDU
    • #link decause Work with jzb to organize the release party in Raleigh, NC area
  • #info === [COMPLETE] jflory7 Add info about where to find the pull request for Ticket #74
    • #link https://fedorahosted.org/fedora-commops/ticket/74#comment:3
  • #info === [COMPLETE] decause / commops stop by the docs office hours tomo to discuss release notes -> release announce flow ===
    • #info decause and jflory7 stopped by for a bit to check in with the team and generate some ideas, more info to come.
  • #info === [IN PROGRESS...?] decause nail down Flock arrangements, add them to Fedocal ===
    • #action decause nail down Flock arrangements, add them to Fedocal
  • #info === [IN PROGRESS] decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
    • #action decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
  • #info === [COMPLETE] maxamillion log into commblog, create a draft for the OSCON report, and then review decause's edits ===
    • #info maxamillion is logged into the CommBlog and is the "author" of the post in the drafts folder
  • #info === [INCOMPLETE] decause input the report, make edits, clear with maxamillion, push before Friday Wheels Up for PyCon ===
    • #action decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push

• #topic Tickets
  • #link https://fedorahosted.org/fedora-commops/report/9
  • #info === Ticket #xx ===
    • #info ""
    • #link
    • description
  • #info === Ticket #xx ===
    • #info ""
    • #link
    • description
  • #info === Ticket #xx ===
    • #info ""
    • #link
    • description

• #topic Wiki Gardening
  • #action CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]

• #topic Community Blog
  • #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
  • #info === This Week in CommBlog ===
    • #info (1) "Fedora <3's PyCon 2016"
      • #link https://communityblog.fedoraproject.org/fedora-loves-pycon-2016/
      • #info Total Views (May 30 - May 31): 27
      • #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1571
  • #info === Coming Up in CommBlog ===
    • #info (1) "OSCON 2016 Expo Hall Booth Report" by maxamillion
      • #link https://communityblog.fedoraproject.org/?p=1558&preview=1&_ppp=68845221b1
      • #action jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source

• #topic Release Schedule
  • #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html

• #topic Open Floor

Next Meeting

• 2016-06-07 16:00 UTC in #fedora-meeting