From Fedora Project Wiki

(Add Community Blog)
(Add tickets)
Line 72: Line 72:
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #info === Ticket #34 ===
** #info === Ticket #34 ===
*** #info ""
*** #info "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** #link https://pagure.io/fedora-commops/issue/34
*** #link https://pagure.io/fedora-commops/issue/34
*** description
** #info === Ticket #81 ===
** #info === Ticket #xx ===
*** #info "Migrating to Pagure"
*** #info ""
*** #link https://pagure.io/fedora-commops/issue/81
*** #link https://pagure.io/fedora-commops/issue/xx
** #info === Ticket #90 ===
*** description
*** #info "Improving Fedora Elections Process"
** #info === Ticket #xx ===
*** #link https://pagure.io/fedora-commops/issue/90
*** #info ""
** #info === Ticket #92 ===
*** #link https://pagure.io/fedora-commops/issue/xx
*** #info "Start a yearly Fedora Appreciation Day"
*** description
*** #link https://pagure.io/fedora-commops/issue/92
** #info === Ticket #xx ===
*** #info ""
*** #link https://pagure.io/fedora-commops/issue/xx
*** description





Revision as of 16:36, 4 October 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-10-04

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-10-04)
  • #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 Action items from last meeting
    • #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-09-27-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 === [INCOMPLETE] jflory7 Write an introductory post for Outreachy 2016 on the CommBlog ===
    • #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
      • #info All pending review posts in the Community Blog are currently reviewed and scheduled!
    • #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 === [INCOMPLETE] jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83 ===
      • #action 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 === [INCOMPLETE] jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards ===
      • #action jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards
    • #info === [INCOMPLETE] 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) ===
      • #action [INCOMPLETE] 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 Open Floor

Meeting summary and action items

Full meeting log

Next Meeting