Meeting:CommOps 2016-05-24

Fedora CommOps Team Meeting Minutes 2016-05-24

Meeting Time

• 2016-05-24 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-24)
• #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-24
  • #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 === "Flock 2016 schedule is now out" ===
    • #link https://fedoramagazine.org/flock-2016-schedule-now/
    • #info Flock is Fedora's annual contributor conference where Fedorans across the world get together for talks, sprints, workshops, and more. The schedule for this year's Flock was recently published and you can find out what talks and workshops there will be for this year. Some CommOpsers are giving talks this year!
  • #info === "" ===
    • #link
    • #info
  • #info === "" ===
    • #link
    • #info

• #topic Action items from last meeting
  • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-17/commops.2016-05-17-16.02.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 === ===
  • #info === ===
  • #info === ===
  • #info === ===
  • #info === ===

   commops add the 'how it works' link above to the etherpad under resources
   decause send out timeslot requests for GSoC
   decause add money dollars to limesurvey due:Friday
   CommOps solidify onboarding steps before 5/23 internships begin
   decause talk to spot about scheduling an EDU FAD after budget gets settled
   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
   jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
   jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
   jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
   jflory7 Ship F24 Party article today
   jflory7 add morning workshop to fedocal
   decause attend morning workshop at 13:30UTC tomo
   CommOps Fork a wiki page for the Education FAD from the template linked previously and begin templating the details for the Education FAD to take place over this summer
   jflory7 Remove Ticket #74 from meeting agenda, add info about where to find the pull request for the ticket
   CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
   decause / commops stop by the docs office hours tomo to discuss release notes -> release announce flow
   decause add conf schedule to Fedocal
   dhanesh95 Fork a wiki page for the Education FAD from the template linked previously and begin templating the details for the Education FAD to take place over this summer

• #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 24: Let's have a party!"
      • #link https://communityblog.fedoraproject.org/fedora-24-have-a-party/
      • #info Total Views (May 24): [ no statistics generated yet, just published ]
      • #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1496
  • #info === Coming Up in CommBlog ===
    • #info (1) "Fedora at Bitcamp 2016"
    • #info (2) "DevConfCZ 2016: Event Report"
      • #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=81757dedb9

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

• #topic Open Floor

Next Meeting

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