From Fedora Project Wiki

Revision as of 19:02, 13 October 2016 by Jflory7 (talk | contribs) (Add minutes and logs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Fedora CommOps Team Meeting Minutes 2016-10-11

Meeting Time

Participants

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

  • 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-10-11)
  • #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
    • #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
    • 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 === "Announcing the Release of Fedora 25 Beta" ===
      • #link https://fedoramagazine.org/announcing-release-fedora-25-beta/
      • #info Fedora 25 is available for download and upgrading. To learn more about the technical changes in Fedora this release, read the announcement on the Fedora Magazine for more information. The targeted final release date (currently) is November 15.
    • #info === "Outreachy with Fedora, Fall 2016" ===
    • #info === "AppData content ratings for games shipped in Fedora" ===
    • #info === Modularity WG on-boarding complete! ===


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-10-04-16.30.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] adityakonarde Create a first draft of a Fedora + Outreachy Fall 2016 post by Thursday evening, share link with the CommOps mailing list when ready for review ===
    • #info === [COMPLETE] skamath Open a ticket in the Fedora Infrastructure Pagure repo proposing the idea of officially migrating all Fedora apps projects to Pagure and deprecating the use of GitHub ===
    • #info === skamath Work with fedbadges#491 to write the badges rule file for giving a badge to people who file bugs in Bugzilla ===
    • #info === [INCOMPLETE] jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83 ===
      • #action jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83
    • #info === [INCOMPLETE] jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards ===
      • #action jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards
    • #info === [INCOMPLETE] jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article ===
      • #action jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article
    • #info === [INCOMPLETE] jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day ===
      • #action jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day
    • #info === [COMPLETE] FranciscoD Look into creating a .thank command for zodbot that thanks a specified contributor for doing awesome work ===
    • #info === [COMPLETE] jflory7 Close ticket #81 about Pagure migration ===
    • #info === [INCOMPLETE] jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process ===
      • #action jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process


  • #topic Tickets
    • #link https://pagure.io/fedora-commops/issues?tags=meeting
    • #info === Ticket #92 ===
      • #info "Start a yearly Fedora Appreciation Day"
      • #link https://pagure.io/fedora-commops/issue/92
      • #info CommBlog post still to be written. Looking at comments in ticket, bexelbie's approach as a soft-launch seems to make the most sense (i.e. encouraging contributors to thank one another on this day).
    • #info === Ticket #44 ===
      • #info " Talking Points: EDU"
      • #link https://pagure.io/fedora-commops/issue/44
      • #info Older ticket, but hasn't been visited in a while. Similar to Fedora release talking points, EDU-related talking points would be bullets or key points about why contributing to open source and Fedora as a student, faculty member, or or staff member is worthwhile. This covers a variety of different angles.
    • #info === Ticket #34 ===




  • #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-10-11&oldid=477049"