From Fedora Project Wiki

(Prepare future meeting template)
 
(Add minutes and logs)
 
(2 intermediate revisions by 2 users not shown)
Line 6: Line 6:
|MINUTE=30
|MINUTE=30
|CHANNEL=#fedora-meeting
|CHANNEL=#fedora-meeting
|CHAIR=jflory7
|CHAIR=rhea
|agenda=* '''#startmeeting Fedora CommOps (2016-11-01)'''
|agenda=* '''#startmeeting Fedora CommOps (2016-11-01)'''
* '''#meetingname commops'''
* '''#meetingname commops'''
Line 31: Line 31:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Fedora at LinuxCon Europe 2016" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedora-linuxcon-europe-2016
*** #info  
*** #info The Fedora community did not miss this years LinuxCon Europe either, which took place on Oct 4-6.
** #info === "" ===
** #info === "Flock Stories 2016, Episode 1: Redon Skikuli" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/flock-stories-2016-redon-skikuli
*** #info  
*** #info Flock Stories podcast interviewed Redon Skikuli.
** #info === "" ===
** #info === "FOSS Wave: Indore, India" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/foss-wave-indore-india
*** #info  
*** #info FOSS Wave and Mozilla Indore community conducted an event at the Indian Institute of Technology in Indore, India on 24th September 2016




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-10-25/commops.2016-10-25-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 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 === ===
** #nick jflory7
** #info === ===
** #info === [INCOMPLETE] jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list ===
** #info === ===
*** #action jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list
** #info === ===
** #info === [INCOMPLETE] 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 === ===
*** #action 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 === [COMPLETE] jflory7 Process and review pending Community Blog articles for publishing ===
*** #info All pending posts processed and scheduled
** #info === [INCOMPLETE] jflory7 Post to the mailing list breaking down how to help with Ticket #93 ===
*** #action jflory7 Post to the mailing list breaking down how to help with Ticket #93
** #info === [COMPLETE] Rhea File ticket in CommOps Pagure for on-boarding help with Dotnet SIG, particular to: (1) what you have created, (2) things you think would be helpful, and (3) areas you think could use some extra brainstorming or thinking from others ===
*** #link https://pagure.io/fedora-commops/issue/95




* '''#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 #93 ===
*** #info ""
*** #info "Elections: Better explain roles of Council and FESCo"
*** #link https://pagure.io/fedora-commops/issue/xx
*** #link https://pagure.io/fedora-commops/issue/93
*** description
*** #info As part of the Elections discussion in #90, it would be helpful to better explain the roles of the Fedora Council and FESCo to motivate new candidates to run for election.
** #info === Ticket #xx ===
** #info === Ticket #44 ===
*** #info ""
*** #info "Talking Points: EDU"
*** #link https://pagure.io/fedora-commops/issue/xx
*** #link https://pagure.io/fedora-commops/issue/44
*** description
*** #info Resuming previous discussion about generating talking points about EDU outreach by Fedorans in academic settings. Talking points would make it easier for a student, faculty, or staff member at a school to help promote Fedora among their peers or in the university itself.
** #info === Ticket #xx ===
** #info === Ticket #95 ===
*** #info ""
*** #info "[Onboarding Series] DotNet SIG"
*** #link https://pagure.io/fedora-commops/issue/xx
*** #link https://pagure.io/fedora-commops/issue/95
*** description
*** description  




Line 97: Line 103:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2016-11-01/commops.2016-11-01-16.29.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2016-11-01/commops.2016-11-01-16.29.log.html
|next-meeting=2016-11-08
|next-meeting=2016-11-08
}}
}}

Latest revision as of 04:51, 2 November 2016

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2016-11-01

Meeting Time

Participants

This week's CommOps Meeting will be led by rhea.

  • 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-11-01)
  • #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-10-25/commops.2016-10-25-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.
    • #nick jflory7
    • #info === [INCOMPLETE] jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list ===
      • #action jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list
    • #info === [INCOMPLETE] 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 ===
      • #action 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 === [COMPLETE] jflory7 Process and review pending Community Blog articles for publishing ===
      • #info All pending posts processed and scheduled
    • #info === [INCOMPLETE] jflory7 Post to the mailing list breaking down how to help with Ticket #93 ===
      • #action jflory7 Post to the mailing list breaking down how to help with Ticket #93
    • #info === [COMPLETE] Rhea File ticket in CommOps Pagure for on-boarding help with Dotnet SIG, particular to: (1) what you have created, (2) things you think would be helpful, and (3) areas you think could use some extra brainstorming or thinking from others ===


  • #topic Tickets


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