From Fedora Project Wiki

(Add Community Blog section)
(Add tickets)
Line 64: Line 64:
* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://fedorahosted.org/fedora-commops/report/9
** #link https://fedorahosted.org/fedora-commops/report/9
** #info === Ticket #xx ===
** #info === Ticket #79 ===
*** #info ""
*** #info "Flock 2016 CommOps Workshop"
*** #link https://fedorahosted.org/fedora-commops/ticket/xx
*** #link https://fedorahosted.org/fedora-commops/ticket/79
*** description
*** #link https://fedoraproject.org/wiki/CommOps/Flock_2016
** #info === Ticket #xx ===
*** #info Workshop is done, but some work needs to be done on post-workshop processing (e.g. turning notes into tickets / commits / posts / other things as necessary. jflory7 and bee2502 will work on taking the feedback from the workshop and converting it into more accessible data.
*** #info ""
*** #action jflory7 bee2502 Take workshop feedback and parse it into more accessiblr data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
*** #link https://fedorahosted.org/fedora-commops/ticket/xx
** #info === Ticket #25 ===
*** description
*** #info "Begin initiative to consolidate subgroup wiki pages"
** #info === Ticket #xx ===
*** #link https://fedorahosted.org/fedora-commops/ticket/25
*** #info ""
*** Any updates since last meeting?
*** #link https://fedorahosted.org/fedora-commops/ticket/xx
** #info === Tickets #34, 49 ===
*** description
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** #info #49: "[Onboarding Series] Infrastructure"
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #link https://fedorahosted.org/fedora-commops/ticket/49
*** #action jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop





Revision as of 16:10, 9 August 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-08-09

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-08-09)
  • #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 Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-07-26/commops.2016-07-26-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 === [COMPLETE] jflory7 Review and edit July 2016 Election retrospective post by jkurik after CommOps meeting ===
    • #info === skamath file a ticket on fedmsg repo for the mailman bug ===
    • #info === [INCOMPLETE] jflory7 Work on drafting an article about the Flock 2016 CommOps workshop for Community Blog ===
      • #info No longer relevant to do so... a post-workshop report would be better
      • #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
    • #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
      • #action jflory7 Review emails for pending posts on the CommBlog
      • There are more since Flock!
    • #info === [INCOMPLETE] jflory7 Write an article stub announcing Fedora 25's existence, separate from Rawhide today ===
      • #info No longer relevant... be more on top of things for Alpha






  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting