From Fedora Project Wiki

(Create initial template)
 
(Finish agenda)
Line 27: Line 27:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === In the news: "Fedora 26 Linux to Ship with GNOME 3.24 Desktop, Support Creation of LVM RAID" ===
*** #link  
*** #link http://news.softpedia.com/news/fedora-26-linux-to-ship-with-gnome-3-24-desktop-support-creation-of-lvm-raid-512454.shtml
*** #info  
*** #info Overall positive write-up about some of the upcoming features for Fedora 26. We should work on creating talking points soon now that the change window is passing.
** #info === "" ===
** #info === "Find Fedora at FOSDEM 2017!" ===
*** #link  
*** #link https://fedoramagazine.org/find-fedora-at-fosdem-2017/
*** #info  
*** #info Fedora was at FOSDEM in Brussels this past weekend. A good number of Fedora contributors participated as speakers during the conference.
** #info === "" ===
** #info === "Fedora Cloud Base Image has a new home!" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedora-cloud-base-new-home/
*** #info  
*** #info Fedora Cloud images moved to a new home, since Cloud is no longer a main edition of Fedora. This could be a useful point to communicate during the next release as Atomic begins to take a more prominent role.




* '''#topic Action items from last meetings'''
* '''#topic Action items from last meetings'''
** #link  
** #link https://meetbot.fedoraproject.org/teams/marketing/marketing.2017-01-10-14.14.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 No past action items!
** #info ===  ===
** #info ===  ===




* '''#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 #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 The idea behind this ticket is to reevaluate what the Marketing team does or should be doing during a release, and then more clearly communicating that in a public place, like our main wiki page. The issue we have is that we haven't discussed or brainstormed this much yet.
** #info === Ticket #xxx ===
** #info === Ticket #245 ===
*** #info ""
*** #info "Create Fedora 26 talking points"
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #link https://pagure.io/fedora-marketing/issue/245
*** #info ticket update here
*** #info As per usual, we want to begin working on the Fedora 26 talking points to share with Ambassadors, the press, and others who will spread the word about what's new and great in the next release of Fedora.




* '''#topic Upcoming Tasks'''
* '''#topic Upcoming Tasks'''
** #link https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
** #link https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
** #info (1) Monitor news sites to provide corrections & info (due: Mon 2016-12-05)
** #info (1) Change Checkpoint: Completion deadline (Tue 2017-02-28)
** #info (2) Marketing Retrospective (due: Tue 2016-12-06)
** #info (2) Create Talking Points (start: Tue 2017-02-28)
** #info (3) Proposed Changes Profiles (start: Tue 2017-03-07)
** #info (4) Email WGs to solicit bullet points for Alpha release announcement (start: Thu 2017-03-09)





Revision as of 14:09, 7 February 2017

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2017-02-07

Meeting Time

Participants

This week's Marketing 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
Attendees, update this agenda with your latest items before the meeting has started.
  • #startmeeting Fedora Marketing meeting (2017-02-07)
  • #meetingname marketing
  • #chair < based on attendance >



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



  • #topic Action items from last meetings


  • #topic Tickets
    • #link https://pagure.io/fedora-marketing/issues?tags=meeting
    • #info === Ticket #242 ===
      • #info "Update release activity steps / process on the wiki"
      • #link https://pagure.io/fedora-marketing/issue/242
      • #info The idea behind this ticket is to reevaluate what the Marketing team does or should be doing during a release, and then more clearly communicating that in a public place, like our main wiki page. The issue we have is that we haven't discussed or brainstormed this much yet.
    • #info === Ticket #245 ===
      • #info "Create Fedora 26 talking points"
      • #link https://pagure.io/fedora-marketing/issue/245
      • #info As per usual, we want to begin working on the Fedora 26 talking points to share with Ambassadors, the press, and others who will spread the word about what's new and great in the next release of Fedora.


  • #topic Upcoming Tasks
    • #link https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
    • #info (1) Change Checkpoint: Completion deadline (Tue 2017-02-28)
    • #info (2) Create Talking Points (start: Tue 2017-02-28)
    • #info (3) Proposed Changes Profiles (start: Tue 2017-03-07)
    • #info (4) Email WGs to solicit bullet points for Alpha release announcement (start: Thu 2017-03-09)


  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting