From Fedora Project Wiki

(Add announcements)
Line 51: Line 51:
 
*** #action commops Write a promo on the CommBlog about the ultimate women's Fedora t-shirt
 
*** #action commops Write a promo on the CommBlog about the ultimate women's Fedora t-shirt
 
*** #help jflory7 will be traveling this week and could use some help on this one - can just be a short, simple follow-up to this article: https://fedoramagazine.org/the-ultimate-fedora-t-shirt/
 
*** #help jflory7 will be traveling this week and could use some help on this one - can just be a short, simple follow-up to this article: https://fedoramagazine.org/the-ultimate-fedora-t-shirt/
** #info === skamath file a ticket on fedmsg repo for the mailman bug ===
+
** #info === [INCOMPLETE] skamath file a ticket on fedmsg repo for the mailman bug ===
 +
*** #action skamath file a ticket on fedmsg repo for the mailman bug
 
** #info === [IN PROGRESS] jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
 
** #info === [IN PROGRESS] jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
 
*** #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
 
*** #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop

Revision as of 16:05, 16 August 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-08-16

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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-08-16)
  • #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 === New metrics brainstorming wiki page ===
      • #link https://fedoraproject.org/wiki/CommOps/Metrics_Ideas
      • #info bee2502 has started working on generating some ideas on community metric generation. Check out the wiki page with more information on metric collection with regards to discussion at the CommOps Flock workshop there.
    • #info === "Docs Project update from Flock 2016" ===
      • #link https://communityblog.fedoraproject.org/docs-project-update-flock-2016/
      • #info On jflory7's "must read list of 2016" - very informative post about the state of the Fedora Docs team and adds a lot of insight into the issues they are facing and how they plan to overcome them. If you haven't been following the Docs team and want to see what's up in a single post, this is a good one to read.
    • #info === "Women in technology: Fedora campus presence" ===
    • #info === "Żegnajcie! Fedora Flock 2016 in words" ===
      • #link https://blog.justinwflory.com/2016/08/fedora-flock-2016/
      • #info jflory7's event report on Flock 2016. There's a section dedicated to the Fedora CommOps workshop and feedback related to the workshop. It may be worth a read for anyone interested in the workshop and what kinds of results we got out of holding it.


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-08-09/commops.2016-08-09-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 === [INCOMPLETE] jflory7 Write a promo on the CommBlog about the ultimate women's Fedora t-shirt ===
      • #action commops Write a promo on the CommBlog about the ultimate women's Fedora t-shirt
      • #help jflory7 will be traveling this week and could use some help on this one - can just be a short, simple follow-up to this article: https://fedoramagazine.org/the-ultimate-fedora-t-shirt/
    • #info === [INCOMPLETE] skamath file a ticket on fedmsg repo for the mailman bug ===
      • #action skamath file a ticket on fedmsg repo for the mailman bug
    • #info === [IN PROGRESS] jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
      • #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
      • #info jflory7 and bee2502 did some parsing of info on Saturday from the workshop, but there's still a little more to do - jflory7 needs to start a draft in the CommBlog next
    • #info === [IN PROGRESS] jflory7 Review emails for pending posts on the CommBlog ===
      • #action jflory7 Review emails for pending posts on the CommBlog
      • #info This is getting done every week, but there's a consistent amount of more coming in each week for new posts and authors, which is awesome. :)
    • #info === [IN PROGRESS] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
      • #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
      • #info jflory7 and bee2502 did some parsing of info on Saturday from the workshop, but there's still a little more to do - jflory7 needs to start a draft in the CommBlog next
    • #info === [INCOMPLETE] jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop ===
      • #action jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop
    • #info === [COMPLETE] jflory7 Close ticket#80 ===
    • #info === [COMPLETE] jflory7 Follow up with nardasev ASAP on whether this one is still good to publish post-Flock ===
    • #info === [INCOMPLETE] jflory7 Update guide for writing a new article based on what's actually happening in 2016 now ===
      • #action jflory7 Update guide for writing a new article based on what's actually happening in 2016 now


  • #topic Tickets
    • #link https://fedorahosted.org/fedora-commops/report/9
    • #info === Ticket #81 ===
      • #info "Migrating to Pagure"
      • #link https://fedorahosted.org/fedora-commops/ticket/81
      • #info It is now possible for us to migrate from Trac to Pagure (the importer tool was recently completed by cverna). A staging repo of what the import looks like exists on the Pagure staging instance. Since we now have the tooling, we should set a hard date for migrating the entire Trac over to Pagure and begin retiring it. Rough timeline detailed in ticket.
      • #link https://stg.pagure.io/stg-fedora-commops/issues
      • #idea Migration date: Mon, 2016 Aug 29? +1/0/-1?
    • #info === Ticket #78 ===
      • #info "Automating a check-in to evaluate activity of members"
      • #link https://fedorahosted.org/fedora-commops/ticket/78
      • #info Two ways to do it: Infra-style with a manual post sent monthly, or could use Fedocal to automate this once a month as check-in calendar event to query members on regular, consistent basis. Non-responders would be removed from the FAS group hypothetically. Need to discuss implementation and if this is something we want to do.
      • #idea Would this be necessary for active members to also complete every month? Is it better to separate into two "groups" - apprentices and regular members?
    • #info === Ticket #10 ===
      • #info "CommOps vFAD 2016"
      • #link https://fedorahosted.org/fedora-commops/ticket/10
      • #info Based on Flock outcome, likely reasonable to begin planning out our own FAD event. Can opt for an in-person FAD at first, and if necessary, fall back to virtual event. Would be held in 2017 (after February / March when budget for next fiscal year allocated). First steps would be for defining purpose and matching up to outcomes and results that align with Fedora mission. We can start now by using mattdm's logic model template and identifying key areas for us to focus on as team.
      • #link https://pagure.io/FedoraLogicModelTemplate
    • #info === Ticket #70 ===
      • #info "FOSS Student Pack"
      • #link https://fedorahosted.org/fedora-commops/ticket/70
      • #info Key thing to get out of this is less on physical / costly items, more on providing resources / tools to point people towards contributing to open source and subsequently Fedora, e.g. IRC client, bouncer service, development tools, software in Fedora, etc.)
      • #idea Key to the gate: FAS account (guide to register and what a FAS account gives you access to)
      • #idea Java IDE: Eclipse
      • #idea IRC client: HexChat (IRC beginner guide, how to use HexChat, etc.)
      • #idea Photo editing: DarkTable (what it does, guides for using it, etc.)
      • #idea Creating Fedora USB media: Whatever the preferred tool now is for creating media correctly and with stability (Fedora Media Writer?)
      • The list can go on…
    • #info === Tickets #34 ===
      • #info #34: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
      • #link https://fedorahosted.org/fedora-commops/ticket/34
      • #info Infrastructure ticket put on hold while current blocking issues are resolved. More detail in the ticket. For now, we need to decide and focus on a new sub-project / team to focus on. jflory7 would like to propose the Python SIG as a team that is in need of some assistance and help. Having difficulties on-boarding new members effectively. Need to find ways for communicating this better and how to make it simpler for getting involved. See rough notes for Flock as a primer on this one.
      • #link https://etherpad.gnome.org/p/flock-2016-commops-workshop





  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting