From Fedora Project Wiki

(Add action items and Community Blog section)
(Add tickets and announcements)
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Fedora 24 Beta released!" ===
*** #link  
*** #link https://fedoramagazine.org/fedora-24-beta-released/
*** #info  
*** #info Today is the day! Wait no more! F24 Beta is rolling out to mirrors near you soon! The F24 Beta is out. Thanks to all who helped contribute to the release announcement!
** #info === "" ===
** #info === "Fedora’s Love For Python Continues" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedoras-love-python-continues/
*** #info  
*** #info New brochures about Python in Fedora are available for Ambassadors and other interested groups. Feel free to take them and print some of your own! mizmo++ bkp++ pythonSIG++
** #info === "" ===
** #info === Fedora Diversity team meetings ===
*** #link  
*** #link https://fedoraproject.org/wiki/Diversity_Adviser
*** #info  
*** #info The Fedora Diversity team, led by tatica, meets every other Tuesday at 12:30 UTC. The next meeting will be May 24 2016, 12:30 UTC. If you are interested in contributing or learning more, join #fedora-diversity and join the mailing list.
*** #link https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org/
** #info === Fedora Women Day ===
*** #link https://fedoraproject.org/wiki/Fedora_Women_Day_2016
*** #info Fedora Women Day is a virtual event for the weekend of July 15-17. Planning is still underway, but if you are interested, please follow the wiki page.




Line 80: Line 84:
* '''#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  
*** Mostly working through previous items and getting up to speed (not much new to report). Last action item was to refine our own Join process as the testing bed for the onboarding process badges. Do we want to do any other planning now or continue to work through the existing queue of tasks?
*** 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 http://etherpad.osuosl.org/fedora-EDU-refresh
*** description
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
*** #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative/draft
*** dhanesh95 has made a lot of awesome progress already and sent a request for feedback to the mailing list. Should be ready to merge into the main page. If no objections, this can be done ASAP.
** #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
*** Progress was made at the last hack session, but follow-up is needed with the Modularity WG to hear their feedback on our ideas and plans. A blog post announcing the WG is also forthcoming.
** #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). jflory7 was to open discussion on the list at last meeting (but was unable to do so before the meeting).




* '''#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 ]
** #help Fork the PyCon 2015 event page and udpate it with the latest info




Revision as of 15:49, 10 May 2016

Fedora CommOps Team Meeting Minutes 2016-05-10

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

CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-05-10)
  • #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-05-03/commops.2016-05-03-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 === [INCOMPLETE] decause / jflory7 create a quick pointer to the DOCs FAD Wiki for commblog ===
      • #info Deadline passed for announcement about Docs FAD - can we get an event report up?
    • #info === decause fill up the LimeSurvey account with moneydollars ===
    • #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 === [INCOMPLETE] decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
      • #action 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 === 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 === skamath help with gardening of Summer Coding wiki ===
    • #info === CommOps start a stub for a vFAD over the summer (before Flock) ===
    • #info === [INCOMPLETE] jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
    • #info === [INCOMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
    • #info === [COMPLETE] jflory7 Schedule "Python + Fedora brochures" article for Thursday ===
    • #info === [COMPLETE] jflory7 Check in with gnokii about when to ship the F24 Release Parties article ===
    • #info === [COMPLETE] jflory7 Ping mailing lists about F24 Beta Release Announcement again, deadline: Friday ===
    • #info === [INCOMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
      • #action jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list
    • #info === [INCOMPLETE] drewmeigs check in with decause and jflory7 on meeting agendas and Meetbot ===
      • This one was on jflory7
      • #action jflory7 Pass information to drewmeigs about preparing next week's meeting agenda



  • #topic Wiki Gardening
    • #action CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
    • #help Fork the PyCon 2015 event page and udpate it with the latest info




  • #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-10&oldid=446156"