Meeting:CommOps 2016-06-28

Fedora CommOps Team Meeting Minutes 2016-06-28

Meeting Time

• 2016-06-28 16:00 UTC
• #fedora-meeting on freenode

Participants

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

• 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-06-28)
• #meetingname commops
• #nick commops
• #chair <given to approved members of FAS group at meeting>

• #topic Agenda
  • #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-28
  • #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 === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info

• #topic Action items from last meeting
  • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-06-21-15.57.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 === [CHANGED] decause review the vFAD goals / objectives / etc. ===
    • #action jflory7 Move forward with making final plans for vFAD or reconsider plans for Flock workshop (???)
  • #info === [CHANGED] decause nail down Flock arrangements and add to fedocal ===
    • #info Further Flock arrangements will be handled by the Flock staff for now, as far as I can tell? --Jflory7 (talk) 03:29, 28 June 2016 (UTC)
  • #info === [INCOMPLETE] jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
    • #action jflory7 jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
  • #info === [INCOMPLETE] decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page ===
    • #info Red Hat Summit happening now.
  • #info === [INCOMPLETE] jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later ===
    • #action jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later
  • #info === [IN PROGRESS] jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response ===
    • #action jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response
  • #info === [COMPLETE] jflory7 Create a placeholder article for F22 EoL article in CommBlog so we keep on the agenda ===
    • #link https://communityblog.fedoraproject.org/?p=1681&preview=1&_ppp=f5cd19f98b
  • #info === [COMPLETE] jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets context to what they are for a CommBlog article ===

• #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 No new posts published this week!
  • #info === Coming Up in CommBlog ===
    • #info (1) "Southeast Linux Fest 2016"
      • #link https://communityblog.fedoraproject.org/?p=1676&preview=1&_ppp=e048ea9a97
    • #info (2) "Hosting your own Fedora Test Day"
      • #link https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=c49265f3f2
    • #info (3) "Fedora 22: End Of Life, 2016 July 19"
      • #link https://communityblog.fedoraproject.org/?p=1681&preview=1&_ppp=f5cd19f98b
    • #info (4) "Getting started with 'update-testing' Fedora QA part 2"
      • #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=b50b2a4e03
    • #info (5) "Getting started with Fedora QA part 3"
      • #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=f84ad57ee4

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

• #topic Open Floor

Next Meeting

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