From Fedora Project Wiki

(Prepare future meeting agenda)
 
(Create meeting agenda)
Line 27: Line 27:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info No new weekly news coverage on jflory7's radar…
*** #link
** #info === "fedorahosted.org retired today (2017-03-01)" ===
*** #info
*** #link https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/RYZMAUPTT7J2ETLN34CHLBEEDV5WAQEW/
** #info === "" ===
*** #info FedoraHosted.org was officially retired last week. All projects are either defunct or have migrated to Pagure (or elsewhere).
*** #link
*** #info
** #info === "" ===
*** #link  
*** #info  




* '''#topic Action items from last meetings'''
* '''#topic Action items from last meetings'''
** #link  
** #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-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 === FranciscoD / bkp Discuss and draft a short proposal of what one-page release announcements looks like for the press kit, with (1) timeline for when they should be created during the release, (2) type of content to include in the announcement, and (3) how it should be delivered ===
** #info === ===
** #info === [COMPLETE] jwf Draft a simple proposal for what background modules / past press coverage should be in the press kit, add comment to ticket #242 for discussion at next meeting ===
** #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:"" ===
*** #link https://pagure.io/fedora-marketing/issue/242
*** #info
** #info === Ticket #245: "" ===
*** #link https://pagure.io/fedora-marketing/issue/245
*** #info
** #info === Ticket #248: "" ===
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #info ticket update here
*** #info  
** #info === Ticket #xx: "" ===
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #info ticket update here




* '''#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'''
** jflory7 unable to chair next week – is anyone able to chair for 2017-03-14?
|summary=
|summary=
|log=
|log=
|next-meeting=2017-03-14
|next-meeting=2017-03-14
}}
}}

Revision as of 13:42, 7 March 2017

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2017-03-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-03-07)
  • #meetingname marketing
  • #chair < based on attendance >



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



  • #topic Action items from last meetings
    • #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-28/marketing.2017-02-28-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 === FranciscoD / bkp Discuss and draft a short proposal of what one-page release announcements looks like for the press kit, with (1) timeline for when they should be created during the release, (2) type of content to include in the announcement, and (3) how it should be delivered ===
    • #info === [COMPLETE] jwf Draft a simple proposal for what background modules / past press coverage should be in the press kit, add comment to ticket #242 for discussion at next meeting ===



  • #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
    • jflory7 unable to chair next week – is anyone able to chair for 2017-03-14?

Meeting summary and action items

Full meeting log

Next Meeting