From Fedora Project Wiki

(Edited action items for skamath)
(Fixed typo)
Line 58: Line 58:
 
** #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
 
** #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
 
*** #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
 
*** #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
** #info === [INCOMPELTE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
+
** #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
 
*** #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
 
*** #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
 
** #info === [COMPLETE] skamath Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group ===
 
** #info === [COMPLETE] skamath Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group ===

Revision as of 16:40, 6 September 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-09-06

Meeting Time

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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-09-06)
  • #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
    • #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 === [Reminder] CommOps has moved to Pagure ===
      • #link https://pagure.io/fedora-commops
      • #info All of our tickets and data from Trac was migrated to Pagure last week. We will no longer use Trac for task management / tickets. Please sign into Pagure with your FAS account and check out the repository if you have not done so yet!
    • #info === "Announcing the release of Fedora 25 Alpha!" ===
    • #info === "Welcoming our new Fedora Community Action and Impact Coordinator" ===
      • #link https://fedoramagazine.org/welcoming-new-fedora-community-coordinator/
      • #info "Good news, everybody! I’m pleased to announce that we have completed our search for a new Fedora Community Action and Impact Coordinator, and he’ll be joining the Open Source and Standards (OSAS) team to work with Fedora as of 3 October. Please give a warm welcome to Brian Exelbierd (bexelbie)!"
    • #info === "Keeping Fedora beautiful: contribute your wallpaper!" ===


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-08-30-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 === [IN PROGRESS] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
      • #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
    • #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
      • #action jflory7 Review emails for pending posts on the CommBlog
      • They just keep coming! ;)
    • #info === [INCOMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
      • #action jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
    • #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
      • #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
    • #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
      • #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
    • #info === [COMPLETE] skamath Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group ===
    • #info === [COMPLETE] jflory7 Follow up on Pagure importer tool for use with decause's CommOps toolbox repositories ===
    • #info === [COMPLETE] jflory7 Remove Ticket #81 from meeting agenda ===
    • #info === dhanesh95 Start IRC / mailing list discussion on wiki gardening for Python SIG ===
    • #info === [COMPLETE] jflory7 Do some srs ticket triaging / updating this week ===
      • #info The CommOps Pagure is completely triaged and migrated to work well in Pagure versus Trac
    • #info === [COMPLETE] amitsin6h Double-check subscription to the mailing list and make sure you are receiving mail from the list ===
    • #info === jflory7 Come up with a more fitting introductory item to place into the meeting ===
    • #info === [COMPLETE] jflory7 Revisit Join page and edit / alter section about wiki page ===
    • #info === [COMPLETE] skamath Garden the CommOps wiki page to remove mention of Trac and replace with Pagure (and update hyperlinks) ===
    • #info === [COMPLETE] downey Migrate the member table from https://fedoraproject.org/wiki/CommOps#Interest_Areas to https://fedoraproject.org/wiki/CommOps/Members ===


  • #topic Tickets
    • #link https://pagure.io/fedora-commops/issues?tags=meeting
    • #info === Ticket #19 ===
      • #info "Improve automation of Elections communication"
      • #link https://pagure.io/fedora-commops/issue/19
      • New ticket to the meeting agenda! This one focuses on Fedora Elections that happen (roughly) each release cycle. Focusing on ways to improve automation, but first steps maybe identifying key steps in communication (e.g. what makes an election more obvious)? Can we improve how the questionnaire is collected? jkurik and bee2502 may have thoughts here. The CommOps workshop also was helpful for this.
    • #info === Ticket #34, 52, 84 ===
    • #info === Ticket #67 ===
      • #info "[Objective] Owning the Release Announcements Process"
      • #link https://pagure.io/fedora-commops/issue/67
      • Older ticket about an objective for CommOps, but wanted to raise to discussion. Release announcements are a uniquely marketing task… doesn't seem like writing them fits along with CommOps tasks. However, there are inefficiencies with communication between working groups / SIGs for new info in release. Are there ways we could maybe help improve the communication flow between these groups and Marketing?
    • #info === Ticket #83 ===
      • #info "replace/improve etherpad working space"
      • #link https://pagure.io/fedora-commops/issue/83
      • Etherpads are inefficient and sometimes unstable for hosting data. They can become sprawling and are better as temporary workspaces. What tooling could CommOps use instead of Etherpads (or in supplement to Etherpads) to make sure data is preserved and stored safely, without sacrificing accessibility and convenience?
    • #info === Ticket #86 ===
      • #info "Adjust meeting time by 30 minutes"
      • #link https://pagure.io/fedora-commops/issue/86
      • We delayed the meeting by 30 minutes today, but can we vote to make this official? Can update and close ticket after this meeting.


  • #topic Wiki Gardening




  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting