From Fedora Project Wiki
Fedora CommOps Team Meeting Minutes 2016-06-07
Meeting Time
- 2016-06-07 16:00 UTC
- #fedora-meeting on freenode
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
CommOpsers, update this agenda with your latest items before the meeting has started.
- #startmeeting Fedora CommOps (2016-06-07)
- #meetingname commops
- #nick commops
- #chair <given to approved members of FAS group at meeting>
- #topic Agenda
- #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-07
- #info (1) Roll Call / Q&A
- #info (2) Announcements
- #info (3) Action items from last meeting
- #info (4) Tickets
- #info (5) Wiki Gardening
- #info (6) Community Blog
- #info (7) Release Schedule
- #info (8) Open Floor
- #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 === "Fedora Cloud FAD 2016" ===
- #link https://communityblog.fedoraproject.org/fedora-cloud-fad-2016/
- #info The Cloud FAD is happening now, from June 7 - 8. The Cloud Working Group will be making decisions, tackling tickets, and writing code to help with topics like automated testing, documentation, and increasing the public cloud provider footprint.
- #info === "Fedora Design Team lead Máirín Duffy wins O’Reilly Open Source Award" ===
- #link https://communityblog.fedoraproject.org/fedora-design-team-lead-mairin-duffy-wins-oreilly-open-source-award/
- #info Big congrats to mizmo for winning big at the O'Reilly Open Source Conference (OSCON) this year! Check out the article to learn more about the award.
- #info === Fedora 24 releases June 14 ===
- #info Just in case you forgot, Fedora 24 drops in another seven days!
- #info === "Fedora Cloud FAD 2016" ===
- #topic Action items from last meeting
- #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-31/commops.2016-05-31-15.56.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 Follow up with tatica and diversity team about LimeSurvey availability ===
- #info === [COMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
- #info === [COMPLETE] jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
- #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
- #info === decause nail down Flock arrangements, add them to Fedocal ===
- #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
- #info === decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push ===
- #info === [INCOMPLETE] skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. :) ===
- #action skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded
- #info === [COMPLETE] jflory7 Reach out to the Design Team about centralizing Design / Marketing resources for Fedora and get their thoughts about the discussions from today's meeting on Ticket #71 ===
- #info === [COMPLETE] jflory7 Update Ticket #71 with the ideas and discussion from this meeting ===
- #info === [COMPLETE] jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source ===
- #info === [COMPLETE] jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session ===
- #topic Tickets
- #link https://fedorahosted.org/fedora-commops/report/9
- #info === Ticket #10 ===
- #info "CommOps vFAD 2016"
- #link https://fedorahosted.org/fedora-commops/ticket/10
- #link https://fedoraproject.org/wiki/FAD_CommOps_2016
- In December, we began discussing the idea of a CommOps vFAD but were going to shelf until we grew some more and after the summer began. Now that we're getting into June, we began discussing this at our last meeting. A wiki page template was started for our vFAD. The next steps should be deciding the objectives and what we wish to accomplish for the CommOps vFAD.
- #info === Tickets #34, 49, 69 ===
- #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
- #info #49: "[Onboarding Series] Infrastructure"
- #info #69: "Fedora Modularity onboarding"
- #link https://fedorahosted.org/fedora-commops/ticket/34
- #link https://fedorahosted.org/fedora-commops/ticket/49
- #link https://fedorahosted.org/fedora-commops/ticket/69
- #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
- At the last meeting, skamath was going to create a ticket the CommOps on-boarding badge and we were going to focus efforts on that one as the "first run" of an on-boarding badge series. Next steps for moving on?
- #info === Ticket #71 ===
- #info "Centralizing Ambassadors / Events resources and utilities"
- #link https://fedorahosted.org/fedora-commops/ticket/71
- Feedback was asked for on the Design Team, and a few replies were given back this morning. Some efforts were already started to centralize the resources, but the Design Team has a strong preference on Ambassadors consulting with Design Team members first before printing (as compared to self-producing). This helps ensure the quality of the final product and that it properly represents the Fedora brand. Maybe an alternative to original problem in the ticket is making a more clear and guided process for what Ambassadors should do to request design assets?
- #link https://pagure.io/designassets/tree/master
- #topic Wiki Gardening
- #action commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
- #topic Community Blog
- #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
- #info === This Week in CommBlog ===
- #info (1) "Fedora CommBlog Keeps it 100"
- #link https://communityblog.fedoraproject.org/commblog-keeps-100/
- #info Total Views (June 2 - June 7): 53
- #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1582
- #info (2) "Fedora Cloud FAD 2016"
- #link https://communityblog.fedoraproject.org/fedora-cloud-fad-2016/
- #info Total Views (June 4 - June 7): 39
- #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1618
- #info (3) "OSCON 2016 Expo Hall Booth Report"
- #link https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/
- #info Total Views (June 6 - June 7): 40
- #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1558
- #info (4) "Fedora Design Team lead Máirín Duffy wins O’Reilly Open Source Award"
- #link https://communityblog.fedoraproject.org/fedora-design-team-lead-mairin-duffy-wins-oreilly-open-source-award/
- #info Total Views (June 6 - June 7): 71
- #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1615
- #info (1) "Fedora CommBlog Keeps it 100"
- #info === Coming Up in CommBlog ===
- #info (1) "Getting started with Fedora QA (Part 1)"
- #link https://communityblog.fedoraproject.org/?p=1608&preview=1&_ppp=cc40c9d0e6
- #info Scheduled for Thursday, June 9, 8:00 UTC
- #info (2) "Getting started with 'update-testing' Fedora QA part 2"
- #info (3) "Getting started with Fedora QA part 3"
- #info (4) "Event Report: PyCon 2016"
- #info (1) "Getting started with Fedora QA (Part 1)"
- #topic Release Schedule
- #topic Open Floor
- #info skamath Introduce the summer-coding stats tool
Meeting summary and action items
Full meeting log
Next Meeting
- 2016-06-14 16:00 UTC in #fedora-meeting