From Fedora Project Wiki

(Prepare agenda for future meeting)
 
(Add minutes and logs)
 
(One intermediate revision by the same user not shown)
Line 2: Line 2:
|YEAR=2016
|YEAR=2016
|MONTH=07
|MONTH=07
|DAY=12
|DAY=05
|HOUR=16
|HOUR=16
|MINUTE=00
|MINUTE=00
|CHANNEL=#fedora-meeting
|CHANNEL=#fedora-meeting
|CHAIR=jflory7
|CHAIR=jflory7
|agenda=* '''#startmeeting Fedora CommOps (2016-07-12)'''
|agenda=* '''#startmeeting Fedora CommOps (2016-07-05)'''
* '''#meetingname commops'''
* '''#meetingname commops'''
* '''#nick commops'''
* '''#nick commops'''
Line 14: Line 14:


* '''#topic Agenda'''
* '''#topic Agenda'''
** #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-07-12
** #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-07-05
** #info (1) Roll Call / Q&A
** #info (1) Roll Call / Q&A
** #info (2) Announcements
** #info (2) Announcements
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Fedora 22: End Of Life, 2016 July 19" ===
*** #link  
*** #link https://fedoramagazine.org/fedora-22-end-of-life-2016-july/
*** #info  
*** #info With the recent release of Fedora 24, Fedora 22 will officially enter End Of Life (EOL) status on July 19th, 2016. After July 19th, all packages in the Fedora 22 repositories will no longer receive security, bugfix, or enhancement updates, and no new packages will be added to the Fedora 22 collection.
** #info === "" ===
** #info === Fedora 24 release parties in progress ===
*** #link  
*** #link http://athosribeiro.com/post/fedora24-rp-sp/
*** #info  
*** #link http://danielammorais.com/2016/07/04/fedora-24-release-party-in-sao-paulo/
** #info === "" ===
*** #link https://yoseft7.wordpress.com/2016/07/03/f24-release-party-pa/
*** #link  
*** #link https://www.facebook.com/events/1625975777730164/
*** #info  
*** #link https://www.facebook.com/events/1141198245938476/
*** #link http://www.abdelmartinez.com/2016/07/fedora-24-release-party-panama-report.html
*** #link https://nmilosev.svbtle.com/fedora-24-release-party-novi-sad
*** #info There are Fedora 24 release parties happening all over the world both this month and the end of last month. You can see reports or event pages from Ambassadors at all of the above links. See if there are any release parties happening in your region! If you're interested in organizing one, check out this post on the Community Blog.
*** #link https://communityblog.fedoraproject.org/fedora-24-have-a-party/
** #info === "Flock 2016: August 2-5, 2016" ===
*** #link https://flocktofedora.org/
*** #info Reminder that Flock, Fedora's annual contributor conference, is coming up at the beginning of next month.




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-06-28-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 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 Move forward with making final plans for vFAD or reconsider plans for Flock workshop (???) ===
** #info === ===
*** #link https://fedorahosted.org/fedora-commops/ticket/79
** #info === ===
*** #link https://fedoraproject.org/wiki/CommOps/Flock_2016
** #info === ===
** #info === [COMPLETE] jflory7 Follow up in #fedora-flock about Fedocal for Flock or if any previous action items need follow-up ===
** #info === ===
** #info === [INCOMPLETE] jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
*** #action jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
** #info === [COMPLETE] jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later ===
*** #link https://fedoraproject.org/wiki/Ambassadors/Design
** #info === [IN PROGRESS] jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response ===
*** #action jflory7 Continue working through Community Blog queue after receiving feedback from authors
** #info === [COMPLETE] skamath File a Badges ticket for the Modularity WG on-boarding badge, write basic YAML file for awarding the badge based on previous badge ticket (#464) ===
*** #link https://fedorahosted.org/fedora-badges/ticket/466
** #info === [COMPLETE] jflory7 Work on getting a wiki page created for the CommOps F23 retrospective ===
*** #link https://fedoraproject.org/wiki/F24_CommOps_retrospective
** #info === skamath Work on generating data from CommOps contributions and shaping interpretations from the data for the retrospective (cc: bee2502 to help relate this to GSoC work, possibly?) ===




* '''#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, 69 ===
*** #link  
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** description
*** #info #49: "[Onboarding Series] CommOps!"
** #info === Ticket #xx ===
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #info ""
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #link  
*** #link https://fedorahosted.org/fedora-badges/ticket/466
*** description
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** skamath filed the next ticket for the Modularity WG badge, based on FAS group sponsorship. It is awaiting review by a Design Team member to create the art assets for it. We can post an update on the Modularity WG ticket about the latest update to their ticket.
*** #action jflory7 Update Ticket #69 about Modularity WG on-boarding badge ticket
** #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 Wiki page written up detailing communication process between Ambassadors and Design team, based on feedback from mizmo and gnokii. Page was sent off to the Design Team mailing list and awaits review from Design members. Once approved, next action is to socialize it with Ambassadors and specific regional leaders, i.e. storytellers and treasurers.
*** Glancing through the page, does anyone notice anything or have any feedback about it that they'd like to offer out?




Line 75: Line 100:
** #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) "Fedora Design Suite considered “best of the basics”"
**** #link  
**** #link https://communityblog.fedoraproject.org/fedora-design-suite-best-basics/
**** #info Total Views (date - date):  
**** #info Total Views (June 30 - July 5): 49
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1691
*** #info (2) ""
**** #link
**** #info Total Views (date - date):  
**** #link
*** #info (3) ""
**** #link
**** #info Total Views (date - date):
**** #link
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "Southeast Linux Fest 2016"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1676&preview=1&_ppp=7b7b5413f2
*** #info (2) ""
**** #action jflory7 Review and schedule SELF 2016 CommBlog post due:2016-07-12T12:00
**** #link  
*** #info (2) "Hosting your own Fedora Test Day"
*** #info (3) ""
**** #link https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=fbcb9c9051
**** #link  
**** #info Already reviewed, waiting for follow-up from author
*** #info (3) "Heroes of Fedora (HoF) – F23 Final"
**** #link https://communityblog.fedoraproject.org/?p=1697&preview=1&_ppp=e29bced019
**** #info Scheduled: 2016-07-07, 08:15 UTC
*** #info (4) "Fedora 24 Release Party: San Fernando Valley Linux Users Group (2016) Event Report – Van Nuys, California"
**** #link https://communityblog.fedoraproject.org/?p=1703&preview=1&_ppp=c68c8b0fae
**** #info In progress by author, will revisit once complete.




* '''#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-24/f-24-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
** #action commops Add thoughts and feedback about CommOps performance this release to the retrospective page
** #action jflory7 Add personal thoughts to F24 CommOps retrospective




* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-07-05/commops.2016-07-05-15.56.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-07-05/commops.2016-07-05-15.56.log.html
|next-meeting=2016-07-12
|next-meeting=2016-07-12
}}
}}

Latest revision as of 18:27, 5 July 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-07-05

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-05)
  • #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-06-28/commops.2016-06-28-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 === [COMPLETE] jflory7 Move forward with making final plans for vFAD or reconsider plans for Flock workshop (???) ===
    • #info === [COMPLETE] jflory7 Follow up in #fedora-flock about Fedocal for Flock or if any previous action items need follow-up ===
    • #info === [INCOMPLETE] jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
      • #action jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
    • #info === [COMPLETE] jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later ===
    • #info === [IN PROGRESS] jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response ===
      • #action jflory7 Continue working through Community Blog queue after receiving feedback from authors
    • #info === [COMPLETE] skamath File a Badges ticket for the Modularity WG on-boarding badge, write basic YAML file for awarding the badge based on previous badge ticket (#464) ===
    • #info === [COMPLETE] jflory7 Work on getting a wiki page created for the CommOps F23 retrospective ===
    • #info === skamath Work on generating data from CommOps contributions and shaping interpretations from the data for the retrospective (cc: bee2502 to help relate this to GSoC work, possibly?) ===





  • #topic Release Schedule
    • #link https://fedorapeople.org/groups/schedule/f-24/f-24-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
    • #action commops Add thoughts and feedback about CommOps performance this release to the retrospective page
    • #action jflory7 Add personal thoughts to F24 CommOps retrospective


  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting