From Fedora Project Wiki

(Make minor adjustments to template)
(Add minutes and logs)
 
(5 intermediate revisions by the same user not shown)
Line 32: Line 32:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Chomreabsuor Phnom Penh — FUDCon APAC is coming!" ===
*** #link  
*** #link https://fedoramagazine.org/chomreabsuor-phnom-penh-fudcon-apac-is-coming/
*** #info  
*** #info The Fedora User and Developer Conference, or FUDCon, is coming to the APAC region in Phnom Penh. Learn more about how to participate in this year's conference in the above link.
** #info === "" ===
** #info === "Fedorahosted sunset: 2017-02-28" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/
*** #info  
*** #info All Fedorahosted instances are being retired on February 28, 2017. Marketing has already moved to Pagure and will set our Trac as a redirect to Pagure at the end of this month. Keep this in mind for any other teams you are participating in as well.
** #info === "" ===
** #info === Fedora 25 translation sprint ended last Friday ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedora-25-translation-sprint/
*** #info  
*** #info The Fedora Globalization (G11n) team wrapped up another translation sprint last week for Fedora 25. Expect more news about the outcome and results soon!




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-09-06-16.25.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 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
** #info === ===
*** #link https://etherpad.gnome.org/p/commops-power-sessions
** #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 === [COMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
*** #link https://communityblog.fedoraproject.org/writing-community-blog-article/
** #info === [COMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
*** #link https://pagure.io/fedora-commops/issue/78#comment-6146
** #info === skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
** #info === [COMPLETE] jflory7 bee2502 Arrange for some personal hacking to close out Flock items ===
*** #link https://etherpad.gnome.org/p/commops-power-sessions
** #info === [COMPLETE] dhanesh95 Start mailing list discussion on wiki page changes for Python SIG ===
*** #link https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/QPLFFRRDFG7E3CVN67ZI7DX34I3KTRQK/
** #info === [COMPLETE] bee2502 jflory7 Work on moving election-specific information from Flock into ticket #19, share with jkurik after ===
*** #link https://pagure.io/fedora-commops/issue/90
** #info === skamath Research Bugzilla datagrepper queries for new bug report tickets ===
** #info === 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 === dhanesh95 Make changes to Python SIG pages based on feedback, post to python-devel mailing list requesting feedback on the rewrites, explain idea of splitting Python SIG into two FAS groups (python-sig for interested members, python-packagers for security-related bugs / pushing to packages git) ===
** #info === [COMPLETE] skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time ===
*** #link https://pagure.io/fedora-commops/issue/86#comment-6106
** #info === [COMPLETE] jflory7 Close ticket #86 no sooner than 2016-09-08 ===
*** #link https://pagure.io/fedora-commops/issue/86#comment-6106




* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #info === Ticket #xx ===
** #info === Ticket #34, 52, 84 ===
*** #link https://pagure.io/fedora-commops/issue/xx
*** #info " [Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series; Quality Assurance; Python SIG"
*** #info ""
*** #link https://pagure.io/fedora-commops/issue/34
*** description
*** #link https://pagure.io/fedora-commops/issue/52
** #info === Ticket #xx ===
*** #link https://pagure.io/fedora-commops/issue/84
*** #link https://pagure.io/fedora-commops/issue/xx
***  
*** #info ""
** #info === Ticket #78 ===
*** description
*** #info "Automating a check-in to evaluate activity of members"
** #info === Ticket #xx ===
*** #link https://pagure.io/fedora-commops/issue/78
*** #link https://pagure.io/fedora-commops/issue/xx
***
*** #info ""
** #info === Ticket #83 ===
*** description
*** #info "replace/improve etherpad working space"
*** #link https://pagure.io/fedora-commops/issue/83
***
** #info === Ticket #87 ===
*** #info "Replacement for join.fp.o"
*** #link https://pagure.io/fedora-commops/issue/87
***
** #info === Ticket #90 ===
*** #info "Improving Fedora Elections Process."
*** #link https://pagure.io/fedora-commops/issue/90
***




Line 75: Line 102:
** #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) "What are Personas and why should you care?"
**** #link  
**** #link https://communityblog.fedoraproject.org/what-are-personas-and-why-care/
**** #info Total Views (date - date):  
**** #info Total Views (Sept. 6 - Sept. 13): 377
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2230
*** #info (2) ""
*** #info (2) "Fedorahosted sunset: 2017-02-28"
**** #link  
**** #link https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/
**** #info Total Views (date - date):  
**** #info Total Views (Sept. 7 - Sept. 13): 347
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2415
*** #info (3) ""
*** #info (3) "Heroes of Fedora (HoF) – F24 Alpha"
**** #link  
**** #link https://communityblog.fedoraproject.org/heroes-of-fedora-f24-alpha/
**** #info Total Views (date - date):  
**** #info Total Views (Sept. 8 - Sept. 13): 49
**** #link  
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2091
*** #info (4) "Heroes of Fedora (HoF) – F24 Beta"
**** #link https://communityblog.fedoraproject.org/heroes-of-fedora-f24-beta/
**** #info Total Views (Sept. 9 - Sept. 13): 46
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2142
*** #info (5) "Heroes of Fedora (HoF) – F24 Final"
**** #link https://communityblog.fedoraproject.org/heroes-of-fedora-f24-final/
**** #info Total Views (Sept. 13): 13
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2204
** #info === Coming Up in CommBlog ===
** #info === Coming Up in CommBlog ===
*** #info (1) ""
*** #info (1) "FOSS Wave: FOSS and Fedora in Bangalore, India"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=2282&preview=1&_ppp=b8d2ca20a3
*** #info (2) ""
*** #info (2) "Event Report: WWFS-FWD'2016, Kolkata"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=2046&preview=1&_ppp=47d4be50af
*** #info (3) ""
*** #info (3) "Onboarding Kickoff - Fedora QA, Bhopal"
**** #link  
**** #link https://communityblog.fedoraproject.org/?p=2188&preview=1&_ppp=d59acc504d
*** #info (4) "Fedora 24 release party in Paris"
**** #link https://communityblog.fedoraproject.org/?p=2380&preview=1&_ppp=3bc720def1




Line 101: Line 138:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-09-13/commops.2016-09-13-16.27.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-09-13/commops.2016-09-13-16.27.log.html
|next-meeting=2016-09-20
|next-meeting=2016-09-20
}}
}}

Latest revision as of 17:57, 13 September 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-09-13

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-13)
  • #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 Wiki Gardening




  • #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-09-13&oldid=471017"