From Fedora Project Wiki

(Prepare future agenda)
 
(Add minutes and logs)
 
(3 intermediate revisions by the same user not shown)
Line 30: Line 30:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Help translate the Fedora User Handbook" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/translate-fedora-user-handbook/
*** #info
*** #help Native English speakers are needed to help bring the Fedora user handbook to English. Check out this CommBlog post to see how you can help.
** #info === "" ===
** #info === "Share Fedora: Difficult Conversations" ===
*** #link  
*** #link https://fedoramagazine.org/share-fedora-difficult-conversations/
*** #info  
*** #info The Opensource.com blogging challenge continues this week, asking for people like you to share your experience about open source communities. This week's topic are difficult conversations. Check it out on the Fedora Magazine.
** #info === "" ===
** #info === "FLISoL 2017 – Linux in Latin America" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/flisol-2017-linux-latin-america/
*** #info  
*** #info FLISoL is an international open source event held across LATAM each year since 2005. Fedora was a part of it, and you can get a quick overview in this introductory article by x3mboy!




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-04-11-16.29.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] jwf File ticket upstream with FAmSCo about Ambassador event reports ===
** #info === ===
*** #link https://pagure.io/famsco/issue/422
** #info === ===
** #info === [COMPLETE] jwf Assign ticket #70 to x3mboy ===
*** #link https://pagure.io/fedora-commops/issue/70
** #info === [COMPLETE] bee2502 File ticket #108 on geographic-based metrics :) ===
*** #link https://pagure.io/fedora-commops/issue/109
** #info === [IN PROGRESS] jwf Continue working on new editor guidelines for how folks can help with editing / scheduling articles ===
*** #action jwf Continue working on new editor guidelines for how folks can help with editing / scheduling articles
** #info === [COMPLETE] jwf Share the hack session details on the mailing list ===




* '''#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 #70: "FOSS Student Pack" ===
*** #link https://pagure.io/fedora-commops/issue/xx
*** #link https://pagure.io/fedora-commops/issue/70
** #info === Ticket #xx: "" ===
** #info === Ticket #92: "Start a yearly Fedora Appreciation Day" ===
*** #link https://pagure.io/fedora-commops/issue/xx
*** #link https://pagure.io/fedora-commops/issue/92
** #info === Ticket #xx: "" ===
*** #link https://pagure.io/fedora-commops/issue/xx




* '''#topic Community Blog'''
* '''#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 Skipping for this week, will pick up in time next week!
** #info === This Week in CommBlog ===
*** #info (1) "" -
**** #link
**** #info Total Views ( - ):
**** #link
*** #info (2) "" -
**** #link
**** #info Total Views ( - ):
**** #link
** #info === Coming Up in CommBlog ===
*** #info (1) ""
**** #link
*** #info (2) ""
**** #link




* '''#topic Open floor'''
* '''#topic Open floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2017-04-25/commops.2017-04-25-16.30.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2017-04-25/commops.2017-04-25-16.30.log.html
|next-meeting=2017-05-02
|next-meeting=2017-05-02
}}
}}

Latest revision as of 06:56, 27 April 2017

Fedora CommOps Team Meeting Minutes 2017-04-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 (2017-04-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 Action items from last meeting
    • #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-04-11-16.29.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 === [COMPLETE] jwf File ticket upstream with FAmSCo about Ambassador event reports ===
    • #info === [COMPLETE] jwf Assign ticket #70 to x3mboy ===
    • #info === [COMPLETE] bee2502 File ticket #108 on geographic-based metrics :) ===
    • #info === [IN PROGRESS] jwf Continue working on new editor guidelines for how folks can help with editing / scheduling articles ===
      • #action jwf Continue working on new editor guidelines for how folks can help with editing / scheduling articles
    • #info === [COMPLETE] jwf Share the hack session details on the mailing list ===



  • #topic Community Blog
    • #info Skipping for this week, will pick up in time next week!


  • #topic Open floor

Meeting summary and action items

Full meeting log

Next Meeting

Retrieved from "https://fedoraproject.org/w/index.php?title=Meeting:CommOps_2017-04-25&oldid=491793"