From Fedora Project Wiki

Revision as of 13:24, 3 May 2016 by Jflory7 (talk | contribs) (Finish meeting agenda)

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-05-03

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

Error creating thumbnail: File missing
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-05-03)
  • #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-04-26/commops.2016-04-26-15.57.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 === decause fill up the LimeSurvey account with $$$ ===
    • #info === [COMPLETE] decause / jflory7 Ping Marketing mailing list about Alpha to Beta release announcement research for May 3rd ===
    • #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 === [IN PROGRESS] decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
      • #action decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog
    • #info === [COMPLETE] CommOps / jflory7 Create tickets for items 1-3 from Ticket #69 so they can be assigned and broken up among CommOps members ===
      • #info Tickets not filed, but work on this ticket was accomplished at the last hack session
    • #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 === [INCOMPLETE] 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 ===


  • #topic Tickets
    • #link https://fedorahosted.org/fedora-commops/report/9
    • #info === Ticket #34, 49 ===
      • #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
      • #info #49: "[Onboarding Series] Infrastructure"
      • #link https://fedorahosted.org/fedora-commops/ticket/34
      • #link https://fedorahosted.org/fedora-commops/ticket/49
      • #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
      • Mostly working through previous items and getting up to speed (not much new to report). Last action item was to refine our own Join process as the testing bed for the onboarding process badges. Do we want to do any other planning now or continue to work through the existing queue of tasks?
    • #info === Ticket #68 ===
    • #info === Ticket #69 ===
      • #info "Fedora Modularity onboarding"
      • #link https://fedorahosted.org/fedora-commops/ticket/69
      • #info (1) Someone can review the contents of their on-boarding wiki page and pass feedback about them in the ticket, as compared to other on-boarding methods in Fedora
      • #info (2) Putting together a badge proposal for membership in the Modularity WG (in the form of a ticket on the fedora-badges Trac)
      • #info (3) A Community Blog article announcing the presence of the Modularity WG, what they are, what they do, how to get involved (penned by one of the WG members)
      • #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
      • A lot of progress was made at the last hack session. The wiki page was reviewed, a few edits were made, and a lot of future planning for how the Modularity WG badges could work was planned out. These details are further explained in jflory7's last comment in Ticket #69. Are there any more action items we want to take this week on this one?
    • #info === Ticket #71 ===
      • #info "Centralizing Ambassadors / Events resources and utilities"
      • #link https://fedorahosted.org/fedora-commops/ticket/71
      • This ticket has to do with bringing together several different resources and tools for Ambassadors and events into a single place. zoltanh721 also left feedback on this ticket (was originally filed in the Marketing Trac). jflory7 was to open discussion on the list, but if we have time, we can visit the ticket in the meeting.





  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting