Meeting:CommOps 2017-04-11

Fedora CommOps Team Meeting Minutes 2017-04-11

Meeting Time

• 2017-04-11 17:30 UTC
• #fedora-meeting on freenode

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

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 Agenda
  • #link https://fedoraproject.org/wiki/Meeting:CommOps_2017-04-11
  • #info (1) Roll Call / Q&A
  • #info (2) Announcements
  • #info (3) Action items from last meeting
  • #info (4) Tickets
  • #info (5) Community Blog
  • #info (6) 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 === "Fedora Council FAD Report – 2017/2018 Initial Steps" ===
    • #link https://communityblog.fedoraproject.org/fedora-council-fad-2017-report/
    • #info The Fedora Council held their FAD from 26-28 March. During the FAD, they tackled some key areas of interest across the project. This is one part of a series of posts (to come). Important information for any contributor to review.
  • #info === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info

• #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 ===
    • #link https://pagure.io/fedora-commops/issue/70#comment-435022
  • #info === [ONGOING] commops Review and leave feedback on ticket for CommOps Google Summer of Code slot https://pagure.io/fedora-commops/issue/105 ===
    • #action 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 Tickets
  • Open ticket meeting - let's find some issues to work on over the next few months that are exciting and that people want to work on. This will help fill the gaps too when jwf becomes inactive next month.
  • #link https://pagure.io/fedora-commops/issues?tags=meeting
  • #info === Ticket #70: "FOSS Student Pack" ===
    • #link https://pagure.io/fedora-commops/issue/70

• #topic Community Blog
  • #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
  • #info === This Week in CommBlog ===
    • #info (1) "Mission to understand: Fedora Diversity FAD 2017" - jflory7
      • #link https://communityblog.fedoraproject.org/fedora-diversity-fad-2017/
      • #info Total Views (April 10 - April 11): 74
      • #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3666
    • #info (2) "Participate in Fedora 26 translation sprint" - pravins++
      • #link https://communityblog.fedoraproject.org/fedora-26-translation-sprint/
      • #info Total Views (April 10 - April 11): 316
      • #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3706
    • #info (3) "Fedora Council FAD Report – 2017/2018 Initial Steps" - bex++
      • #link https://communityblog.fedoraproject.org/fedora-council-fad-2017-report/
      • #info Total Views (April 11): 73
      • #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3692
  • #info === Coming Up in CommBlog ===
    • #info (1) "Fedora at Technologix 2017"
      • #link https://communityblog.fedoraproject.org/?p=3647&preview=1&_ppp=ccf4d8ed4f
    • #info (2) "Fedora User Handbook"
      • #link https://communityblog.fedoraproject.org/?p=3688&preview=1&_ppp=6a9574e678
    • #info (3) "Heroes of Fedora (HoF) - F26 Alpha"
      • #link https://communityblog.fedoraproject.org/?p=3716&preview=1&_ppp=e7961702f9
    • #info (4) "[Test Day Report] Anaconda Blivet GUI"
      • #link https://communityblog.fedoraproject.org/?p=3733&preview=1&_ppp=b2ff8cf18e

• #topic Open Floor

Next Meeting

• 2017-04-18 17:30 UTC in #fedora-meeting