From Fedora Project Wiki

(Create meeting outline for future week)
 
(Complete agenda for today's meeting)
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Heroes of Fedora (HoF) – F23 Final" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/heroes-of-fedora-hof-f23-final/
*** #info  
*** #info Every release of Fedora, there's testers who help make sure the next release is tested and functioning as expected. The Heroes of Fedora series looks at who contributed to Fedora 23 Final testing by looking at Bodhi feedback on updates, release validation tests, and bug reports.
** #info === "" ===
** #info === "Southeast Linux Fest (SELF) 2016" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/southeast-linux-fest-self-2016/
*** #info  
*** #info The Southeast Linux Fest (SELF) is an annual Linux conference in the southeast region of the United States. The Fedora Ambassadors of North America attended this event as representatives of the project. Learn more in the event report.
** #info === "" ===
** #info === "Fedora Elections July 2016 - Campaign period has started" ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/Z5VUZ2BR4TN25QQJDPUEHUSNBGNC3QPS/
*** #info  
*** #info The Nomination period of Elections to Council and FESCo is now over. Nominees can now start with their own campaign, to attract people in the Fedora community. Like last time, all interviews will be published on the Community Blog.




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-07-05/commops.2016-07-05-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 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 === ===
** #info === [COMPLETE] jflory7 Continue working through Community Blog queue after receiving feedback from authors ===
** #info === ===
*** #info Article published today, good number coming out this week, still some more in the queue of being edited
** #info === ===
** #info === [COMPLETE] jflory7 Update Ticket #69 about Modularity WG on-boarding badge ticket ===
** #info === ===
*** #link https://fedorahosted.org/fedora-commops/ticket/69#comment:4
** #info === ===
** #info === skamath File a Pagure issue about adding listeners for tracking activity in forks via fedmsg ===
** #info === [COMPLETE] jflory7 Review and schedule SELF 2016 CommBlog post due:2016-07-12T12:00 ===
*** #link https://communityblog.fedoraproject.org/southeast-linux-fest-self-2016/
** #info === [COMPLETE] jflory7 Take a look at the FOSCo status page closer, see if there's anything to add from CommOps / Marketing perspective ===
*** #link https://fedoraproject.org/wiki/FOSCo_status#Other_considerations
** #info === [IN PROGRESS] commops Add thoughts and feedback about CommOps performance this release to the retrospective page ===
*** #action commops Add thoughts and feedback about CommOps performance this release to the retrospective page
** #info === [COMPLETE] jflory7 Add personal thoughts to F24 CommOps retrospective ===
*** #link https://fedoraproject.org/wiki/F24_CommOps_retrospective
** #info === skamath Figure out how to add statistics to the CommOps retrospective wiki ===




* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://fedorahosted.org/fedora-commops/report/9
** #link https://fedorahosted.org/fedora-commops/report/9
** #info === Ticket #xx ===
** #info === Ticket #79 ===
*** #info ""
*** #info "Flock 2016 CommOps Workshop"
*** #link  
*** #link https://fedorahosted.org/fedora-commops/ticket/79
*** description
*** #link https://fedoraproject.org/wiki/CommOps/Flock_2016
** #info === Ticket #xx ===
*** The [[CommOps/Flock 2016|CommOps workshop]] at Flock will be happening next month. We have a two hour slot where we can present and work on existing tasks and action items. This is also a place for the community to bring ideas and wishes for us to help work on building a better project together. Take a mint
*** #info ""
** #info === Tickets #34, 49 ===
*** #link  
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** description
*** #info #49: "[Onboarding Series] Infrastructure"
** #info === Ticket #xx ===
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #info ""
*** #link https://fedorahosted.org/fedora-commops/ticket/49
*** #link  
*** #info CommOps badge (#57) and Modularity WG (#69) badges are in progress in the Badges Team Trac, blocking on artwork (YAML files are written and ready)
*** description
*** #action jflory7 Patch the script for awarding past members the new badge
*** As mentioned last week, the next ticket we wanted to discuss and focus on was the Infrastructure team on-boarding series. This one is slightly different than previous ones because it's not dependent on FAS group membership (already exists) as much as other criteria. Some already filed tickets for this need YAML rule files or just need to be pushed.
*** #link https://fedorahosted.org/fedora-badges/ticket/434
*** #link https://fedorahosted.org/fedora-badges/ticket/441
*** #link https://fedorahosted.org/fedora-badges/ticket/442
** #info === Ticket #71 ===
*** #info "Centralizing Ambassadors / Events resources and utilities"
*** #link https://fedorahosted.org/fedora-commops/ticket/71
*** #link https://fedoraproject.org/wiki/Ambassadors/Design
*** #info Still awaiting feedback from the Design Team - once approved, we can send it out on the Ambassadors list, to regional treasurers / storytellers, and write a CommBlog article




Line 75: Line 93:
** #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 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 === This Week in CommBlog ===
*** #info (1) ""
*** #info (1) "Heroes of Fedora (HoF) – F23 Final"
**** #link  
**** #link https://communityblog.fedoraproject.org/heroes-of-fedora-hof-f23-final/
**** #info Total Views (date - date):  
**** #info Total Views (July 7 - July 12): 155
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1697
*** #info (2) ""
*** #info (2) "Southeast Linux Fest (SELF) 2016"
**** #link  
**** #link https://communityblog.fedoraproject.org/southeast-linux-fest-self-2016/
**** #info Total Views (date - date):  
**** #info Total Views (July 8 - July 12): 80
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1676
*** #info (3) ""
*** #info (3) "Hosting your own Fedora Test Day"
**** #link  
**** #link https://communityblog.fedoraproject.org/hosting-fedora-test-day/
**** #info Total Views (date - date):  
**** #info Total Views (July 12): 6
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1667
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "Fedora 24 Release Party: SFVLUG Event Report" – 2016-07-13
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1703&preview=1&_ppp=74bfe46cd0
*** #info (2) ""
*** #info (2) "Fedora 24 Release Party: Bangalore, India" – 2016-07-14
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1731&preview=1&_ppp=b9ec742d59
*** #info (3) ""
*** #info (3) "Fedora Needs You to Port a Python Package!"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1771&preview=1&_ppp=65368d7db4
*** #info (4) "Getting started with 'update-testing' Fedora QA part 2"
**** #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=408e25d891
*** #info (5) "Getting started with Fedora QA part 3"
**** #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=fdff785ddf
** #help Writers for the Community Blog wanted! Working on cool stuff in Fedora? Want to get the word out about future changes? Need to get more opinions or eyes on a topic? Consider writing a short post for the Community Blog! Check out #fedora-commops for more info!




* '''#topic Release Schedule'''
* '''#topic Release Schedule'''
** #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
** #link https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
** #info The CommOps Fedora 24 retrospective wiki page is now up. Anyone who has contributed or participated in CommOps this release cycle is HIGHLY encouraged to add feedback to the page with their thoughts and opinions about our performance as a team this release. Please take 10 - 20 minutes to add your own thoughts and ideas to the page this week. This helps us improve and grow as a team.
** #link https://fedoraproject.org/wiki/F24_CommOps_retrospective





Revision as of 15:43, 12 July 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-07-12

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-07-12)
  • #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-07-05/commops.2016-07-05-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 === [COMPLETE] jflory7 Continue working through Community Blog queue after receiving feedback from authors ===
      • #info Article published today, good number coming out this week, still some more in the queue of being edited
    • #info === [COMPLETE] jflory7 Update Ticket #69 about Modularity WG on-boarding badge ticket ===
    • #info === skamath File a Pagure issue about adding listeners for tracking activity in forks via fedmsg ===
    • #info === [COMPLETE] jflory7 Review and schedule SELF 2016 CommBlog post due:2016-07-12T12:00 ===
    • #info === [COMPLETE] jflory7 Take a look at the FOSCo status page closer, see if there's anything to add from CommOps / Marketing perspective ===
    • #info === [IN PROGRESS] commops Add thoughts and feedback about CommOps performance this release to the retrospective page ===
      • #action commops Add thoughts and feedback about CommOps performance this release to the retrospective page
    • #info === [COMPLETE] jflory7 Add personal thoughts to F24 CommOps retrospective ===
    • #info === skamath Figure out how to add statistics to the CommOps retrospective wiki ===






  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting