From Fedora Project Wiki

(Prepare future meeting agenda)
 
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 3: Line 3:
|MONTH=02
|MONTH=02
|DAY=21
|DAY=21
|HOUR=16
|HOUR=17
|MINUTE=30
|MINUTE=30
|CHANNEL=#fedora-meeting
|CHANNEL=#fedora-meeting
Line 30: Line 30:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "North America and Fedora: Year in Review" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/
*** #info  
*** #info A quick overview of the past year's events in North America by the Ambassadors. A good overview of the activities and what all is going on in the North American continent with Fedora!
** #info === "" ===
** #info === "[release] pagure: 2.13" ===
*** #link  
*** #link https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/4KHO6XZCMU6NUB4OC5T6GDGHHKV6D72F/
*** #info  
*** #info A new version of Pagure was released and pushed to the staging instance. It will likely make it ways over to production in the next few days.
** #info === "" ===
** #info === Marketing team: "Create Fedora 26 talking points" ===
*** #link  
*** #link https://pagure.io/fedora-marketing/issue/245#comment-193454
*** #info  
*** #info Ongoing discussion in the Marketing Team to choose and narrow down target audiences for talking points. Knowing target audiences of Fedora 26 is also of interest to us too – feel free to follow along in the ticket!




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/commops.2017-02-14-17.31.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] bt0 Add bulletpoint list with a quick summary of each major area to the top of fp.o/wiki/Join page, close ticket #62 when completed ===
** #info === ===
*** #link https://pagure.io/fedora-commops/issue/62#comment-193447
** #info === ===
** #info === [INCOMPLETE] jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts ===
*** #action jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
** #info === [INCOMPLETE] jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed ===
*** #action jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed
** #info === [COMPLETE] jwf Add pictures sent from award3535 to post, create featured image, schedule ASAP ===
*** #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/




* '''#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 #21: "Ambassadors - Event Report Template" ===
*** #link https://pagure.io/fedora-commops/issue/xx
*** #link https://pagure.io/fedora-commops/issue/21
** #info === Ticket #xx: "" ===
*** #info This is an older ticket that we wanted to try to revisit this release cycle. To best approach this, it's worth discussing what type of content event reports should tell. What narrative are we looking for? What should Ambassadors focus on in their event reports? Does it differ from region to region? Let's focus on determining the goals and aims of what an Ambassador event report should have.
*** #link https://pagure.io/fedora-commops/issue/xx
** #info === Ticket #43: "EDU Roster" ===
** #info === Ticket #xx: "" ===
*** #link https://pagure.io/fedora-commops/issue/43
*** #link https://pagure.io/fedora-commops/issue/xx
*** #info We also wanted to follow up on this ticket this release cycle. This one focuses on building an active list or directory of active Fedora contributors who are involved with universities or schools already. Ideally, this people would be "first adopters" of any efforts we aim for with education-related outreach, like in the Marketing team. But where is the best place to keep and maintain this data?
** #info === Ticket #70: "FOSS Student Pack" ===
*** #link https://pagure.io/fedora-commops/issue/70
*** #info Another older ticket to circle back to for this release cycle and possibly the next. This could have two different audiences. Do we want a student pack for new contributors to Fedora with resources for getting them started? Do we want to feature cool Fedora apps or general infrastructure a student could use for any open source project? What are the goals of a student pack and what do we want to get out of it? What should the student get out of it?
 


* '''#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 === This Week in CommBlog ===
*** #info (1) "North America and Fedora: Year in Review" - award3535++
**** #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/
**** #info Total Views (Feb. 17 - Feb. 21): 186
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3412
** #info === Coming Up in CommBlog ===
*** #info (1) "TAFFY – Tucson Arizona Fedora Fanatic Yeasayers" - schyken
**** #link https://communityblog.fedoraproject.org/?p=3390&preview=1&_ppp=58c9663ba4
*** #info (2) "Google Summer of Code (GSoC) 2017: Mentors and ideas needed!" - rhea
**** #link https://communityblog.fedoraproject.org/?p=3454&preview=1&_ppp=98546c028c
*** #info (3) "University Connect – PCCOE , Pune" - amsharma
**** #link https://communityblog.fedoraproject.org/?p=3448&preview=1&_ppp=956558f7e1
*** #info (4) "University Connect - D. Y. Patil College, Pune"
**** #link https://communityblog.fedoraproject.org/?p=3439&preview=1&_ppp=c0cada9663




* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/commops.2017-02-21-17.30.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/commops.2017-02-21-17.30.log.html
|next-meeting=2017-02-28
|next-meeting=2017-02-28
}}
}}

Latest revision as of 19:25, 21 February 2017

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2017-02-21

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

Important.png
CommOpsers, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora CommOps (2017-02-21)
  • #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/2017-02-14/commops.2017-02-14-17.31.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] bt0 Add bulletpoint list with a quick summary of each major area to the top of fp.o/wiki/Join page, close ticket #62 when completed ===
    • #info === [INCOMPLETE] jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts ===
      • #action jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
    • #info === [INCOMPLETE] jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed ===
      • #action jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed
    • #info === [COMPLETE] jwf Add pictures sent from award3535 to post, create featured image, schedule ASAP ===


  • #topic Tickets
    • #link https://pagure.io/fedora-commops/issues?tags=meeting
    • #info === Ticket #21: "Ambassadors - Event Report Template" ===
      • #link https://pagure.io/fedora-commops/issue/21
      • #info This is an older ticket that we wanted to try to revisit this release cycle. To best approach this, it's worth discussing what type of content event reports should tell. What narrative are we looking for? What should Ambassadors focus on in their event reports? Does it differ from region to region? Let's focus on determining the goals and aims of what an Ambassador event report should have.
    • #info === Ticket #43: "EDU Roster" ===
      • #link https://pagure.io/fedora-commops/issue/43
      • #info We also wanted to follow up on this ticket this release cycle. This one focuses on building an active list or directory of active Fedora contributors who are involved with universities or schools already. Ideally, this people would be "first adopters" of any efforts we aim for with education-related outreach, like in the Marketing team. But where is the best place to keep and maintain this data?
    • #info === Ticket #70: "FOSS Student Pack" ===
      • #link https://pagure.io/fedora-commops/issue/70
      • #info Another older ticket to circle back to for this release cycle and possibly the next. This could have two different audiences. Do we want a student pack for new contributors to Fedora with resources for getting them started? Do we want to feature cool Fedora apps or general infrastructure a student could use for any open source project? What are the goals of a student pack and what do we want to get out of it? What should the student get out of it?



  • #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-02-21&oldid=486671"