From Fedora Project Wiki

(Update template for next week)
 
(First draft of the agenda)
Line 9: Line 9:
|agenda=* '''#startmeeting Fedora CommOps (2016-06-07)'''
|agenda=* '''#startmeeting Fedora CommOps (2016-06-07)'''
* '''#meetingname commops'''
* '''#meetingname commops'''
* '''#nick CommOps'''
* '''#nick commops'''
* '''#chair <given to approved members of FAS group at meeting>'''
* '''#chair <given to approved members of FAS group at meeting>'''


Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Fedora Cloud FAD 2016" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedora-cloud-fad-2016/
*** #info  
*** #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 === "" ===
** #info === "Fedora Design Team lead Máirín Duffy wins O’Reilly Open Source Award" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedora-design-team-lead-mairin-duffy-wins-oreilly-open-source-award/
*** #info  
*** #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 === "" ===
** #info === Fedora 24 releases June 14 ===
*** #link
*** #info Just in case you forgot, Fedora 24 drops in another seven days!
*** #info  




Line 45: Line 44:
** #link  
** #link  
** #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 === [COMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
** #info === ===
*** #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/OGHF2254VRUWUJTE36X3S5X5EQX5MQ5I/
** #info === ===
** #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 === ===
*** #link https://fedoraproject.org/wiki/FAD_CommOps_2016
** #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 === 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. :) ===
** #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 ===
*** #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/OGHF2254VRUWUJTE36X3S5X5EQX5MQ5I/
** #info === [COMPLETE] jflory7 Update Ticket #71 with the ideas and discussion from this meeting ===
*** #link https://fedorahosted.org/fedora-commops/ticket/71#comment:6
** #info === [COMPLETE] jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source ===
*** #link https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/
** #info === [COMPLETE] jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session ===
*** #link




* '''#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 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 ""
** #info === Tickets #34, 49, 69 ===
*** #link  
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** description
*** #info #49: "[Onboarding Series] Infrastructure"
** #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/49
*** description
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** This tickets are all currently blocking on Badges proposals. The next logical steps to get this in motion will be to propose the badge series creation on the Fedora Badges Trac. After that, these badges can be tackled at the Design + CommOps hack session or another convenient time. With this week being PyCon, it might be a slow start at the beginning of this week, but there are Fedora sprints at PyCon, so this might be a good time to try to coordinate a hack session or something similar. It will be worth checking in with decause about when the hack sessions are so we can maybe try to work around those times. Would anyone be interested in proposing the badges on the Fedora Badges Trac?
*** #link https://fedorahosted.org/fedora-badges/
** #info === Ticket #71 ===
*** #info "Centralizing Ambassadors / Events resources and utilities"
*** #link https://fedorahosted.org/fedora-commops/ticket/71
***  




* '''#topic Wiki Gardening'''
* '''#topic Wiki Gardening'''
** #action CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
** #action commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]




Line 75: Line 94:
** #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 CommBlog Keeps it 100"
**** #link  
**** #link https://communityblog.fedoraproject.org/commblog-keeps-100/
**** #info Total Views (date - date):  
**** #info Total Views (June 2 - June 7): 53
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1582
*** #info (2) ""
*** #info (2) "Fedora Cloud FAD 2016"
**** #link  
**** #link https://communityblog.fedoraproject.org/fedora-cloud-fad-2016/
**** #info Total Views (date - date):  
**** #info Total Views (June 4 - June 7): 39
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1618
*** #info (3) ""
*** #info (3) "OSCON 2016 Expo Hall Booth Report"
**** #link  
**** #link https://communityblog.fedoraproject.org/oscon-2016-expo-hall-booth-report/
**** #info Total Views (date - date):  
**** #info Total Views (June 6 - June 7): 40
**** #link  
**** #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 === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "Getting started with Fedora QA (Part 1)"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1608&preview=1&_ppp=cc40c9d0e6
*** #info (2) ""
**** #info Scheduled for Thursday, June 9, 8:00 UTC
**** #link  
*** #info (2) "Getting started with 'update-testing' Fedora QA part 2"
*** #info (3) ""
**** #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=8c73937530
**** #link  
*** #info (3) "Getting started with Fedora QA part 3"
**** #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=17e4652e53
*** #info (4) "Event Report: PyCon 2016"
**** #link https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=cffc2b4a56




Revision as of 14:01, 7 June 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-06-07

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-07)
  • #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
    • #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 === 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. :) ===
    • #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 ===
      • #link


  • #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
      • This tickets are all currently blocking on Badges proposals. The next logical steps to get this in motion will be to propose the badge series creation on the Fedora Badges Trac. After that, these badges can be tackled at the Design + CommOps hack session or another convenient time. With this week being PyCon, it might be a slow start at the beginning of this week, but there are Fedora sprints at PyCon, so this might be a good time to try to coordinate a hack session or something similar. It will be worth checking in with decause about when the hack sessions are so we can maybe try to work around those times. Would anyone be interested in proposing the badges on the Fedora Badges Trac?
      • #link https://fedorahosted.org/fedora-badges/
    • #info === Ticket #71 ===





  • #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-07&oldid=449446"