From Fedora Project Wiki

(Create future meeting agenda template)
 
(Add minutes and logs)
 
(2 intermediate revisions by the same user not shown)
Line 27: Line 27:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === In the news: "Fedora Linux Distro to No Longer Offer Alpha Builds Starting with Fedora 27" ===
*** #link  
*** #link http://news.softpedia.com/news/fedora-linux-distro-to-no-longer-offer-alpha-builds-starting-with-fedora-27-513252.shtml
*** #info  
*** #info While it's not true that this is finalized, there is a current change proposal to drop Alpha releases from the release cycles of Fedora starting in Fedora 27. You can read more information at the Change wiki page.
** #info === "" ===
**** #link https://fedoraproject.org/wiki/Changes/NoMoreAlpha
*** #link  
** #info === In the news: "Fedora 26 Linux Has Been Delayed by a Week, Should Now Land on June 13, 2017" ===
*** #info
*** #link http://linux.softpedia.com/blog/fedora-26-linux-has-been-delayed-by-a-week-should-now-land-on-june-13-2017-513250.shtml
** #info === "" ===
*** #info Normal coverage about the week delay from no/no-go discussions. Article doesn't take strong stance. New release date on 2017-06-13.
*** #link  
*** #info  




* '''#topic Action items from last meetings'''
* '''#topic Action items from last meetings'''
** #link  
** #link https://meetbot.fedoraproject.org/teams/marketing/marketing.2017-02-21-13.59.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 Start mailing list thread about using a git forge for maintaining and creating a press kit for our release cycle activities ===
** #info ===  ===
*** #link https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/LWFDXEVAM6F4PUJNRIA3263ICAOF35KG/
** #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 #xx:"" ===
** #info === Ticket #242: "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 Left off with discussion about git forge and what should be included in the press kit. Can make a quick decision on where we want to host this, then focus more on the content that we wanted to put in there and how we want to start building it.
** #info === Ticket #xx: "" ===
*** #link https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/LWFDXEVAM6F4PUJNRIA3263ICAOF35KG/
*** #link https://pagure.io/fedora-marketing/issue/xxx
** #info === Ticket #245: "Create Fedora 26 talking points" ===
*** #info ticket update here
*** #link https://pagure.io/fedora-marketing/issue/245
*** #info Talking points officially start today, now that the change window is closed for Fedora 26. We're still awaiting feedback from the Council, but we try starting with the raw data that is on the existing talking points page and try to organize that in a way that we can work with? We can also try to task outreach to different WGs / SIGs, but this depends on if we want to collect information by technical grouping or by audience.




* '''#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)  
** #info (1) Change Checkpoint: Completion deadline (Tue 2017-02-28)
** #info (2)  
** #info (2) Create Talking Points (start: Tue 2017-02-28)
** #info (3)  
** #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'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-14.00.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-14.00.log.html
|next-meeting=2017-03-07
|next-meeting=2017-03-07
}}
}}

Latest revision as of 15:10, 28 February 2017

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2017-02-28

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-28)
  • #meetingname marketing
  • #chair < based on attendance >



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





  • #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

Retrieved from "https://fedoraproject.org/w/index.php?title=Meeting:Marketing_meeting_2017-02-28&oldid=487088"