From Fedora Project Wiki

(Create meeting agenda outline)
 
(Add minutes and logs)
 
(4 intermediate revisions by the same user not shown)
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === GSoC project period begins Monday, May 23 ===
*** #link  
*** #link https://summerofcode.withgoogle.com/how-it-works/
*** #info  
*** #info The Google Summer of Code project period officially begins on May 23rd. Students will officially begin working on their projects starting next Monday.
** #info === "" ===
** /me hasn't been around much this week to know of any other announcements :)
*** #link
*** #info
** #info === "" ===
*** #link
*** #info




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-10/commops.2016-05-10-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 === decause fill up the LimeSurvey account with moneydollars ===
** #info === ===
** #info === [COMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
** #info === ===
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/J6MSAW4UBESXPC7PD6C43JCTWZKB2W5B/
** #info === ===
** #info === [COMPLETE] decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
** #info === ===
*** #link https://fedorahosted.org/fedora-infrastructure/ticket/5304
** #info === CommOps solidify onboarding steps before 5/23 internships begin ===
*** #action CommOps solidify onboarding steps before 5/23 internships begin
** #info === decause talk to spot about scheduling an EDU FAD after budget gets settled ===
** #info === [INCOMPLETE] jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad ===
*** #action jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad
** #info === [INCOMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
*** #action jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
** #info === [INCOMPLETE] jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
*** #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
** #info === [COMPLETE] skamath add categories to the Summer Coding 2016 page ===
*** #link https://fedoraproject.org/wiki/Summer_Coding_SIG
** #info === jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
** #info === [COMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
*** #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
** #info === [COMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/NIRMPNQI7TV2LNT42IZMAWUSATGSKFGK/
** #info === [COMPLETE] dhanesh95 Work on merging the draft changes for the University Involvement Initiative into the main page (including in the section header "Proposed") ===
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative#Proposed_Program:_Campus_Ambassadors
** #info === [COMPLETE] jflory7 / decause Drop ticket comment in #fedora-modularization after meeting ===
** #info === [COMPLETE] skamath File an issue in the Community Blog repo for adding a footer with licensing information to the bottom of the site ===
*** #link https://pagure.io/communityblog-theme/pull-request/8
*** LinuxHippie++
** #info === [IN PROGRESS] decause get the tshirt orders in ASAP for PyCon ===
*** #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
** #info === [IN PROGRESS] decause get the sticker orders in ASAP for PyCon ===
*** #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
** #info === [COMPLETE] LinuxHippie Work on creating a first draft of the PyCon 2016 page on the wiki, drop mail on the mailing list once an initial draft is ready for decause and other attendees to review ===
*** #link https://fedoraproject.org/wiki/PyCon_2016
** #info === [INCOMPLETE] jflory7 Help ship F24 Party article for Thursday morning (Wednesday if possible) ===
*** #action jflory7 Ship F24 Party article today
** #info === omiday Contact the Infrastructure team in IRC or mailing list about point of contact for Ask Fedora and about adding banners for Magazine and/or CommBlog ===




* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://fedorahosted.org/fedora-commops/report/9
** #link https://fedorahosted.org/fedora-commops/report/9
** #info === Ticket #xx ===
** #info === Tickets #34, 49 ===
*** #info ""
*** #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
*** #link  
*** #info #49: "[Onboarding Series] Infrastructure"
*** description
*** #link https://fedorahosted.org/fedora-commops/ticket/34
** #info === Ticket #xx ===
*** #link https://fedorahosted.org/fedora-commops/ticket/49
*** #info ""
*** #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
*** #link  
*** A Badges workshop was officially proposed this morning on the CommOps and Design mailing list. This is the first steps to moving forward on these items (since there has been a lull for the past week or two since others have been away / busy). A hack session tonight or tomorrow might be useful to do some moving forward on this ticket, finalizing a Badges workshop with the Design team, and also getting through our own backlog. If a hack session works well, when do we want to aim for?
*** description
** #info === Ticket #68 ===
** #info === Ticket #xx ===
*** #info "Reconstructing the Campus Ambassadors program and campus outreach"
*** #info ""
*** #link https://fedorahosted.org/fedora-commops/ticket/68
*** #link  
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
*** description
*** With Dhanesh's progress on this, a big first step towards centralizing info has been accomplished. Now that it's there, we should identify the next steps of how to reconstruct the program. Is the next step the FAD? Or is there more work that needs to be done in order for us to get to a FAD?
** #info === Ticket #69 ===
*** #info "Fedora Modularity onboarding"
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #info (1) Someone can review the contents of their on-boarding wiki page and pass feedback about them in the ticket, as compared to other on-boarding methods in Fedora
*** #info (2) Putting together a badge proposal for membership in the Modularity WG (in the form of a ticket on the fedora-badges Trac)
*** #info (3) A Community Blog article announcing the presence of the Modularity WG, what they are, what they do, how to get involved (penned by one of the WG members)
*** #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
*** The Modularity WG is currently reviewing the feedback on the ticket as of this morning. They may have comments by the time this ticket rolls around in the meeting.
** #info === Ticket #74 ===
*** #info "Add license information to the CommBlog footer"
*** #link https://fedorahosted.org/fedora-commops/ticket/74
*** #info Nice work by LinuxHippie submitting a pull request to accomplish this! The PR is pending review by ryanlerch for merging into the theme. Anyone else is also welcome to review if you are PHP-savvy or want to double-check the correct license is being used.
*** #link https://pagure.io/communityblog-theme/pull-request/8




Line 75: Line 114:
** #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) "Event Report: Fedora Docs FAD"
**** #link  
**** #link https://communityblog.fedoraproject.org/event-report-fedora-docs-fad/
**** #info Total Views (date - date):  
**** #info Total Views (May 12 - May 17): 218
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1511
*** #info (2) ""
*** #info (2) "Fedora 24 Beta Released!"
**** #link  
**** #link https://communityblog.fedoraproject.org/fedora-24-beta-released/
**** #info Total Views (date - date):  
**** #info Total Views (May 12 - May 17): 54
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1542
*** #info (3) ""
**** #link
**** #info Total Views (date - date):
**** #link
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "Fedora 24: Let’s have a party!"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=1496&preview=1&_ppp=a34697b353
*** #info (2) ""
**** Going out today.
**** #link
*** #info (2) "Fedora at Bitcamp 2016"
*** #info (3) ""
**** #info In progress, jflory7 to assist in writing this one
**** #link  
*** #info (3) "DevConfCZ 2016: Event Report"
**** #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=97da4ae90c
 




Line 101: Line 138:


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

Latest revision as of 17:20, 17 May 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-05-17

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-05-17)
  • #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 === GSoC project period begins Monday, May 23 ===
    • /me hasn't been around much this week to know of any other announcements :)


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-10/commops.2016-05-10-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 === decause fill up the LimeSurvey account with moneydollars ===
    • #info === [COMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
    • #info === [COMPLETE] decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
    • #info === CommOps solidify onboarding steps before 5/23 internships begin ===
      • #action CommOps solidify onboarding steps before 5/23 internships begin
    • #info === decause talk to spot about scheduling an EDU FAD after budget gets settled ===
    • #info === [INCOMPLETE] jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad ===
      • #action jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad
    • #info === [INCOMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
      • #action jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
    • #info === [INCOMPLETE] jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
      • #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
    • #info === [COMPLETE] skamath add categories to the Summer Coding 2016 page ===
    • #info === jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
    • #info === [COMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
    • #info === [COMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
    • #info === [COMPLETE] dhanesh95 Work on merging the draft changes for the University Involvement Initiative into the main page (including in the section header "Proposed") ===
    • #info === [COMPLETE] jflory7 / decause Drop ticket comment in #fedora-modularization after meeting ===
    • #info === [COMPLETE] skamath File an issue in the Community Blog repo for adding a footer with licensing information to the bottom of the site ===
    • #info === [IN PROGRESS] decause get the tshirt orders in ASAP for PyCon ===
      • #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
    • #info === [IN PROGRESS] decause get the sticker orders in ASAP for PyCon ===
      • #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
    • #info === [COMPLETE] LinuxHippie Work on creating a first draft of the PyCon 2016 page on the wiki, drop mail on the mailing list once an initial draft is ready for decause and other attendees to review ===
    • #info === [INCOMPLETE] jflory7 Help ship F24 Party article for Thursday morning (Wednesday if possible) ===
      • #action jflory7 Ship F24 Party article today
    • #info === omiday Contact the Infrastructure team in IRC or mailing list about point of contact for Ask Fedora and about adding banners for Magazine and/or CommBlog ===


  • #topic Tickets
    • #link https://fedorahosted.org/fedora-commops/report/9
    • #info === Tickets #34, 49 ===
      • #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
      • #info #49: "[Onboarding Series] Infrastructure"
      • #link https://fedorahosted.org/fedora-commops/ticket/34
      • #link https://fedorahosted.org/fedora-commops/ticket/49
      • #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
      • A Badges workshop was officially proposed this morning on the CommOps and Design mailing list. This is the first steps to moving forward on these items (since there has been a lull for the past week or two since others have been away / busy). A hack session tonight or tomorrow might be useful to do some moving forward on this ticket, finalizing a Badges workshop with the Design team, and also getting through our own backlog. If a hack session works well, when do we want to aim for?
    • #info === Ticket #68 ===
    • #info === Ticket #69 ===
      • #info "Fedora Modularity onboarding"
      • #link https://fedorahosted.org/fedora-commops/ticket/69
      • #info (1) Someone can review the contents of their on-boarding wiki page and pass feedback about them in the ticket, as compared to other on-boarding methods in Fedora
      • #info (2) Putting together a badge proposal for membership in the Modularity WG (in the form of a ticket on the fedora-badges Trac)
      • #info (3) A Community Blog article announcing the presence of the Modularity WG, what they are, what they do, how to get involved (penned by one of the WG members)
      • #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
      • The Modularity WG is currently reviewing the feedback on the ticket as of this morning. They may have comments by the time this ticket rolls around in the meeting.
    • #info === Ticket #74 ===





  • #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-05-17&oldid=446783"