From Fedora Project Wiki

(Add meeting template for future meeting)
 
(Prepare today's agenda)
Line 19: Line 19:
** #info (3) Action items from last meeting
** #info (3) Action items from last meeting
** #info (4) Tickets
** #info (4) Tickets
** #info (5) Community Blog - skipping today, but will be back next week!
** #info (5) Community Blog
** #info (5) Open Floor
** #info (6) Open Floor




Line 30: Line 30:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Community Promotion Ads - 2017" ===
*** #link  
*** #link http://meta.unix.stackexchange.com/questions/4337/community-promotion-ads-2017
*** #info
*** #info mattdm submitted a series of community ads to the Unix StackExchange site, featuring the Fedora Magazine and each Fedora edition. To be featured on the site, ads need to have six or more votes. If you have a StackExchange / StackOverflow account, please log in and add your vote!
** #info === "Ambassadors LATAM: Year in Review" ===
*** #link https://communityblog.fedoraproject.org/ambassadors-latam-year-in-review/
*** #info williamjmorenor writes up a summary of the past year for the Ambassadors of LATAM. Read more in his write-up on the Community Blog.
** #info === Exciting times in Marketing land ===
*** #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.2017-02-14-13.58.html
*** #info The Marketing meetings are starting to become fast-paced and interest, with talks of building new marketing campaigns for education-related audiences and building press kits targeted towards different user types of Fedora. If you're interested in this, check out the minutes for more information!




* '''#topic Action items from last meeting'''
* '''#topic Action items from last meeting'''
** #link  
** #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-02-07-17.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 === ===
** #info === [COMPLETE] jflory7 File feature tickets in Election app for (1) nomination of candidates, and (2) questionnaire question interaction (e.g. submitting new questions) ===
** #info === ===
*** #link https://pagure.io/elections/issue/47
*** #action Rhea - Post on Reddit with the Election results.
*** #link https://pagure.io/elections/issue/48
*** #link https://pagure.io/elections/issue/49
** #info === [COMPLETE] jflory7 Summarize this discussion into the ticket, try to get opinion of jkurik (and also bee2502 for metrics) in the ticket ===
*** #link https://pagure.io/fedora-commops/issue/103#comment-75589




* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #link https://pagure.io/fedora-commops/issues?tags=meeting
** #info === Ticket #98 "Round Up of Fedora Contributor Talks @ FOSDEM" ===
** Open ticket triage?
*** #link https://pagure.io/fedora-commops/issue/98
** #info === Ticket #90 "Improving Fedora Elections Process" ===
*** #link https://pagure.io/fedora-commops/issue/90
** #info === Ticket #93 "Elections: Better explain roles of Council and FESCo" ===
*** #link https://pagure.io/fedora-commops/issue/93


* '''#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) "Ambassadors LATAM: Year in Review" - williamjmorenor++
**** #link https://communityblog.fedoraproject.org/ambassadors-latam-year-in-review/
**** #info Total Views (Feb. 7 - Feb. 14): 56
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3344
*** #info (2) "Earn Fedora Badges designing Badges!" - riecatnor++
**** #link https://communityblog.fedoraproject.org/earn-badges-designing-badges/
**** #info Total Views (Feb. 9 - Feb. 14): 249
**** #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3352
** #info === Coming Up in CommBlog ===
*** #info (1) "" -
**** #link
*** #info (2) "" -
**** #link




Revision as of 17:31, 14 February 2017

CommOps wiki banner.png

Fedora CommOps Team Meeting Minutes 2017-02-14

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-14)
  • #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 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-14&oldid=486163"