From Fedora Project Wiki

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-05-17

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-17)
  • #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 Announcements
    • #info === GSoC project period begins Monday, May 23 ===
    • /me hasn't been around much this week to know of any other announcements :)


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-10/commops.2016-05-10-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 === decause fill up the LimeSurvey account with moneydollars ===
    • #info === [COMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
    • #info === [COMPLETE] 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 === [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 === [COMPLETE] skamath add categories to the Summer Coding 2016 page ===
    • #info === jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
    • #info === [COMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
    • #info === [COMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
    • #info === [COMPLETE] dhanesh95 Work on merging the draft changes for the University Involvement Initiative into the main page (including in the section header "Proposed") ===
    • #info === [COMPLETE] jflory7 / decause Drop ticket comment in #fedora-modularization after meeting ===
    • #info === [COMPLETE] skamath File an issue in the Community Blog repo for adding a footer with licensing information to the bottom of the site ===
    • #info === [IN PROGRESS] decause get the tshirt orders in ASAP for PyCon ===
      • #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
    • #info === [IN PROGRESS] decause get the sticker orders in ASAP for PyCon ===
      • #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
    • #info === [COMPLETE] LinuxHippie Work on creating a first draft of the PyCon 2016 page on the wiki, drop mail on the mailing list once an initial draft is ready for decause and other attendees to review ===
    • #info === [INCOMPLETE] jflory7 Help ship F24 Party article for Thursday morning (Wednesday if possible) ===
      • #action jflory7 Ship F24 Party article today
    • #info === omiday Contact the Infrastructure team in IRC or mailing list about point of contact for Ask Fedora and about adding banners for Magazine and/or CommBlog ===


  • #topic Tickets
    • #link https://fedorahosted.org/fedora-commops/report/9
    • #info === Tickets #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
      • A Badges workshop was officially proposed this morning on the CommOps and Design mailing list. This is the first steps to moving forward on these items (since there has been a lull for the past week or two since others have been away / busy). A hack session tonight or tomorrow might be useful to do some moving forward on this ticket, finalizing a Badges workshop with the Design team, and also getting through our own backlog. If a hack session works well, when do we want to aim for?
    • #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
      • The Modularity WG is currently reviewing the feedback on the ticket as of this morning. They may have comments by the time this ticket rolls around in the meeting.
    • #info === Ticket #74 ===





  • #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-17&oldid=446783"