Meeting:CommOps 2016-09-27

Fedora CommOps Team Meeting Minutes 2016-09-27

Meeting Time

• 2016-09-27 16:30 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-09-27)
• #meetingname commops
• #nick commops
• #chair <given to approved members of FAS group at meeting>

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

• #topic Roll Call / Q&A
  • #info Name; Timezone; Sub-projects/Interest Areas
  • #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  • 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 === "Change Checkpoint: 100% Code Complete Deadline" ===
    • #link https://fedoraproject.org/wiki/Releases/25/Schedule
    • #info As of today, no more new code or major changes will be incorporated into Fedora 25. This sets us on track for the Fedora 25 Beta release in another two weeks on October 11th, 2016.
  • #info === "What is the Fedora Code of Conduct?" ===
    • #link https://communityblog.fedoraproject.org/what-is-fedora-code-conduct/
    • #info A short article that introduces and details what the Fedora Code of Conduct is, what it accomplishes, and why we have it.
  • #info === "Fedora Media Writer Test Day – 2016-09-20" ===
    • #link https://communityblog.fedoraproject.org/fedora-media-writer-test-day-2016/
    • #info This past week, the Fedora QA team organized a test day for the new Media Writer tool, to help make it easier and more effective to create live USBs (as compared to the current tool available). More results should become available about the test day outcome soon.

• #topic Action items from last meeting
  • #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-09-20-16.31.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 === jflory7 Write an introductory post for Outreachy 2016 on the CommBlog ===
  • #info === jflory7 Review emails for pending posts on the CommBlog ===
  • #info === skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
  • #info === skamath Research Bugzilla datagrepper queries for new bug report tickets ===
  • #info === commops Review comments in ticket #78, reply and leave feedback with your thoughts when possible ===
  • #info === jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83 ===
  • #info === dhanesh95 Follow-up in Infra ticket for creating second Python SIG group ===
  • #info === jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards ===
  • #info === commops Look into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article (more info to be put into ticket) ===

• #topic Tickets
  • #link https://pagure.io/fedora-commops/issues?tags=meeting
  • #info === Ticket #34, 52, 84 ===
    • #info "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series, Quality Assurance, "
    • #link https://pagure.io/fedora-commops/issue/34
    • #link https://pagure.io/fedora-commops/issue/52
    • #link https://pagure.io/fedora-commops/issue/84
  • #info === Ticket #81 ===
    • #info "Migrating to Pagure"
    • #link https://pagure.io/fedora-commops/issue/81
  • #info === Ticket #83 ===
    • #info "replace/improve etherpad working space"
    • #link https://pagure.io/fedora-commops/issue/83

• #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) "What is the Fedora Code of Conduct?"
      • #link https://communityblog.fedoraproject.org/what-is-fedora-code-conduct/
      • #info Total Views (Sept. 20 - Sept. 27):
      • #link
    • #info (2) "Fedora Media Writer Test Day – 2016-09-20"
      • #link https://communityblog.fedoraproject.org/fedora-media-writer-test-day-2016/
      • #info Total Views (Sept. 20 - Sept. 27):
      • #link
  • #info === Coming Up in CommBlog ===
    • #info (1) ""
      • #link
    • #info (2) ""
      • #link
    • #info (3) ""
      • #link

• #topic Release Schedule
  • #link https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
  • #info (1)
  • #info (2)
  • #info (3)

• #topic Open Floor

Next Meeting

• 2016-10-04 16:30 UTC in #fedora-meeting