Fedora CommOps Team Meeting Minutes 2017-01-24

Meeting Time

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

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.

#topic Agenda
- #link https://fedoraproject.org/wiki/Meeting:CommOps_2017-01-24
- #info (1) Roll Call / Q&A
- #info (2) Announcements
- #info (3) Action items from last meeting
- #info (4) Tickets
- #info (5) Community Blog - skipping today, but will be back next week!
- #info (5) Open Floor

#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 Announcements
- #info === "Elections Retrospective, January 2017" ===
  - #link https://communityblog.fedoraproject.org/elections-retrospective-january-2017/
  - #info jkurik combined a brief retrospective of the past election cycle. This was one of the top participated elections of Fedora history! Awesome job for everyone involved with the election process. The feedback in this post will be helpful for a later analysis of the election cycle and seeing what we can do better for next time.
- #info === Upcoming travel arrangements ===
  - #info DevConf (27-29 Jan.) and FOSDEM (3-5 Feb.) are coming up soon. As a result, many people may be away or busy for the next couple of weeks, so be aware activity may slow down a little in some parts of the project until after the two conferences.

#topic Action items from last meeting
- #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-01-17-17.28.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 === Rhea Post on Reddit with the Election results ===
- #info === bt0 to try to get a list of Fedora contributors & talks out of FOSDEM calendar ===