From Fedora Project Wiki

(Prepare future meeting template)
 
(Prepare today's meeting agenda)
Line 27: Line 27:


* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "" ===
** #info === IMPORTANT: "Fedora Council FAD Report – 2017/2018 Initial Steps" ===
*** #link  
*** #link https://communityblog.fedoraproject.org/fedora-council-fad-2017-report/
*** #info  
*** #info The Fedora Council held their FAD from 26-28 March. During the FAD, they tackled some key areas of interest across the project. This is one part of a series of posts (to come). Important information for any contributor to review.
** #info === "" ===
** #info === In the news: "Fedora 26 Alpha Released With New Features — Download ISO File Here" ===
*** #link  
*** #link https://fossbytes.com/fedora-26-alpha-released-new-features-download/
*** #info  
*** #info A generic article supporting the Fedora 26 Alpha release. Nothing too unique, mostly positive, advises caution to using it on stable machinery. Worth noting is that they source their changes from the 26 ChangeSet wiki page.
** #info === "" ===
** #info === In the news: "Red Hat and Fedora Teams Welcome Ubuntu to GNOME and Wayland with Open Arms" ===
*** #link  
*** #link http://news.softpedia.com/news/red-hat-and-fedora-teams-welcome-ubuntu-to-gnome-and-wayland-with-open-arms-514661.shtml
*** #info  
*** #info Softpedia covered GNOME developer Christian Schaller's blog post welcoming Ubuntu / Canonical to the GNOME community on behalf of the Fedora Workstation team. The response was overwhelmingly positive! Which brings to the next point…
** #info === Record setting: Facebook, collaboration on GNOME ===
*** #link https://www.facebook.com/TheFedoraProject/posts/10155140243620480
*** #info Our Facebook post resharing the article was one of our most widely responded to post on Facebook… ever! As of now, 69,018 people reached, 1.4k likes, and 257 shares! People are in love with the idea of upstream collaboration (it seems)!




Line 41: Line 44:
** #link  
** #link  
** #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 === [DROPPED] jwf to solicit the WGs left to edit the Talking Point page, even splitting the TP in two parts (one of them is for the long-term vision of audience-based TPs) ===
** #info === ===
*** #info Most feedback is there, following up with remaining groups
** #info === ===
** #info === x3mboy Follow up with the KDE and LXQt SIGs to add their information to the wiki page before the beta release ===
** #info === [INCOMPLETE] jwf Reach out to the Server WG / Spins mailing list to ask for talking point additions to the wiki page before beta release ===
*** #action jwf Reach out to the Server WG / Spins mailing list to ask for talking point additions to the wiki page before beta release




* '''#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 #249: "Create Fedora 26 talking points" ===
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #link https://pagure.io/fedora-marketing/issue/249
*** #info ticket update here
*** Brief, quick check-in. Where are we, who's left, do we need to follow up at meetings or on mailing lists? IRC channels?
** #info === Ticket #xx: "" ===
** #info === Ticket #246: "Prepare report for Council sub-project report" ===
*** #link https://pagure.io/fedora-marketing/issue/xxx
*** #link https://pagure.io/fedora-marketing/issue/246
*** #info ticket update here
*** What do we want to build the base of "State of Marketing" as?




* '''#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) Review Firefox Bookmarks For Update (due: Tue 2017-04-11)
** #info (2)  
** #info (2) Update and Package Firefox Bookmarks (due: Thu 2017-04-13
** #info (3)  
** #info (3) Tag Updated Bookmarks Package for Fedora 26 (due: Thu 2017-04-13)
** #info (4) Beta Freeze (Tue 2017-05-16, 00:00 UTC)





Revision as of 12:54, 11 April 2017

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2017-04-11

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



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


  • #topic Announcements
    • #info === IMPORTANT: "Fedora Council FAD Report – 2017/2018 Initial Steps" ===
    • #info === In the news: "Fedora 26 Alpha Released With New Features — Download ISO File Here" ===
    • #info === In the news: "Red Hat and Fedora Teams Welcome Ubuntu to GNOME and Wayland with Open Arms" ===
    • #info === Record setting: Facebook, collaboration on GNOME ===


  • #topic Action items from last meetings
    • #link
    • #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 === [DROPPED] jwf to solicit the WGs left to edit the Talking Point page, even splitting the TP in two parts (one of them is for the long-term vision of audience-based TPs) ===
      • #info Most feedback is there, following up with remaining groups
    • #info === x3mboy Follow up with the KDE and LXQt SIGs to add their information to the wiki page before the beta release ===
    • #info === [INCOMPLETE] jwf Reach out to the Server WG / Spins mailing list to ask for talking point additions to the wiki page before beta release ===
      • #action jwf Reach out to the Server WG / Spins mailing list to ask for talking point additions to the wiki page before beta release



  • #topic Upcoming Tasks


  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting