From Fedora Project Wiki

(Add Ticket #74)
(Add minutes and logs)
 
Line 143: Line 143:


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

Latest revision as of 17:15, 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=446163"