From Fedora Project Wiki

(Prepare future meeting agenda)
 
No edit summary
Line 21: Line 21:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === "Fedora 25 makes Linux easy enough for anyone to try" ===
*** #link  
*** #link http://www.pcworld.com/article/3144644/linux/fedora-25-makes-linux-easy-enough-for-anyone-to-try.html
*** #info  
*** #info One of several positive reviews.
** #info === "" ===
** #info === "Fedora Receives Its Own Electrum Bitcoin Wallet Client" ===
*** #link  
*** #link http://www.newsbtc.com/2016/12/04/fedora-gets-electrum-bitcoin-wallet-client/
*** #info  
*** #info This is a feature about which a lot of outlets got excited
** #info === "" ===
** #info === "Fedora 25 and the Internet time scale" ===
*** #link  
*** #link http://windowsitpro.com/security/fedora-25-and-internet-time-scale
*** #info  
*** #info NTP is also getting a lot of attention these days


* '''#topic F25 Marketing Retrospective'''
** #info === "What did we do right?" ===
** #info === "What can we do better?" ===
** #info === "Where did we have gaps?" ===
** #info === "How can we bridge those gaps?" ===
** #info === "What ideas or wishlist do we have for F26?" ===


* '''#topic Action items from last meetings'''
* '''#topic Action items from last meetings'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/marketing.2016-11-29-14.00.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 === jflory7 was given positive feedback on the freenode/Fedora article, with the suggestion to add F25 features. ===
** #info === ===
** #info === jflory7 maybe a more detailed explanation of useful commands and some rules on how to follow meetings. But I do see that a freenode-fedora howto should be more complex. ===
** #info === ===
** #info === COMPLETE bkp to raise ticket #241 on the #fedora-magazine channel this week ===
** #info === x3mboy to poll lost to see about altering release activities page to a more action-oriented table like the one at https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Project_tasks, or some variant in-between ===
** #info === Check into existence of SurveyMonkey/LimeSurvey/similar account in Fedora-land ===




* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://pagure.io/fedora-marketing/issues?tags=meeting
** #link https://pagure.io/fedora-marketing/issues?tags=meeting
** #info === Ticket #xxx ===
** #info === Ticket #241 ===
*** #info ""
*** #info "Fedora Magazine feed fails to validate"
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #link https://pagure.io/fedora-marketing/issue/241
*** #info ticket update here
*** #info From ryanlerch: The issue with the feed here is that that url has the & in it, but not in a cdata block, or using an xml entity (&). Unsure how to fix.
** #info === Ticket #xxx ===
** #info === Ticket #242 ===
*** #info ""
*** #info "Update release activity steps / process on the wiki"
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #link https://pagure.io/fedora-marketing/issue/242
*** #info ticket update here
*** #info x3mboy to poll lost to see about altering release activities page to a more action-oriented table like the one at https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Project_tasks, or some variant in-between




Line 57: Line 65:
** #info (1) Monitor news sites to provide corrections & info (due: Mon 2016-12-05)
** #info (1) Monitor news sites to provide corrections & info (due: Mon 2016-12-05)
** #info (2) Marketing Retrospective (due: Tue 2016-12-06)
** #info (2) Marketing Retrospective (due: Tue 2016-12-06)
** #info (3) Cleanup Marketing wiki from previous releases (due: Tue 2016-12-20)
** #info (4) Cycle Marketing wiki pages for current release (due: Tue 2016-12-20)
** #info (5) Change Checkpoint: Completion deadline (testable) (due: Tue 2017-02-21)





Revision as of 12:22, 6 December 2016

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2016-12-06

Meeting Time

Participants

This week's Marketing Meeting will be led by bproffit.

  • 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
Attendees, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora Marketing meeting (2016-12-06)
  • #meetingname marketing
  • #chair < based on attendance >



  • #topic Roll Call
    • #info Name; Timezone; Other sub-projects / interest areas


  • #topic F25 Marketing Retrospective
    • #info === "What did we do right?" ===
    • #info === "What can we do better?" ===
    • #info === "Where did we have gaps?" ===
    • #info === "How can we bridge those gaps?" ===
    • #info === "What ideas or wishlist do we have for F26?" ===
  • #topic Action items from last meetings
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2016-11-29/marketing.2016-11-29-14.00.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 === jflory7 was given positive feedback on the freenode/Fedora article, with the suggestion to add F25 features. ===
    • #info === jflory7 maybe a more detailed explanation of useful commands and some rules on how to follow meetings. But I do see that a freenode-fedora howto should be more complex. ===
    • #info === COMPLETE bkp to raise ticket #241 on the #fedora-magazine channel this week ===
    • #info === x3mboy to poll lost to see about altering release activities page to a more action-oriented table like the one at https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Project_tasks, or some variant in-between ===
    • #info === Check into existence of SurveyMonkey/LimeSurvey/similar account in Fedora-land ===




  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting