From Fedora Project Wiki

m (Line break)
(Add action items)
Line 43: Line 43:
  
 
* '''#topic Action items from last meeting'''
 
* '''#topic Action items from last meeting'''
** #link  
+
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-06-14-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 review the vFAD goals/objectives/etc ===
** #info === ===
+
** #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
** #info === ===
+
** #info === decause nail down Flock arrangements and add to fedocal ===
** #info === ===
+
** #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
** #info === ===
+
** #info === decause Finish "final" version of F24 GA Release Announcement for review after go/no-go meeting on Thursday ===
 +
** #info === [COMPLETE] jflory7 Create a WhenIsGood and share with CommOps mailing list to decide on vFAD dates of July 2-3 or June 25-26 ===
 +
*** #link http://goo.gl/forms/ck9Dcxb9vqo6jqh62
 +
*** #info Mixed results, but low response rate on the poll. Will discuss during Ticket #10.
 +
** #info === [COMPLETE] jflory7 Write YAML file for CommOps on-boarding badge based on FAS group sponsorship ===
 +
*** #link https://fedorahosted.org/fedora-badges/ticket/464#comment:2
 +
** #info === jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
 +
***
 +
** #info === [COMPLETE] commops File a ticket on the Pagure repository for Fedora Hubs about creating a News widget that aggregates different sources of information and puts it together for easy consumption by a reader ===
 +
***
 +
** #info === [COMPLETE] jflory7 Update Ticket #71 with the "WHY" perspective in relation to FOSCo ===
 +
*** #link https://fedorahosted.org/famsco/ticket/373#comment:23
 +
*** #info Added the info to the relevant ticket on the FAmSCo Trac
 +
** #info === decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page ===
 +
** #info === [COMPLETE] jflory7 Look into filing a ticket on Pagure for CCing users / lists from a Pagure issue ===
 +
*** #link https://pagure.io/pagure/issue/746
  
  

Revision as of 05:45, 21 June 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-06-21

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-21)
  • #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 === "" ===
      • #link
      • #info
    • #info === "" ===
      • #link
      • #info
    • #info === "" ===
      • #link
      • #info


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-06-14-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 === decause review the vFAD goals/objectives/etc ===
    • #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
    • #info === decause nail down Flock arrangements and add to fedocal ===
    • #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
    • #info === decause Finish "final" version of F24 GA Release Announcement for review after go/no-go meeting on Thursday ===
    • #info === [COMPLETE] jflory7 Create a WhenIsGood and share with CommOps mailing list to decide on vFAD dates of July 2-3 or June 25-26 ===
    • #info === [COMPLETE] jflory7 Write YAML file for CommOps on-boarding badge based on FAS group sponsorship ===
    • #info === jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity ===
    • #info === [COMPLETE] commops File a ticket on the Pagure repository for Fedora Hubs about creating a News widget that aggregates different sources of information and puts it together for easy consumption by a reader ===
    • #info === [COMPLETE] jflory7 Update Ticket #71 with the "WHY" perspective in relation to FOSCo ===
    • #info === decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page ===
    • #info === [COMPLETE] jflory7 Look into filing a ticket on Pagure for CCing users / lists from a Pagure issue ===




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