From Fedora Project Wiki

(Add announcements)
(Add action items)
Line 46: Line 46:
** #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-09-06-16.25.html
** #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




Revision as of 14:17, 13 September 2016

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

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

Retrieved from "https://fedoraproject.org/w/index.php?title=Meeting:CommOps_2016-09-13&oldid=471007"