Fedora Marketing Team Meeting Minutes 2017-04-25

Meeting Time

This week's Marketing Meeting will be led by jflory7.

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.

Attendees, update this agenda with your latest items before the meeting has started.

#topic Agenda
- #link https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-04-25
- #info (1) Roll call
- #info (2) Announcements
- #info (3) Action items from last meeting
- #info (4) Tickets
- #info (5) Upcoming tasks
- #info (6) Open floor

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

#topic Announcements
- #info === In the news: "Docker's Moby cast in same mold as Fedora's Red Hat" ===
  - #link http://www.infoworld.com/article/3191591/open-source-tools/dockers-moby-cast-in-same-mold-as-fedoras-red-hat.html
  - #info Not really focusing on Fedora, but covering the new emergence of Docker's Moby Project and how its role for a commercial product is similar to Fedora's own structure. Nothing critical for us, but an interesting view on what Fedora and Red Hat's relationship is by an outside viewer.
- #info === "Help translate the Fedora User Handbook" ===
  - #link https://communityblog.fedoraproject.org/translate-fedora-user-handbook/
  - #help Native English speakers are needed to help bring the Fedora user handbook to English. Check out this CommBlog post to see how you can help.
- #info === "Share Fedora: Difficult Conversations" ===
  - #link https://fedoramagazine.org/share-fedora-difficult-conversations/
  - #info The Opensource.com blogging challenge continues this week, asking for people like you to share your experience about open source communities. This week's topic are difficult conversations. Check it out on the Fedora Magazine.

#topic Action items from last meetings
- #link https://meetbot.fedoraproject.org/teams/marketing/marketing.2017-04-18-13.03.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 === x3mboy Reach out to the Design Team (IRC, mailing list, meeting, etc.) to solicit points for the Design Suite talking points ===
- #info === jwf Reach out to the Server WG / Spins mailing list to ask for talking point additions to the wiki page before beta release ===
- #info === x3mboy will finish work with atomic team, that is being work in atomic's Pagure ===

#topic Tickets
- #link https://pagure.io/fedora-marketing/issues?tags=meeting
- #info === Ticket #251:"Extend meeting time" ===
  - #link https://pagure.io/fedora-marketing/issue/251
- #info === Ticket #246: "Prepare report for Council sub-project report" ===
  - #link https://pagure.io/fedora-marketing/issue/246
  - Try to find an owner for this topic?
- #info === Ticket #249: "Create Fedora 26 talking points" ===
  - #link https://pagure.io/fedora-marketing/issue/249
  - Try to find an owner for this topic?

#topic Upcoming Tasks
- #link https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
- #info (1) Beta Freeze (Tue 2017-05-16, 00:00 UTC)
- #info (2) Change Checkpoint: 100% Code Complete Deadline (Tue 2017-05-16)
- #info (3) Email WGs to solicit bullet points for Beta release announcement (due: Fri 2017-05-19)