From Fedora Project Wiki

(Prepare next week's agenda)
 
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === Last week: Fedora 24 no-go, delayed to June 21 ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/CCPEFDBYMHBNLTNG2CC57KUBBQOO67RD/
*** #info  
*** #info Due to a remaining blocker bug in F24, the release has been delayed by one week to June 21st, 2016. If all goes well, we should be back again here next week with a new Fedora release on our hands.
** #info === "" ===
** #info === Events coming soon: Red Hat Summit, Flock ===
*** #link  
*** #link https://www.redhat.com/en/summit
*** #info  
*** #link https://flocktofedora.org/
** #info === "" ===
*** #info Two upcoming events on the Fedora calendar are Red Hat Summit (June 27-29) and Flock, Fedora's annual contributor conference (August 2-5).
*** #link  
** #info === "Fedora Council Meeting 2016-06-13: Report on CommOps " ===
*** #info  
*** #link https://youtu.be/AQWybn1QVKc
*** #info Yesterday at the Fedora Council meeting, decause gave a report on the status, work, and accomplishments of the CommOps sub-project. Thanks to everyone who helped pull together information and the presentation yesterday! decause++ bee2502++ skamath++ meskarune++ commops++ It's worth a watch if you haven't checked it out already.




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06-07-15.58.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 === decause Follow up with tatica and diversity team about LimeSurvey availability ===
** #info === ===
** #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
** #info === ===
** #info === decause nail down Flock arrangements, add them to Fedocal ===
** #info === ===
** #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
** #info === ===
** #info === [COMPLETE] 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 ===
*** #link https://fedorahosted.org/fedora-badges/ticket/464
** #info === [COMPLETE] jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) ===
*** #link https://fedorahosted.org/fedora-commops/ticket/10#comment:5
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/GSZLMED2YQ3HNQVJDH6ETCJCWXZTRCIE/
** #info === [COMPLETE] jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on mizmo's feedback ===
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/L7VXDJD47JSB5O7UUQNUDTGZTSSTA7LB/
** #info === decause ship "final" version for review by EoB thursday of F24 GA Release Announcement ===
** #info === [COMPLETE] jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC ===
*** #link https://apps.fedoraproject.org/calendar/meeting/4145/
*** viorel++




* '''#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 #10 ===
*** #info ""
*** #info "CommOps vFAD 2016"
*** #link  
*** #link https://fedorahosted.org/fedora-commops/ticket/10
*** description
*** #link https://fedoraproject.org/wiki/FAD_CommOps_2016
** #info === Ticket #xx ===
*** In the ticket, there is a summary of the changes made to the wiki page for the vFAD, mostly focusing on our purposes for a vFAD, the impact we'd like to have by organizing this, and the objectives we would wish to accomplish. A vote was put out last week, and as according to our voting policy, the ticket "passed". The next steps should be trying to pick out a date for when we could organize our vFAD and reach the most people. Also deciding how long we want to run our vFAD?
*** #info ""
** #info === Tickets #34, 49, 69 ===
*** #link  
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** description
*** #info #49: "[Onboarding Series] CommOps!"
** #info === Ticket #xx ===
*** #info #69: "Fedora Modularity onboarding"
*** #info ""
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #link  
*** #link https://fedorahosted.org/fedora-commops/ticket/57
*** description
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** skamath filed a ticket for the CommOps on-boarding badge series on the Badges Team Trac. In the ticket, we have the basic criteria, some name ideas, a badge description, discussion on how to automate the badge, and some initial artwork concept ideas.
*** Best place to start for now... how do we want to handle automation of this badge? Should it be dependent on whether a user already has certain badges? Questions to ask: Is this an expensive operation? Will we be able to hit everything we need?
*** Alternatively, would it be better to make sponsorship in the FAS group the best way to automate this? This will ensure a human is verifying the person has performed the needed responsibilities and tasks to become "bootstrapped" in CommOps. The FAS group memberships have to be manually approved already, so this is a factor to consider too.
*** #link https://fedorahosted.org/fedora-badges/ticket/464
** #info === Ticket #71 ===
*** #info "Centralizing Ambassadors / Events resources and utilities"
*** #link https://fedorahosted.org/fedora-commops/ticket/71
*** Based on feedback given by the Design Team, there are already efforts and repositories in place to bring together Design resources. However, the Design Team has a strong preference for having Ambassadors or others request assets or design work for the printing press in the Design Team Trac to ensure that guidelines are met and the Fedora brand is well-represented. The suggestion I had was better communicating this process to the Ambassadors. Take a minute to review the ticket and let us know what your thoughts are.
*** #link https://pagure.io/designassets/tree/master




Line 75: Line 96:
** #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) "Getting started with Fedora QA (Part 1)"
**** #link
**** #link https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/
**** #info Total Views (date - date):
**** #info Total Views (June 9 - June 14): 510
**** #link
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1608
*** #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) "Cloud Working Group FAD"
**** #link  
**** #link https://public.etherpad-mozilla.org/p/fad-summary-2016-june
*** #info (2) ""
**** #info Written by jzb, looking at publishing this week.
**** #link  
*** #info (2) "Event Report: PyCon 2016"
*** #info (3) ""
**** #link https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=d3705befb7
**** #link  
*** #info (3) "Getting started with 'update-testing' Fedora QA part 2"
**** #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=8a0d20416e
*** #info (4) "Getting started with Fedora QA part 3"
**** #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=676163dcfd




Line 101: Line 117:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-06-14-15.58.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-06-14-15.58.log.html
|next-meeting=2016-06-21
|next-meeting=2016-06-21
}}
}}

Latest revision as of 17:38, 14 June 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-06-14

Meeting Time

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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-06-14)
  • #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 === Last week: Fedora 24 no-go, delayed to June 21 ===
    • #info === Events coming soon: Red Hat Summit, Flock ===
    • #info === "Fedora Council Meeting 2016-06-13: Report on CommOps " ===
      • #link https://youtu.be/AQWybn1QVKc
      • #info Yesterday at the Fedora Council meeting, decause gave a report on the status, work, and accomplishments of the CommOps sub-project. Thanks to everyone who helped pull together information and the presentation yesterday! decause++ bee2502++ skamath++ meskarune++ commops++ It's worth a watch if you haven't checked it out already.



  • #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 the ticket, there is a summary of the changes made to the wiki page for the vFAD, mostly focusing on our purposes for a vFAD, the impact we'd like to have by organizing this, and the objectives we would wish to accomplish. A vote was put out last week, and as according to our voting policy, the ticket "passed". The next steps should be trying to pick out a date for when we could organize our vFAD and reach the most people. Also deciding how long we want to run our vFAD?
    • #info === Tickets #34, 49, 69 ===
      • #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
      • #info #49: "[Onboarding Series] CommOps!"
      • #info #69: "Fedora Modularity onboarding"
      • #link https://fedorahosted.org/fedora-commops/ticket/34
      • #link https://fedorahosted.org/fedora-commops/ticket/57
      • #link https://fedorahosted.org/fedora-commops/ticket/69
      • #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
      • skamath filed a ticket for the CommOps on-boarding badge series on the Badges Team Trac. In the ticket, we have the basic criteria, some name ideas, a badge description, discussion on how to automate the badge, and some initial artwork concept ideas.
      • Best place to start for now... how do we want to handle automation of this badge? Should it be dependent on whether a user already has certain badges? Questions to ask: Is this an expensive operation? Will we be able to hit everything we need?
      • Alternatively, would it be better to make sponsorship in the FAS group the best way to automate this? This will ensure a human is verifying the person has performed the needed responsibilities and tasks to become "bootstrapped" in CommOps. The FAS group memberships have to be manually approved already, so this is a factor to consider too.
      • #link https://fedorahosted.org/fedora-badges/ticket/464
    • #info === Ticket #71 ===
      • #info "Centralizing Ambassadors / Events resources and utilities"
      • #link https://fedorahosted.org/fedora-commops/ticket/71
      • Based on feedback given by the Design Team, there are already efforts and repositories in place to bring together Design resources. However, the Design Team has a strong preference for having Ambassadors or others request assets or design work for the printing press in the Design Team Trac to ensure that guidelines are met and the Fedora brand is well-represented. The suggestion I had was better communicating this process to the Ambassadors. Take a minute to review the ticket and let us know what your thoughts are.
      • #link https://pagure.io/designassets/tree/master





  • #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-06-14&oldid=455565"