From Fedora Project Wiki

(Remove wiki gardening from future agendas)
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 31: Line 31:
  
 
* '''#topic Announcements'''
 
* '''#topic Announcements'''
** #info === "" ===
+
** #info === "What is the Fedora Code of Conduct?" ===
*** #link  
+
*** #link https://communityblog.fedoraproject.org/what-is-fedora-code-conduct/
*** #info  
+
*** #info A quick introduction to the Fedora Code of Conduct and why such a thing is important.
** #info === "" ===
+
** #info === "Fedora 24 release party in Paris" ===
*** #link  
+
*** #link https://communityblog.fedoraproject.org/fedora-24-release-party-paris/
*** #info  
+
*** #info This month, a group of Fedora Ambassadors in Paris put together a release party for Fedora 24 and an introduction to the upcoming Fedora 25. Learn more about the event in their report.
** #info === "" ===
+
** #info === "Event Report: Fedora Women Day 2016, Kolkata" ===
*** #link  
+
*** #link https://communityblog.fedoraproject.org/fedora-women-day-2016-kolkata/
*** #info  
+
*** #info Over the summer, the Fedora Diversity Team helped organize a series of international events to celebrate Fedora Women Day. Read more about the events held in Kolkata over the summer.
 +
** #info === "On-boarding Kickoff: Fedora QA, Bhopal, India" ===
 +
*** #link https://communityblog.fedoraproject.org/on-boarding-fedora-qa-bhopal-india/
 +
*** #info A group of contributors in Bhopal, India, helped introduce potential contributors to Fedora and how to get involved with quality assurance.
 +
** #info === "Heroes of Fedora (HoF) – F24 Final" ===
 +
*** #link https://communityblog.fedoraproject.org/heroes-of-fedora-f24-final/
 +
*** #info The series introducing our testing heroes of Fedora recently concluded for F24. Check out the numbers in the report for the final parts of the release cycle for F24!
 +
** #info === "Outreachy - remote internships in Free and Open Source Software" ===
 +
*** #link https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject.org/thread/JJOYTD2ZAMFH53RCC32DFJ5FMO7GUAIY/
 +
*** #link https://fedoraproject.org/wiki/Outreachy/2016
 +
*** #info Outreachy 2016 is getting started in Fedora. Fedora is again participating in Outreachy this year with a single slot for a Fedora Hubs UI/UX intern. Learn more about the program in the mailing list thread and more about Fedora's involvement on the wiki page.
  
  
 
* '''#topic Action items from last meeting'''
 
* '''#topic Action items from last meeting'''
** #link  
+
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-09-13/commops.2016-09-13-16.27.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 emails for pending posts on the CommBlog ===
** #info === ===
+
*** #action jflory7 Review emails for pending posts on the CommBlog
** #info === ===
+
** #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
** #info === ===
+
** #info === [INCOMPLETE] skamath Research Bugzilla datagrepper queries for new bug report tickets ===
** #info === ===
+
** #info === [COMPLETE] sumantro a2batic File tickets in Fedora Badges Trac for filing Bugzilla bugs, for completing release validation testing, and getting sponsored to the QA group ===
 +
** #info === commops Review comments in ticket #78, reply and leave feedback with your thoughts when possible ===
 +
** #info === [INCOMPLETE] jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83 ===
 +
** #info === commops Leave feedback on suggestions or add your own ideas for improving the election cycles for December 2016 elections in ticket #90 ===
  
  
Line 97: Line 110:
  
 
* '''#topic Open Floor'''
 
* '''#topic Open Floor'''
|summary=
+
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-09-20/commops.2016-09-20-16.31.html
|log=
+
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-09-20/commops.2016-09-20-16.31.log.html
 
|next-meeting=2016-09-27
 
|next-meeting=2016-09-27
 
}}
 
}}

Latest revision as of 03:23, 23 September 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-09-20

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-09-20)
  • #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-09-13/commops.2016-09-13-16.27.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 emails for pending posts on the CommBlog ===
      • #action jflory7 Review emails for pending posts on the CommBlog
    • #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
    • #info === [INCOMPLETE] skamath Research Bugzilla datagrepper queries for new bug report tickets ===
    • #info === [COMPLETE] sumantro a2batic File tickets in Fedora Badges Trac for filing Bugzilla bugs, for completing release validation testing, and getting sponsored to the QA group ===
    • #info === commops Review comments in ticket #78, reply and leave feedback with your thoughts when possible ===
    • #info === [INCOMPLETE] jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83 ===
    • #info === commops Leave feedback on suggestions or add your own ideas for improving the election cycles for December 2016 elections in ticket #90 ===



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