From Fedora Project Wiki

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-10-18

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-10-18)
  • #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 Announcements
    • #info === FUDCon LATAM ===
      • #link
      • #info FUDCon LATAM ended last week. Fedora contributors from all around the globe flocked to Puno, Perú for speaker talks, workshops, and collaboration to advance Fedora and its Four Foundations. You can read more in the Community Blog post, and there should be event reports popping up soon.
    • #info === "Fedora 25 Supplementary Wallpapers: Vote now!" ===
    • #info === In the news: "Fedora 25 Beta Resets the Linux Performance Bar" ===
      • #link
      • #info LinuxInsider covers some of the latest features and changes in the Fedora 25 Beta, and includes comments and a brief interview from mattdm. This article highlights many of the talking points generated in the past few weeks. It's clear they're making it easy for everyone to talk about what's new in Fedora 25!

  • #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 === [COMPLETE] jflory7 Promote Outreachy article on social media channels for final week of applications ===
    • #info === skamath Follow up with Infrastructure team on fas=>bz email lookup rules and whether a fix can be made to gracefully handle failed lookups ===
    • #info === [INCOMPLETE] jflory7 File ticket for looking 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 ===
    • #info === [INCOMPLETE] jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day ===
    • #info === [INCOMPLETE] jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process ===
    • #info === [INCOMPLETE] jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list ===
    • #info === [COMPLETE] jflory7 Create initial wiki page for EDU talking points, share in ticket ===
    • #info === skamath open a new ticket with information about g11n onboarding with inputs from pravins ===

  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting