From Fedora Project Wiki

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-11-29

Meeting Time


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.


CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-11-29)
  • #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 [ ]
    • 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
    • #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 Open up discussion about Fedora Appreciation Day date on the mailing list ===
    • #info === jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket ===
    • #info === jflory7 Post to the mailing list breaking down how to help with Ticket #93 ===
    • #info === Rhea Update the #95 ticket after the first dotnet meeting ===
    • #info === FranciscoD work on "Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.)." ===

  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting