From Fedora Project Wiki

(Complete more action items)
(Complete action item for election role explanation)
Line 46: Line 46:
** #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 === skamath Follow up with Infrastructure team on fas=>bz email lookup rules and whether a fix can be made to gracefully handle failed lookups ===
** #info === skamath Follow up with Infrastructure team on fas=>bz email lookup rules and whether a fix can be made to gracefully handle failed lookups ===
** #info === jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article ===
** #info === [COMPLETE] jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article ===
*** #link https://pagure.io/fedora-commops/issue/93
** #info === [COMPLETE] jflory7 Reach out to skamath about Infrastructure / Bugzilla+FAS lookup rules ===
** #info === [COMPLETE] jflory7 Reach out to skamath about Infrastructure / Bugzilla+FAS lookup rules ===
** #info === jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day ===
** #info === jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day ===

Revision as of 15:13, 23 October 2016

Fedora CommOps Team Meeting Minutes 2016-10-25

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-10-25)
  • #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 Announcements
    • #info === "" ===
      • #link
      • #info
    • #info === "" ===
      • #link
      • #info
    • #info === "" ===
      • #link
      • #info


  • #topic Action items from last meeting
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-10-18/commops.2016-10-18-16.30.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 === skamath Follow up with Infrastructure team on fas=>bz email lookup rules and whether a fix can be made to gracefully handle failed lookups ===
    • #info === [COMPLETE] jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article ===
    • #info === [COMPLETE] jflory7 Reach out to skamath about Infrastructure / Bugzilla+FAS lookup rules ===
    • #info === jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day ===
    • #info === jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process ===
    • #info === [COMPLETE] jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list ===
      • #info Discussed during meetings, have selected Marketing + G11n
    • #info === jflory7 Take the discussion points from today's meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket ===
    • #info === jflory7 Process and review pending Community Blog articles for publishing ===



  • #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-10-25&oldid=477754"