From Fedora Project Wiki

(Finish meeting agenda! An entire hour before! Whoooo!)
(Add minutes and logs)
 
Line 70: Line 70:


* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/marketing.2017-02-21-13.59.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/marketing.2017-02-21-13.59.log.html
|next-meeting=2017-02-28
|next-meeting=2017-02-28
}}
}}

Latest revision as of 15:02, 21 February 2017

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2017-02-21

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-21)
  • #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-14/marketing.2017-02-14-13.58.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 === [COMPLETE] jwf / x3mboy Discuss possibility of using a bot to sync social media platform (e.g. FB / Twitter / RSS) to Fedora Projects News Telegram group ===
      • #info Bot was set up this morning in the Project News channel to sync with Facebook – all Facebook posts should show up in the Telegram channel within an hour of being posted
      • x3mboy++
    • #info === [COMPLETE] jwf File new ticket for education-focused marketing campaign, with end goal being to share with Fedora Council at March 22nd sub-project report meeting ===
    • #info === bkp (1) Research what our old press kits were, (2) leave comment in ticket #242 with that info, (3) all marketing team members encouraged to discuss / give feedback for modernizing press kits ===
    • #info === [COMPLETE] x3mboy Leave comment in ticket #245 for initial list of "target audiences" based on Fedora Labs, cross-compared with package categories, to be discussed at the next meeting ===


  • #topic Tickets
    • #link https://pagure.io/fedora-marketing/issues?tags=meeting
    • #info === Ticket #242: "Update release activity steps / process on the wiki" ===
    • #info === Ticket #245: "Create Fedora 26 talking points" ===
      • #link https://pagure.io/fedora-marketing/issue/245
      • #info Eduard put a full list of our Labs, Spins, and DNF repository groups. He also proposed a small list of target audiences we could start with, and try to filter down for how we want to approach this release's talking points.
    • #info === Ticket #248: " Create an education-focused marketing campaign" ===
      • #link https://pagure.io/fedora-marketing/issue/248
      • #info This was the biggest discussion last meeting, but to move forward on this, we should probably establish a rough idea of milestones to help lead us towards establishing and creating this campaign. We should have one or two initial planning milestones before the Council sub-project report, which we are tentatively slated for on March 22.


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