From Fedora Project Wiki

(Get an initial version of this up, still working)
 
(Add minutes and logs)
 
(One intermediate revision by the same user not shown)
Line 13: Line 13:
** #info Name; Timezone; Other sub-projects / interest areas
** #info Name; Timezone; Other sub-projects / interest areas
* '''#topic Announcements'''
* '''#topic Announcements'''
** #info === "Outreachy 2016 remote internships and Fedora" ===
** #info === "Find Fedora at BrickHack 2016" ===
*** #link https://communityblog.fedoraproject.org/outreachy-2016-remote-internships-and-fedora/
*** #link https://communityblog.fedoraproject.org/find-fedora-at-brickhack-2016/
*** #info Fedora was accepted as a participating organization in the GNOME Outreachy program. This is an excellent opportunity for women to get a paid internship working in open source and on Fedora.
*** #info Fedora recently participated as an event sponsor at a hackathon event at the Rochester Institute of Technology. You can read a basic overview of the event there. An event report will be published soon (which will contain information important for Marketing to consider).
** #info === "PCWorld interviews FPL Matthew Miller for Fedora 2016 plans" ===
** #info === "FOSDEM 2016: Event Report" ===
*** #link https://communityblog.fedoraproject.org/pcworld-interviews-fpl-matthew-miller-for-fedora-2016-plans/
*** #link https://communityblog.fedoraproject.org/fosdem-2016-event-report/
*** #info PCWorld interviewed mattdm about the future plans for Fedora in 2016. This article has gotten a fair amount of exposure across the web and there is a lot of feedback coming from the post. There's a lot of questions concerning the discussion over packaging proprietary drivers. This could possibly use some attention by Marketing in a formal Magazine article?
*** #info A brief event report by decause about FOSDEM 2016 and Fedora's participation in the Distro DevRoom.
** #info === Google Summer of Code ===
** #info === "Modularity Use Case: Application Independence"
*** #info Fedora was accepted as a mentoring organization in GSoC again this year. A new article will be posted on the Community Blog soon, and an article on the Magazine would be a good companion to this article.
*** #link https://communityblog.fedoraproject.org/modularity-use-case-application-independence/
*** #action jflory7 Write the pointer article about GSoC on the Magazine once the CommBlog article is drafted
*** #info A look at the Modularization objective set by the Fedora Council. langdon writes about why modularization is important and how it helps Fedora.
 
*** #link https://fedoraproject.org/wiki/Modularization
 
* '''#topic Action items from last meetings'''
* '''#topic Action items from last meetings'''
** #link https://meetbot.fedoraproject.org/teams/marketing/marketing.2016-02-24-22.07.html
** #link https://meetbot.fedoraproject.org/teams/marketing/marketing.2016-02-17-21.56.html
** #info === mailga raise marketing meeting attendance with FAmSCo ===
** #info [INCOMPLETE] === jflory7 Write the pointer article about GSoC on the Magazine once the CommBlog article is drafted ===
*** mailga: Was this completed? Any FAmSCo members here in the meeting now?
*** #help Write an article about the Google Summer of Code announcement and Fedora's participation on the Community Blog
** #info [INCOMPLETE] === linuxmodder raise marketing meeting attendance with FAMNA ===
** #info [INCOMPLETE] === jflory7 / linuxmodder Bring up Marketing meeting times with FAmNA on Thursday evening meeting ===
*** #action jflory7 / linuxmodder Bring up Marketing meeting times with FAmNA on Thursday evening meeting
*** #info jflory7 was absent at the last FAmNA meeting and didn't have a chance to bring it up
** #info === jzb move discussion on FAS membership to list ===
*** #action jflory7 Bring up Marketing meeting date and time with FAmNA on Thursday
*** #action jzb Start discussion about FAS membership on the Marketing list
** #info [COMPLETE] === jflory7 Follow up with nirik or puiterwijk about updating the Magazine "head" and close the ticket once completed ===
** #info [COMPLETE] === jflory7 Create a ticket for Fedora Server talking points and CC linuxmodder on it ===
** #info [COMPLETE] === nb will coordinate with decause about removing inactive people from Marketing FAS group ===
*** #link https://fedorahosted.org/marketing-team/ticket/220
** #info === jzb Update the Marketing Join page to incorporate the new guidelines proposed on the mailing list ===
** #info [INCOMPLETE] === jflory7 / linuxmodder Take on responsibility for the Workstation ticket and begin collecting info for talking points ===
** #info [COMPLETE] === jflory7 Update Ticket #218 with new information and owners ===
*** jflory7 is short for cycles this week until after BrickHack this weekend – would be helpful if someone else could help linuxmodder with this
** #info === decause ping serverWG ML for status update ===
** #info [COMPLETE] === decause/jflory7 add to commops meeting agenda in wikigardening section https://fedoraproject.org/wiki/Fedora_24_talking_points ===
*** #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/JMWDQHLHLAQZTTQHDH6ZHBNVGPKCPQRD/
*** #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-03-08
*** Looks like it made it to the CommOps list but not the Server list? Is it stuck in a queue?
** #info [INCOMPLETE] === jflory7 Get F24 talking points page up to date and update Marketing page ===
** #info === decause work with fale to get server WG talking points from ML ===
** #info [COMPLETE] === jflory7 File a ticket to discuss adding a [Marketing] prefix to the mailing list ===
** #info [COMPLETE] === jflory7 Contact Fedora Infra about adding the prefix or file a ticket in Infra Trac if necessary ===
*** #link https://fedorahosted.org/marketing-team/ticket/221
** #info === fale will draft the procedure for the official recognition of entities using Fedora ===
** #info [COMPLETE] === jflory7 Create a ticket about publicizing Fedora affiliates / similar kind of topic ===
** #info === decause ping the EDU list with the wiki page fale is working on after it has been created ===
*** #link https://fedorahosted.org/marketing-team/ticket/222
 
 
* '''#topic Tickets'''
* '''#topic Tickets'''
** #link https://fedorahosted.org/marketing-team/report/12
** #link https://fedorahosted.org/marketing-team/report/12
** #info === Ticket #160 ===
** #info === Ticket #219 ===
*** #link https://fedorahosted.org/marketing-team/ticket/160
*** #link https://fedorahosted.org/marketing-team/ticket/219
*** #info * "Fedora magazine "head" for planet"
*** #info * "Create Python talking points for Ambassadors"
*** Simple fix, just need to ping nirik or puiterwijk about this and close this loop
** #info === Ticket #222 ===
*** #action jflory7 Follow up with nirik or puiterwijk about doing this and close the ticket once completed
*** #link https://fedorahosted.org/marketing-team/ticket/222
** #info === Ticket #214 ===
*** #info * "Publicizing "Fedora affiliates" (or groups using Fedora)"
*** #link https://fedorahosted.org/marketing-team/ticket/214
*** fale: Any progress on creating an initial draft of a process?
*** #info * "Clean up Marketing FAS group membership"
*** Recommendation: Since Marketing is small, just do this manually and close the ticket? Who wants to take on that task?
** #info === Ticket #215 ===
** #info === Ticket #215 ===
*** #link https://fedorahosted.org/marketing-team/ticket/215
*** #link https://fedorahosted.org/marketing-team/ticket/215
*** #info * "Looking at our Join process"
*** #info * "Looking at our Join process"
*** jzb: Any progress on the draft of what defines an active Marketing member?
*** jzb: Any progress on updating the wiki page?
** #info === Ticket #217 ===
** #info === Ticket #217 ===
*** #link https://fedorahosted.org/marketing-team/ticket/217
*** #link https://fedorahosted.org/marketing-team/ticket/217
*** #info * "Talking points: Fedora Cloud"
*** #info * "Talking points: Fedora Cloud"
*** jzb: Ticket was due on March 8th. Were talking points completed or are there more steps to complete? If so, what steps?
** #info === Ticket #220 ===
*** #link https://fedorahosted.org/marketing-team/ticket/220
*** #info * "Talking points: Fedora Server"
*** fale, decause, simo: Ticket was due on March 8th. Were talking points completed or are there more steps to complete? If so, what steps?
** #info === Ticket #218 ===
** #info === Ticket #218 ===
*** #link https://fedorahosted.org/marketing-team/ticket/218
*** #link https://fedorahosted.org/marketing-team/ticket/218
*** #info * "Talking points: Fedora Workstation"
*** #info * "Talking points: Fedora Workstation"
** #info === Ticket #220 ===
*** sesivany, ardian: Ticket was due on March 8th. Were talking points completed or are there more steps to complete? If so, what steps?
*** #link https://fedorahosted.org/marketing-team/ticket/220
*** #info * "Talking points: Fedora Server"
*** Ticket needs an owner
** #info === Ticket #221 ===
*** #link https://fedorahosted.org/marketing-team/ticket/221
*** #info * "Add a [Marketing] prefix to mail on our list"
*** This is a simple vote: +1 / -1?
** #info === Ticket #222 ===
*** #link https://fedorahosted.org/marketing-team/ticket/222
*** #info * "Publicizing "Fedora affiliates" (or groups using Fedora)"
*** Part of the discussion we began last week looking at publicizing entities already using Fedora
* '''#topic Long-Term Plans: Magazine'''
** Discussion: Are there any long-term objectives we want to set in place for the Magazine? Are there ways we can grow readership further? Do we believe we are taking advantage of our resources with the Magazine? What can be improved?  
 
 
* '''#topic Open Floor'''
* '''#topic Open Floor'''
|summary=
|summary=https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-09/marketing.2016-03-09-21.55.html
|log=
|log=https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-09/marketing.2016-03-09-21.55.log.html
|next-meeting=2016-03-16
|next-meeting=2016-03-16
}}
}}

Latest revision as of 19:40, 16 March 2016

FedoraMarketing.png

Fedora Marketing Team Meeting Minutes 2016-03-09

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 (2016-03-09)
  • #meetingname marketing
  • #chair < based on attendance >
  • #topic Roll Call
    • #info Name; Timezone; Other sub-projects / interest areas
  • #topic Announcements
  • #topic Action items from last meetings
    • #link https://meetbot.fedoraproject.org/teams/marketing/marketing.2016-02-17-21.56.html
    • #info [INCOMPLETE] === jflory7 Write the pointer article about GSoC on the Magazine once the CommBlog article is drafted ===
      • #help Write an article about the Google Summer of Code announcement and Fedora's participation on the Community Blog
    • #info [INCOMPLETE] === jflory7 / linuxmodder Bring up Marketing meeting times with FAmNA on Thursday evening meeting ===
      • #info jflory7 was absent at the last FAmNA meeting and didn't have a chance to bring it up
      • #action jflory7 Bring up Marketing meeting date and time with FAmNA on Thursday
    • #info [COMPLETE] === jflory7 Follow up with nirik or puiterwijk about updating the Magazine "head" and close the ticket once completed ===
    • #info [COMPLETE] === nb will coordinate with decause about removing inactive people from Marketing FAS group ===
    • #info === jzb Update the Marketing Join page to incorporate the new guidelines proposed on the mailing list ===
    • #info [COMPLETE] === jflory7 Update Ticket #218 with new information and owners ===
    • #info === decause ping serverWG ML for status update ===
    • #info === decause work with fale to get server WG talking points from ML ===
    • #info [COMPLETE] === jflory7 Contact Fedora Infra about adding the prefix or file a ticket in Infra Trac if necessary ===
    • #info === fale will draft the procedure for the official recognition of entities using Fedora ===
    • #info === decause ping the EDU list with the wiki page fale is working on after it has been created ===
  • #topic Tickets
  • #topic Open Floor

Meeting summary and action items

Full meeting log

Next Meeting