Meeting:CommOps 2016-05-10

Fedora CommOps Team Meeting Minutes 2016-05-10

Meeting Time

• 2016-05-10 16:00 UTC
• #fedora-meeting on freenode

Participants

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

• 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 (2016-05-10)
• #meetingname commops
• #nick CommOps
• #chair <given to approved members of FAS group at meeting>

• #topic Agenda
  • #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-10
  • #info (1) Roll Call / Q&A
  • #info (2) Announcements
  • #info (3) Action items from last meeting
  • #info (4) Tickets
  • #info (5) Wiki Gardening
  • #info (6) Community Blog
  • #info (7) Release Schedule
  • #info (8) Open Floor

• #topic Roll Call / Q&A
  • #info Name; Timezone; Sub-projects/Interest Areas
  • 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 === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info

• #topic Action items from last meeting
  • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-03/commops.2016-05-03-15.55.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 === [INCOMPLETE] decause / jflory7 create a quick pointer to the DOCs FAD Wiki for commblog ===
    • #info Deadline passed for announcement about Docs FAD - can we get an event report up?
  • #info === decause fill up the LimeSurvey account with moneydollars ===
  • #info === [INCOMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
    • #action jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team
  • #info === [INCOMPLETE] decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
    • #action decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog
  • #info === CommOps solidify onboarding steps before 5/23 internships begin ===
    • #action CommOps solidify onboarding steps before 5/23 internships begin
  • #info === decause talk to spot about scheduling an EDU FAD after budget gets settled ===
  • #info === [INCOMPLETE] jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad ===
    • #action jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad
  • #info === [INCOMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
    • #action jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
  • #info === jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
    • #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
  • #info === skamath help with gardening of Summer Coding wiki ===
  • #info === CommOps start a stub for a vFAD over the summer (before Flock) ===
  • #info === [INCOMPLETE] jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
  • #info === [INCOMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
  • #info === [COMPLETE] jflory7 Schedule "Python + Fedora brochures" article for Thursday ===
    • #link https://communityblog.fedoraproject.org/fedoras-love-python-continues/
  • #info === [COMPLETE] jflory7 Check in with gnokii about when to ship the F24 Release Parties article ===
  • #info === [COMPLETE] jflory7 Ping mailing lists about F24 Beta Release Announcement again, deadline: Friday ===
    • decause++
    • #link https://pagure.io/fedora-mktg/blob/master/f/release-announcements/f24/beta
  • #info === [INCOMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
    • #action jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list
  • #info === [INCOMPLETE] drewmeigs check in with decause and jflory7 on meeting agendas and Meetbot ===
    • This one was on jflory7
    • #action jflory7 Pass information to drewmeigs about preparing next week's meeting agenda

• #topic Tickets
  • #link https://fedorahosted.org/fedora-commops/report/9
  • #info === Ticket #xx ===
    • #info ""
    • #link
    • description
  • #info === Ticket #xx ===
    • #info ""
    • #link
    • description
  • #info === Ticket #xx ===
    • #info ""
    • #link
    • description

• #topic Wiki Gardening
  • #action CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]

• #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) "Fedora's Love For Python Continues"
      • #link https://communityblog.fedoraproject.org/fedoras-love-python-continues/
      • #info Total Views (May 5 - May 9): 102
      • #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1470
  • #info === Coming Up in CommBlog ===
    • #info (1) "Fedora 24: Let’s have a party!"
      • #link https://communityblog.fedoraproject.org/?p=1496&preview=1&_ppp=a34697b353
    • #info (2) "Event Report: Fedora Docs FAD"
      • #link https://communityblog.fedoraproject.org/?p=1511&preview=1&_ppp=b48bef9a25
    • #info (3) "Fedora at Bitcamp 2016"
      • #info In progress, jflory7 to assist in writing this one
    • #info (4) "DevConfCZ 2016: Event Report"
      • #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=97da4ae90c

• #topic Release Schedule
  • #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html

• #topic Open Floor

Next Meeting

• 2016-05-17 16:00 UTC in #fedora-meeting