From Fedora Project Wiki

(Temporary save)
No edit summary
Line 49: Line 49:
** #link  
** #link  
** #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 === downey Ping jflory7 for editing article / adding paragraph into article ===
** #info === ===
** #info === jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
** #info === ===
** #info === jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
** #info === ===
** #info === jflory7 Review emails for pending posts on the CommBlog ===
** #info === ===
** #info === jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
** #info === jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
** #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
*** #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
** #info === jflory7 Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group ===
** #info === jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal ===
** #info === jflory7 Revisit wiki spam article with context of current situation with FAS groups ===
 




Revision as of 15:27, 30 August 2016

Fedora CommOps Team Meeting Minutes 2016-08-30

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-08-30)
  • #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 Action items from last meeting
    • #link
    • #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 === downey Ping jflory7 for editing article / adding paragraph into article ===
    • #info === jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
    • #info === jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
    • #info === jflory7 Review emails for pending posts on the CommBlog ===
    • #info === jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
    • #info === jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
    • #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
      • #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
    • #info === jflory7 Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group ===
    • #info === jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal ===
    • #info === jflory7 Revisit wiki spam article with context of current situation with FAS groups ===




  • #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-08-30&oldid=469792"