From Fedora Project Wiki

(Prepare next week's agenda)
 
(Add announcements, action items, Community Blog updates)
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === Last week: Fedora 24 no-go, delayed to June 21 ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/CCPEFDBYMHBNLTNG2CC57KUBBQOO67RD/
*** #info  
*** #info Due to a remaining blocker bug in F24, the release has been delayed by one week to June 21st, 2016. If all goes well, we should be back again here next week with a new Fedora release on our hands.
** #info === "" ===
** #info === Events coming soon: Red Hat Summit, Flock ===
*** #link  
*** #link https://www.redhat.com/en/summit
*** #info  
*** #link https://flocktofedora.org/
** #info === "" ===
*** #info Two upcoming events on the Fedora calendar are Red Hat Summit (June 27-29) and Flock, Fedora's annual contributor conference (August 2-5).
*** #link  
** #info === "Fedora Council Meeting 2016-06-13: Report on CommOps " ===
*** #info  
*** #link https://youtu.be/AQWybn1QVKc
*** #info Yesterday at the Fedora Council meeting, decause gave a report on the status, work, and accomplishments of the CommOps sub-project. Thanks to everyone who helped pull together information and the presentation yesterday! decause++ bee2502++ skamath++ meskarune++ commops++ It's worth a watch if you haven't checked it out already.




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06-07-15.58.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 === decause Follow up with tatica and diversity team about LimeSurvey availability ===
** #info === ===
** #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
** #info === ===
** #info === decause nail down Flock arrangements, add them to Fedocal ===
** #info === ===
** #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
** #info === ===
** #info === [COMPLETE] skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed ===
*** #link https://fedorahosted.org/fedora-badges/ticket/464
** #info === [COMPLETE] jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) ===
*** #link https://fedorahosted.org/fedora-commops/ticket/10#comment:5
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/GSZLMED2YQ3HNQVJDH6ETCJCWXZTRCIE/
** #info === [COMPLETE] jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on mizmo's feedback ===
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/L7VXDJD47JSB5O7UUQNUDTGZTSSTA7LB/
** #info === decause ship "final" version for review by EoB thursday of F24 GA Release Announcement ===
** #info === [COMPLETE] jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC ===
*** #link https://apps.fedoraproject.org/calendar/meeting/4145/
*** viorel++




Line 75: Line 86:
** #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) "Getting started with Fedora QA (Part 1)"
**** #link
**** #link https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/
**** #info Total Views (date - date):
**** #info Total Views (June 9 - June 14): 510
**** #link
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1608
*** #info (2) ""
**** #link  
**** #info Total Views (date - date):  
**** #link  
*** #info (3) ""
**** #link
**** #info Total Views (date - date):
**** #link
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "Cloud Working Group FAD"
**** #link  
**** #link https://public.etherpad-mozilla.org/p/fad-summary-2016-june
*** #info (2) ""
**** #info Written by jzb, looking at publishing this week.
**** #link  
*** #info (2) "Event Report: PyCon 2016"
*** #info (3) ""
**** #link https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=d3705befb7
**** #link  
*** #info (3) "Getting started with 'update-testing' Fedora QA part 2"
**** #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=8a0d20416e
*** #info (4) "Getting started with Fedora QA part 3"
**** #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=676163dcfd




Revision as of 14:32, 14 June 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-06-14

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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2016-06-14)
  • #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 Announcements
    • #info === Last week: Fedora 24 no-go, delayed to June 21 ===
    • #info === Events coming soon: Red Hat Summit, Flock ===
    • #info === "Fedora Council Meeting 2016-06-13: Report on CommOps " ===
      • #link https://youtu.be/AQWybn1QVKc
      • #info Yesterday at the Fedora Council meeting, decause gave a report on the status, work, and accomplishments of the CommOps sub-project. Thanks to everyone who helped pull together information and the presentation yesterday! decause++ bee2502++ skamath++ meskarune++ commops++ It's worth a watch if you haven't checked it out already.







  • #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-06-14&oldid=455431"