From Fedora Project Wiki

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2017-04-11

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 (2017-04-11)
  • #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 Announcements
    • #info === "Fedora Council FAD Report – 2017/2018 Initial Steps" ===
    • #info === "Mission to understand: Fedora Diversity FAD 2017" ===
      • #link https://communityblog.fedoraproject.org/fedora-diversity-fad-2017/
      • #info The Diversity Team held their first FAD at the end of January. They worked on a few topics to help better understand the community and promote positive behavior that follows the spirit of being excellent to each other. Read the full details in the event report.
    • #info === "Participate in Fedora 26 translation sprint" ===


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2017-04-04/commops.2017-04-04-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 === [PENDING] jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports ===
      • #info Decided that this ticket is best communicated and shared with FAmSCo - intend to migrate this ticket out of CommOps and start discussion with FAmSCo
    • #action jwf File ticket upstream with FAmSCo about Ambassador event reports
    • #info === [COMPLETE] jwf Add comment to ticket #70 explaining our discussion and focus of student pack, give examples of questions, post to mailing list asking for comments ===
    • #info === [ONGOING] commops Review and leave feedback on ticket for CommOps Google Summer of Code slot https://pagure.io/fedora-commops/issue/105 ===
    • #info === [COMPLETE] jwf Investigate why like / share buttons have gone MIA in Magazine / CommBlog ===
      • #info Community Blog upgraded, should be fixed now




  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting

Retrieved from "https://fedoraproject.org/w/index.php?title=Meeting:CommOps_2017-04-11&oldid=490664"