From Fedora Project Wiki

Revision as of 04:31, 22 March 2016 by Jflory7 (talk | contribs) (Create an empty, unchanged template from last week's meeting)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-03-22

Meeting Time

Participants

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

  • 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-03-22)
  • #meetingname commops
  • #chair <based on meeting attendance>
  • #topic Agenda
  • #topic Roll Call
    • #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!


  • #topic Announcements
    • #info === No tickets closed this week ===
    • #info === Ticket #21 ===
      • #link https://fedorahosted.org/fedora-commops/ticket/21
      • #info * "Ambassadors - Event Report Template"
      • #info This ticket is open for anyone to claim and start working on. The idea is that we have a recommended "format" for Ambassadors to use for writing event reports of places that they represent Fedora at. This is a *great* task for someone who wants to get involved and either has experience as a Fedora Ambassador or going to other events as open source representatives. If this interests you, ask to claim this ticket at Open Floor or on the mailing list!
    • #info === Ticket #26 ===
      • #link https://fedorahosted.org/fedora-commops/ticket/26
      • #info * "Mailing lists analysis and graphs"
      • #info This ticket is also open; another *great* ticket for someone new who wants to get involved. Ticket looks at mailing list activity in Fedora with fedmsg and tries to try conclusions from that data. If this interests you, ask to claim this ticket at Open Floor or on the mailing list!
    • #info === Ticket #45 ===
      • #link https://fedorahosted.org/fedora-commops/ticket/45
      • #info * "Talking Points: Python"
      • #info Ticket needs collaboration! Cross-effort between Marketing and CommOps. 2016 is the Year of Python in Fedora! If you have experience with working on Python in Fedora, your input is needed and valued for this ticket for helping come up with ideas and points about why working on Python in Fedora makes your life easier. If this interests you, ask to help on this ticket at Open Floor or on the mailing list!
    • #info === Ticket #59 ===
      • #link https://fedorahosted.org/fedora-commops/ticket/59
      • #info * "Modernization of Trac wiki page"
      • #info Justin (jflory7) and Ryan (masetrax) have been collaborating over email on this ticket; masetrax will become the new owner and is looking at bringing the Trac wiki page "up to date" for 2016. Thanks for taking this on, Ryan!
    • #info === Google Summer of Code announced on Community Blog ===


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-03-08/commops.2016-03-08-16.55.html
    • #info * #info How This Works: Simple, completed action items from previous week are not brought up; action items that were either important tasks or have an unclear or incomplete status are brought up again for an update or to be given an #action again
    • #info === decause Let us know in #fedora-commops if the mailing list announcement about the Fedora Diversity Adviser position is ready to ship ===
    • #info === [COMPLETE] jflory7 Draft up a GSoC announcement post confirming Fedora's participation and linking to the essential pages [DUE: March 11] ===
    • #info === [INCOMPLETE] jflory7 Begin writing small pieces of the Trac for Beginners article this week ===
      • jflory7 did not complete, but Ryan (masetrax) is actively working on the Trac pieces and is going to claim Ticket #59 while he makes progress
    • #info === bee2502_ Finish up on the fedmsg2gource article, share with CommOps, and push out this week ===
    • #info === jflory7 Work with bee2502 on fedmsg2gource article ===
    • #info === decause follow up with noriko/pravis about commblog announcement ===
    • #info === [INCOMPLETE] jflory7 Convert Etherpad => Tickets ===




  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting