From Fedora Project Wiki

(Preliminary draft of meeting agenda)
 
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 39: Line 39:
*** #link https://fedorahosted.org/fedora-commops/ticket/29
*** #link https://fedorahosted.org/fedora-commops/ticket/29
*** #info Ticket #29, "G11n - proposal for the group revitalization", is now marked as closed. With the publication of the above event report, this was the last action item identified to close out this ticket. Awesome work to everyone involved!
*** #info Ticket #29, "G11n - proposal for the group revitalization", is now marked as closed. With the publication of the above event report, this was the last action item identified to close out this ticket. Awesome work to everyone involved!
** #info === Fedora 24 Beta Release Readiness meeting ===
** #info === Fedora 24 Beta Release Readiness Meeting, Thursday, April 28 19:00 UTC ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/logistics@lists.fedoraproject.org/thread/JMZO6YNQSBMQHQNTYKF7EXRK3CMZGGDY/#JMZO6YNQSBMQHQNTYKF7EXRK3CMZGGDY
*** #info
*** #info Before each public release all of the groups participating in the development of Fedora's next release meet to make sure the release is well coordinated. This meeting is called the: Release Readiness Meeting. The Release Readiness Meeting is held after after the Go/No-Go Meeting that is held for each public release. CommOpsers are welcome to attend!
** #info === "" ===
*** #link
*** #info  




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-04-19/commops.2016-04-19-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 === decause complete limesurvey account creation process ===
** #info === ===
** #info === [IN PROGRESS] decause Work on migrating the raw University Involvement Initiative notes from the Etherpad into a more parseable, digestible format (whether wiki or other format) ===
** #info === ===
*** #agreed This action item is now Ticket #68. We will revisit this item later on in the meeting during ticket discussion.
** #info === ===
** #info === [IN PROGRESS] jflory7 Continue writing and compiling project profiles of BrickHack 2016 participants (three replies so far, need to keep communication channels open) ===
** #info === ===
*** #action jflory7 Continue writing and compiling project profiles of BrickHack 2016 participants
** #info === [INCOMPLETE] decause / jflory7 Ping Marketing mailing list about Alpha to Beta release announcement research for May 3rd ===
*** #action decause / jflory7 Ping Marketing mailing list about Alpha to Beta release announcement research for May 3rd
** #info === [INCOMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
*** #action jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team
** #info === [IN PROGRESS] decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
*** #action decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog
** #info === [COMPLETE] jflory7 Upload the local Albanian F24 translation sprint group photo to the G11n vFAD article on the Community Blog ===
*** #link https://communityblog.fedoraproject.org/fedora-translation-sprint-5-days-50-members-20-thousand-words/
** #info === [IN PROGRESS] justharshal / dhanesh95 Work on moving the Etherpad notes into a more readable format on the University Involvement Initiative wiki page; after converting it, send to CommOps mailing list for feedback and review ===
*** #agreed This action item is now Ticket #68. We will revisit this item later on in the meeting during ticket discussion.
** #info === [INCOMPLETE] commops / jflory7 Create tickets for the above items 1-3 so they can be assigned and broken up among CommOps members ===
*** #action commops / jflory7 Create tickets for the above items 1-3 so they can be assigned and broken up among CommOps members
** #info === [COMPLETE] jflory7 Review and edit "Fedora translation sprint" article for publication on Thursday, if possible ===
*** #link https://communityblog.fedoraproject.org/fedora-translation-sprint-5-days-50-members-20-thousand-words/
** #info === [INCOMPLETE] jflory7 Ship the "Fedora Media Writer" article ASAP, contact author about dropping a link on the CommOps mailing list next time so we don't wind up last minute ===
*** #info This deadline was missed, was not published the day of the event :(




Line 64: Line 77:
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #link https://fedorahosted.org/fedora-commops/ticket/34
*** #link https://fedorahosted.org/fedora-commops/ticket/49
*** #link https://fedorahosted.org/fedora-commops/ticket/49
*** Last meeting, we wanted to follow up with the Design Team about the badges we were proposing for all teams (e.g. mailing list posts) and the Pagure-specific ones for Infrastructure. An email was sent to the Design Team list and awaits a response. Outside of assisting the Design Team in getting these next few badges created and pushed, are there any other tasks we want to focus on now? Preferred to focus our own resources on getting these badges done, but new badge ideas welcome, especially if they can be used for *all* sub-projects.
*** A lot of discussion and planning for the strategy and approach for these tickets and Fedora Hubs happened last week with decause, mizmo, ryanlerch, and sayan.
*** #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/JRDNZ5L3BXP7457AKXUJC62T256Q6MAN/
** #info === Ticket #68 ===
** #info === Ticket #68 ===
*** #info "Reconstructing the Campus Ambassadors program and campus outreach"
*** #info "Reconstructing the Campus Ambassadors program and campus outreach"
*** #link https://fedorahosted.org/fedora-commops/ticket/68
*** #link https://fedorahosted.org/fedora-commops/ticket/68
*** Last meeting, we identified that the next step for this ticket would be converting the raw Etherpad notes into the University Involvement Initiative wiki page. Once this is done, it will be easier to identify where to go with planning and organization for Campus Ambassadors in the future. This is a great task for someone wanting to dive in to help with. If you want to help with this, feel free to volunteer!
*** #link http://etherpad.osuosl.org/fedora-EDU-refresh
*** #link http://etherpad.osuosl.org/fedora-EDU-refresh
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative/draft
*** Last meeting, justharshal and dhanesh95 were going to work on moving the Etherpad contents into a more readable and formalized format on the wiki. Are there any updates on this progress or any questions that need to be answered?
** #info === Ticket #69 ===
** #info === Ticket #69 ===
*** #info "Fedora Modularity onboarding"
*** #info "Fedora Modularity onboarding"
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** #link https://fedorahosted.org/fedora-commops/ticket/69
*** A great start for this could be to help generate some traction with a Community Blog article announcing the Modularity WG. A badge proposal would be useful for sponsored / official members of the WG. A review of the wiki pages linked in the ticket would be helpful. Can we break up these tasks among members of CommOps?
*** #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)
*** Last meeting, we identified three smaller items of this ticket that needed to be broken up into smaller tickets so CommOps members could help take on the tasks. jflory7 still needs to create the tickets (will do today). Is there any other discussion needed here?
** #info === Ticket #70 ===
*** #info "FOSS Student Pack"
*** #link https://fedorahosted.org/fedora-commops/ticket/70
** #info === Ticket #71 ===
*** #info "Centralizing Ambassadors / Events resources and utilities"
*** #link https://fedorahosted.org/fedora-commops/ticket/71
*** This ticket has to do with bringing together several different resources and tools for Ambassadors and events into a single place. zoltanh721 also left feedback on this ticket (was originally filed in the Marketing Trac).




Line 91: Line 114:
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1434
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1434
** #info === Coming up in CommBlog ===
** #info === Coming up in CommBlog ===
*** #info (1) ""
**** #link
*** #info (2) ""
**** #link
*** #info (3) ""
**** #link
*** #info (1) "DevConfCZ 2016: Event Report"
*** #info (1) "DevConfCZ 2016: Event Report"
**** #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=6b95d2c034
**** #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=6b95d2c034
*** #info (2) "Fedora translation sprint – 5 days, 50 members and 20+ thousand words"
*** #info (2) "Announcing Fedora Google Summer of Code (GSoC) Class of 2016"
**** #link https://communityblog.fedoraproject.org/?p=1434&preview=1&_ppp=b2e060d3ee
**** #link https://communityblog.fedoraproject.org/?p=1477&preview=1&_ppp=1693dddaff
**** #action jflory7 Review and edit "Fedora translation sprint" article for publication on Thursday, if possible
*** #info (3) "Fedora's Love For Python Continues"
*** #info (3) "Time to test Fedora Media Writer"
**** #link https://communityblog.fedoraproject.org/?p=1470&preview=1&_ppp=8324c1b68a
**** #link https://communityblog.fedoraproject.org/?p=1446&preview=1&_ppp=6ffd1bc529
*** #info (4) "Fedora at Bitcamp 2016"
*** #info (4) "Fedora at Bitcamp 2016"
**** Still in progress
**** Still in progress, jflory7 will help write this one
**** #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors




Line 113: Line 130:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-04-26/commops.2016-04-26-15.57.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-04-26/commops.2016-04-26-15.57.log.html
|next-meeting=2016-05-03
|next-meeting=2016-05-03
}}
}}

Latest revision as of 05:56, 27 April 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-04-26

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-04-26)
  • #meetingname 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-04-19/commops.2016-04-19-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 === decause complete limesurvey account creation process ===
    • #info === [IN PROGRESS] decause Work on migrating the raw University Involvement Initiative notes from the Etherpad into a more parseable, digestible format (whether wiki or other format) ===
      • #agreed This action item is now Ticket #68. We will revisit this item later on in the meeting during ticket discussion.
    • #info === [IN PROGRESS] jflory7 Continue writing and compiling project profiles of BrickHack 2016 participants (three replies so far, need to keep communication channels open) ===
      • #action jflory7 Continue writing and compiling project profiles of BrickHack 2016 participants
    • #info === [INCOMPLETE] decause / jflory7 Ping Marketing mailing list about Alpha to Beta release announcement research for May 3rd ===
      • #action decause / jflory7 Ping Marketing mailing list about Alpha to Beta release announcement research for May 3rd
    • #info === [INCOMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
      • #action jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team
    • #info === [IN PROGRESS] decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
      • #action decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog
    • #info === [COMPLETE] jflory7 Upload the local Albanian F24 translation sprint group photo to the G11n vFAD article on the Community Blog ===
    • #info === [IN PROGRESS] justharshal / dhanesh95 Work on moving the Etherpad notes into a more readable format on the University Involvement Initiative wiki page; after converting it, send to CommOps mailing list for feedback and review ===
      • #agreed This action item is now Ticket #68. We will revisit this item later on in the meeting during ticket discussion.
    • #info === [INCOMPLETE] commops / jflory7 Create tickets for the above items 1-3 so they can be assigned and broken up among CommOps members ===
      • #action commops / jflory7 Create tickets for the above items 1-3 so they can be assigned and broken up among CommOps members
    • #info === [COMPLETE] jflory7 Review and edit "Fedora translation sprint" article for publication on Thursday, if possible ===
    • #info === [INCOMPLETE] jflory7 Ship the "Fedora Media Writer" article ASAP, contact author about dropping a link on the CommOps mailing list next time so we don't wind up last minute ===
      • #info This deadline was missed, was not published the day of the event :(






  • #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-04-26&oldid=444409"