From Fedora Project Wiki

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-05-31

Meeting Time

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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-05-31)
  • #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
    • 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 Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-24/commops.2016-05-24-15.58.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 === [COMPLETE] cprofitt File a ticket for wiki gardening the Python SIG page (others who have noticed things can also chime in, cc: LinuxHippie / dhanesh95) ===
    • #info === [IN PROGRESS] decause follow-up with tatica and diversity team about limesurvey avaiability ===
      • #action decause Follow up with tatica and diversity team about LimeSurvey availability
      • #info tatica has been offline due to illness, so might be a slight delay in getting this one done
    • #info === [IN PROGRESS] 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 Email draft is started, will be sent out by end of day
    • #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 === [CLOSED] jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
      • #info Article has gone past its prime publishing period (event was in early April); there are individual Ambassador reports for the event, so this should suffice for the time being.
    • #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 ===
      • #action jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
    • #info === [IN PROGRESS] decause work with jzb to possibly organize a release party in RDU
      • #action decause Work with jzb to organize the release party in Raleigh, NC area
    • #info === [COMPLETE] jflory7 Add info about where to find the pull request for Ticket #74
    • #info === [COMPLETE] decause / commops stop by the docs office hours tomo to discuss release notes -> release announce flow ===
      • #info decause and jflory7 stopped by for a bit to check in with the team and generate some ideas, more info to come.
    • #info === [IN PROGRESS...?] decause nail down Flock arrangements, add them to Fedocal ===
      • #action decause nail down Flock arrangements, add them to Fedocal
    • #info === [IN PROGRESS] decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
      • #action decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
    • #info === [COMPLETE] maxamillion log into commblog, create a draft for the OSCON report, and then review decause's edits ===
      • #info maxamillion is logged into the CommBlog and is the "author" of the post in the drafts folder
    • #info === [INCOMPLETE] decause input the report, make edits, clear with maxamillion, push before Friday Wheels Up for PyCon ===
      • #action decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push






  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting

Retrieved from "https://fedoraproject.org/w/index.php?title=Meeting:CommOps_2016-05-31&oldid=448665"