From Fedora Project Wiki

(Prepare agenda for a future day)
 
(Add announcements and action items)
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === Flock 2016 ended last week ===
*** #link  
*** #link https://communityblog.fedoraproject.org/flock-update-day-1/
*** #info  
*** #link https://communityblog.fedoraproject.org/flock-update-day-2/
** #info === "" ===
*** #link https://meetbot.fedoraproject.org/sresults/?group_id=flock2016&type=team
*** #link  
*** #info Flock, the annual Fedora contributor conference, ended last Friday. There were several talks and workshops on various topics, teams, and projects in Fedora. Watch the Community Blog for more updates and read the transcripts of some talks / workshops in Meetbot to stay current. Thanks to all organizers and sponsors for helping make this year's Flock successful!
*** #info  
*** #idea "Thank you" letter post to organizers / sponsors on the Community Blog?
** #info === "" ===
** #info === Ultimate Women's Fedora t-shirt ===
*** #link  
*** #link https://www.unixstickers.com/tshirts-and-hoodies/t-shirts/the-ultimate-fedora-woman-tshirt
*** #info  
*** #info Unixstickers just released a women's fit version of their ultimate Fedora t-shirt. Pick one up for yourself or a friend! More on this coming soon on the Community Blog!
*** #action jflory7 Write a promo on the CommBlog about the ultimate women's Fedora t-shirt
** #info === "Fedora Account System (FAS) security issue" ===
*** #link https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/3GQR7CKGKM5TZCCH7FHFW55HSZE72VEL/
*** #info There was a security vulnerability identified and fixed in FAS this week. No known exploits at this time, but Infrastructure team is monitoring and investigating further. If more information is found later, it will be shared.




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-07-26/commops.2016-07-26-15.57.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 === [COMPLETE] jflory7 Review and edit July 2016 Election retrospective post by jkurik after CommOps meeting ===
** #info === ===
*** #link https://communityblog.fedoraproject.org/elections-retrospective-july-2016/
** #info === ===
** #info === skamath file a ticket on fedmsg repo for the mailman bug ===
** #info === ===
** #info === [INCOMPLETE] jflory7 Work on drafting an article about the Flock 2016 CommOps workshop for Community Blog ===
** #info === ===
*** #info No longer relevant to do so... a post-workshop report would be better
*** #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
** #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
*** #action jflory7 Review emails for pending posts on the CommBlog
*** There are more since Flock!
** #info === [INCOMPLETE] jflory7 Write an article stub announcing Fedora 25's existence, separate from Rawhide today ===
*** #info No longer relevant... be more on top of things for Alpha





Revision as of 14:04, 9 August 2016

Fedora CommOps Team Meeting Minutes 2016-08-09

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

CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-08-09)
  • #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-26/commops.2016-07-26-15.57.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 Review and edit July 2016 Election retrospective post by jkurik after CommOps meeting ===
    • #info === skamath file a ticket on fedmsg repo for the mailman bug ===
    • #info === [INCOMPLETE] jflory7 Work on drafting an article about the Flock 2016 CommOps workshop for Community Blog ===
      • #info No longer relevant to do so... a post-workshop report would be better
      • #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
    • #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
      • #action jflory7 Review emails for pending posts on the CommBlog
      • There are more since Flock!
    • #info === [INCOMPLETE] jflory7 Write an article stub announcing Fedora 25's existence, separate from Rawhide today ===
      • #info No longer relevant... be more on top of things for Alpha




  • #topic Community Blog
    • #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 (1) ""
        • #link
        • #info Total Views (date - date):
        • #link
      • #info (2) ""
        • #link
        • #info Total Views (date - date):
        • #link
      • #info (3) ""
        • #link
        • #info Total Views (date - date):
        • #link
    • #info === Coming Up in CommBlog ===
      • #info (1) ""
        • #link
      • #info (2) ""
        • #link
      • #info (3) ""
        • #link



  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting