From Fedora Project Wiki

(Add action items)
(Begin announcements, CommBlog sections)
Line 31: Line 31:
  
 
* '''#topic Announcements'''
 
* '''#topic Announcements'''
** #info === "" ===
+
** #info === "Some preliminary Fedora 25 stats — and future release scheduling" ===
*** #link  
+
*** #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DTXEZ3UACKA6VIVMVNCPLTB336BXIFJI/
 +
*** #info mattdm shared some statistics related to the recent release, along with a proposal that Fedora should consider a yearly release cycle instead of six months. More discussion follows in the thread.
 +
** #info === "Fedora 26 release dates and schedule" ===
 +
*** #link https://communityblog.fedoraproject.org/fedora-26-release-dates-schedule/
 +
*** #info The tentative schedule for Fedora 26 is announced. You can check what the next release cycle is looking like so far in the above post.
 +
** #info === "Heroes of Fedora (HoF) – F25 Final" ===
 +
*** #link https://communityblog.fedoraproject.org/heroes-of-fedora-hof-f25-final/
 
*** #info  
 
*** #info  
** #info === "" ===
+
** #info === "Introducing Fedora Hubs" ===
*** #link  
+
*** #link https://fedoramagazine.org/fedora-hubs/
*** #info
 
** #info === "" ===
 
*** #link
 
 
*** #info  
 
*** #info  
  
Line 82: Line 85:
 
** #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 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 === This Week in CommBlog ===
*** #info (1) ""
+
*** #info (1) "Heroes of Fedora (HoF) – F25 Final"
**** #link
+
**** #link https://communityblog.fedoraproject.org/heroes-of-fedora-hof-f25-final/
**** #info Total Views (date - date):
 
**** #link
 
*** #info (2) ""
 
**** #link  
 
 
**** #info Total Views (date - date):  
 
**** #info Total Views (date - date):  
 
**** #link  
 
**** #link  
*** #info (3) ""
+
*** #info (2) "Fedora 26 release dates and schedule"
**** #link  
+
**** #link https://communityblog.fedoraproject.org/fedora-26-release-dates-schedule/
 
**** #info Total Views (date - date):  
 
**** #info Total Views (date - date):  
 
**** #link  
 
**** #link  

Revision as of 16:47, 6 December 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-12-06

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-12-06)
  • #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
    • #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
    • 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-11-29/commops.2016-11-29-17.28.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 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket ===
    • #info === [INCOMPLETE] FranciscoD Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.) ===
      • #action FranciscoD Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.)
    • #info === [COMPLETE] jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting ===
    • #info === [COMPLETE] meskarune File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position ===
    • #info === [COMPLETE] dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016 ===
    • #info === [INCOMPLETE] jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016 ===
      • #action jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016
    • #info === [COMPLETE] jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week ===
    • #info === [COMPLETE] jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok ===



  • #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 === 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