From Fedora Project Wiki

(Add minutes and logs)
 
Line 127: Line 127:
  
 
* '''#topic Open Floor'''
 
* '''#topic Open Floor'''
|summary=
+
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-07-12/commops.2016-07-12-15.55.html
|log=
+
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-07-12/commops.2016-07-12-15.55.log.html
 
|next-meeting=2016-07-19
 
|next-meeting=2016-07-19
 
}}
 
}}

Latest revision as of 17:41, 12 July 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-07-12

Meeting Time

Participants

This week's CommOps Meeting will be led by jflory7.

  • 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-07-12)
  • #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-07-05/commops.2016-07-05-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 === [COMPLETE] jflory7 Continue working through Community Blog queue after receiving feedback from authors ===
      • #info Article published today, good number coming out this week, still some more in the queue of being edited
    • #info === [COMPLETE] jflory7 Update Ticket #69 about Modularity WG on-boarding badge ticket ===
    • #info === [INCOMPLETE] skamath File a Pagure issue about adding listeners for tracking activity in forks via fedmsg ===
      • #action skamath File a Pagure issue about adding listeners for tracking activity in forks via fedmsg
    • #info === [COMPLETE] jflory7 Review and schedule SELF 2016 CommBlog post due:2016-07-12T12:00 ===
    • #info === [COMPLETE] jflory7 Take a look at the FOSCo status page closer, see if there's anything to add from CommOps / Marketing perspective ===
    • #info === [IN PROGRESS] commops Add thoughts and feedback about CommOps performance this release to the retrospective page ===
      • #action commops Add thoughts and feedback about CommOps performance this release to the retrospective page
    • #info === [COMPLETE] jflory7 Add personal thoughts to F24 CommOps retrospective ===
    • #info === [IN PROGRESS] skamath Figure out how to add statistics to the CommOps retrospective wiki ===






  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting