13:59:03 <jwf> #startmeeting Fedora Marketing meeting (2017-02-21)
13:59:03 <zodbot> Meeting started Tue Feb 21 13:59:03 2017 UTC.  The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:59:03 <zodbot> The meeting name has been set to 'fedora_marketing_meeting_(2017-02-21)'
13:59:04 <jwf> #meetingname marketing
13:59:04 <zodbot> The meeting name has been set to 'marketing'
13:59:05 <jwf> #topic Agenda
13:59:11 <jwf> #link https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-02-21
13:59:16 <jwf> #info (1) Roll call
13:59:22 <jwf> #info (2) Announcements
13:59:27 <jwf> #info (3) Action items from last meeting
13:59:32 <jwf> #info (4) Tickets
13:59:33 <x3mboy> .hello x3mboy
13:59:34 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
13:59:37 <jwf> #info (5) Upcoming tasks
13:59:42 <jwf> #info (6) Open floor
13:59:47 <jwf> #topic Roll call
13:59:47 <bkp> .hello bkp
13:59:48 <zodbot> bkp: Sorry, but you don't exist
13:59:52 <jwf> #info Name; Timezone; Other sub-projects / interest areas
14:00:00 <bkp> .hello bproffitt
14:00:01 <zodbot> bkp: Sorry, but you don't exist
14:00:10 <bkp> .hello bproffit
14:00:11 <zodbot> bkp: bproffit 'Brian Proffitt' <bkp@redhat.com>
14:00:17 <jwf> #info Justin W. Flory; UTC+1; Marketing, Magazine, CommOps, Ambassador, Diversity Team, sysadmin-badges, etc.
14:00:23 <bkp> I do exist
14:00:34 <jwf> Heh. :) Maybe zodbot needs coffee…
14:00:37 <jwf> .moar coffee zodbot
14:00:37 <zodbot> here zodbot, have some more coffee
14:00:45 <jwf> #chair bkp x3mboy
14:00:45 <zodbot> Current chairs: bkp jwf x3mboy
14:00:56 <bkp> #info Brian Proffitt; UTC-5; marketing; social media
14:00:58 <x3mboy> #info Eduard Lucena; UTC-4; Marketing, Magazine, CommOps, Ambassador, Hubs, Join, etc
14:01:19 <bkp> jwf: Are you still in EU?
14:01:21 <jwf> We'll wait a couple more minutes for some more folks to roll in. Agenda is here: https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-02-21
14:01:33 <jwf> bkp: Yep! I'll be in Croatia until mid-May or so.
14:01:50 <jwf> I'm studying abroad for a semester.
14:02:13 <bexelbie> .hello bex
14:02:14 <zodbot> bexelbie: bex 'Brian (bex) Exelbierd' <bex@pobox.com>
14:02:25 <bkp> Cool. Going to drive over to Brno?
14:02:26 * jwf waves
14:02:30 <jwf> #chair bexelbie
14:02:30 <zodbot> Current chairs: bexelbie bkp jwf x3mboy
14:02:43 <jwf> bkp: If I can find an excuse to go again, I'll take it :)
14:04:57 <jwf> Alrighty, we can go ahead and press on.
14:05:09 <jwf> Anyone else can chime in when they arrive.
14:05:09 <jwf> #topic Announcements
14:05:15 <jwf> #info === In the news: "New Fedora 25 Live ISO Respins Now Available with Linux Kernel 4.9.8, Bug Fixes" ===
14:05:20 <jwf> #link http://news.softpedia.com/news/new-fedora-25-live-iso-respins-now-available-with-linux-kernel-4-9-8-bug-fixes-512945.shtml
14:05:25 <jwf> #info New live respins of all the Fedora 25 desktop environments and editions are now available. Softpedia covers where to find them and details a little about what they are and who they're for.
14:05:31 <jwf> #info === "North America and Fedora: Year in Review" ===
14:05:37 <jwf> #link https://communityblog.fedoraproject.org/north-america-fedora-year-review/
14:05:44 <jwf> #info A quick overview of the past year's events in North America by the Ambassadors.
14:05:47 <jwf> <eof>
14:05:53 <jwf> Anyone else have anything they'd like to share?
14:06:07 <bkp> Not I
14:06:52 <jwf> Announcements, going once…
14:07:02 <jwf> Going twice…
14:07:08 <jwf> Thrice…
14:07:13 <jwf> #topic Action items from last meetings
14:07:20 <jwf> #link https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.2017-02-14-13.58.html
14:07:26 <jwf> #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.
14:07:34 <jwf> #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 ===
14:07:46 <jwf> #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++ )
14:07:53 <jwf> #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 ===
14:07:57 <jwf> #link https://pagure.io/fedora-marketing/issue/248
14:08:05 <jwf> #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 ===
14:08:15 <jwf> bkp: Any updates here?
14:09:21 <bkp> Yeah, I didn't remember which ticket had to be updated. shantorn and I looked this up, and found a wealth of information on the wiki. I have written a new proposal and will paste it to #242 now.
14:09:50 <jwf> Excellent!
14:10:16 <bkp> Pasted
14:10:17 <jwf> #info bkp and shantorn did some research and found a lot of info on the wiki - bkp has a proposal and is putting it into #242 now
14:10:22 <jwf> bkp++
14:10:27 <jwf> #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 ===
14:10:32 <jwf> #link https://pagure.io/fedora-marketing/issue/245#comment-172225
14:10:39 <jwf> No remaining actions then – awesome!
14:10:44 <jwf> #topic Tickets
14:10:48 <jwf> #link https://pagure.io/fedora-marketing/issues?tags=meeting
14:10:56 <jwf> #info === Ticket #242: "Update release activity steps / process on the wiki" ===
14:11:00 <jwf> #link https://pagure.io/fedora-marketing/issue/242
14:11:03 * jwf goes to read said comment
14:12:38 <bkp> It's a revision of what was on the Press Kit SOP page.
14:13:04 <bkp> Except now I think everything should be electronic.
14:13:07 * jwf nods
14:13:10 <jwf> Yeah, agreed to that.
14:13:34 <jwf> To some extent, we are doing the release announcement, but not in the context of creating it in a PDF or easy deliverable that we could reproduce for the Ambassadors, for example.
14:13:55 <bkp> If we do want to put something on a stick to hand to press at events, USB sticks run around $7 US each for 4 GB,
14:13:56 <jwf> That could be a nice thing to do, like a printable version of our Fedora Magazine announcement to share with Ambassadors, maybe with links written as footnotes at the bottom
14:14:27 <bkp> Right, or a standing leaflet that has a module to update with current info, logos, links.
14:14:45 <bkp> The Ambassadors could print on demand
14:15:14 <x3mboy> jwf, i'm still working on the print version
14:15:15 <jwf> bkp: I imagine that might be something we do based on the event we're attending, for USBs. Someone in the loop could prepare one before the event, but it will be more difficult to direct part of the Fedora budget for creating the USBs.
14:15:23 <x3mboy> It's still my task, no?
14:15:30 <jwf> bkp: Right, so more or less a template we just have to update with current info and links
14:15:33 <jwf> *?
14:15:44 <bkp> jwf: Yep
14:16:02 <jwf> x3mboy: Print version of the Magazine?
14:16:14 <bkp> x3mboy: Sure. What I am referring to is the one-page release document.
14:16:32 <x3mboy> jwf, yes, the ticket says downloadable version, but is still a pdf version
14:17:05 <jwf> x3mboy: I had closed the ticket since I wasn't sure if it would be something we could easily commit to a long-term sense (i.e. if a plugin breaks, since that was a concern for one where the developer was inactive). My earlier comment was adapting the individual release announcement usually written by Matt on the Magazine on release day.
14:17:51 <x3mboy> Oh ok
14:18:01 <jwf> So, that could be one possible idea of including this in our usual set of tasks for the release. If I'm understanding right, the background / feature modules would be something we could create from our talking points.
14:18:11 <jwf> Well, actually
14:18:30 <jwf> The background modules / notes would be more like Matt's "State of Fedora" data
14:18:40 <x3mboy> Well, I'm still researching a way to do downloadable version, and since we have someone with pdf magazines experience naw in the team, we could polish something
14:18:41 <jwf> The feature modules more like the talking points.
14:18:47 <bkp> jwf: Yes. And they should be semi-permanent, since we won't change our talking points too much over a year's time.
14:19:02 <x3mboy> TPs are per realease, no?
14:19:08 * jwf nods
14:19:20 <bexelbie> not changing our talking points will lead to people ignoring the releases, I think
14:19:32 <bkp> x3mboy: Yeah, but I still think we should have some meta TPs to address "core" audiences.
14:19:49 <x3mboy> Agreed with bexelbie
14:19:55 <bkp> So I guess I was thinking of the meta messaging, not the TPs
14:20:10 <jwf> bexelbie: Not sure I follow what you mean?
14:20:30 <bexelbie> bkp, I can see that.  I agree that our booth messaging may not change a lot during a year, but I think our press messaging needs to make it clear why this release of Fedora is important and different
14:20:43 <bexelbie> they want to write stories about new, not "Fedora released stuff, but nothing changed"
14:21:08 <jwf> Ahh. So I think it's not as much about changing the talking points frequently during the release, you mean, but rather on how we deliver them, right?
14:21:09 <bexelbie> but booth messaging also needs to be very customized to where the booth is
14:21:22 <bkp> bexelbie: Agreed. But I strongly feel that Fedora needs to be messaging that One Big Thing that makes it a better distro choice.
14:21:30 <bexelbie> bkp +100
14:21:36 <x3mboy> +1
14:21:47 * jwf follows now
14:21:50 <bexelbie> jwf, so I believe at Release we need to explain to the press and others why this is the best Fedora ever
14:22:03 <bkp> bexelbie: Right
14:22:05 <bexelbie> jwf, during the release we can visit with different categories of users and help them understand why Fedora is the best for them
14:22:11 <bkp> And the press kits will have that.
14:22:30 <jwf> Okay, yes. :) +1.
14:22:55 <bexelbie> bkp cool - maybe the "talking points" vocabulaly is overused here and we need to be more explicit ?
14:23:05 <bkp> But they should also address whatever overarching metatheme we might have for Fedora during a given period.
14:23:30 <bkp> bexelbie: Yes. I suggest meta points for what I am referring to.
14:23:34 <bexelbie> bkp, yes, we should be building to a story/destination that we periodically move
14:23:44 <bkp> Talking points for release based information
14:23:53 <x3mboy> e.g: Fedora is a Linux Distribution with bleeding edge technologies, best to work with new hardware and new techonlogies, And this new version is the better one because it has support to rasberry pi 4 out-of-the-box
14:23:59 <x3mboy> Something like that?
14:24:12 <jwf> #idea One-page release notes: We are creating release notes, but a one-page deliverable (adapted from FPL's release announcement? something more unique / targeted?) to share with Ambassadors could improve communication of info to Ambassadors and better equip them for events to talk about a new release
14:24:47 <bkp> x3mboy: Perhaps. Or something even simpler, like "Fedora is the Best Dev Distro Ever."
14:24:57 <bexelbie> x3mboy, ignoring hte content of your statement, yes
14:25:04 <bkp> Nothing really that mundane, but a simplified overarching theme.
14:25:07 <jwf> #idea Background modules: Pulling info about Fedora itself, similar to FPL's "State of Fedora" talk data about project metrics for approximate growth, both technical and community?
14:25:19 <bexelbie> jwf, yes for background
14:25:41 <bexelbie> jwf, but most non-community folks may be less swayed by metrics and more swayed by "developing in X is easier on Fedora because y, z, p, q, r"
14:25:50 <bkp> jwf: +1 on background idea.
14:26:03 <jwf> bexelbie: This was in the context for the press kits and what we deliver to the press on release or nearing release.
14:26:12 <bkp> bexelbie: Yes, but remember this is also a press kit, and some data like that could be interesting
14:26:22 * jwf is trying to avoid too much of the talking point discussion right now since that's our next ticket to cover on the agenda. :)
14:26:22 <bexelbie> +1 for inclusion in press release
14:26:32 <bexelbie> I am not sure it should be the top of hte ambassador prep though
14:26:42 <bkp> If we have a document that can do double-duty for press and Ambassadors, so much the better.
14:26:49 <bexelbie> we need to be attracting new users which means going to places that don't know us :)
14:27:28 <x3mboy> bexelbie, Is there a place like that?
14:27:49 <x3mboy> xD
14:28:14 <jwf> So, for building the feature modules, I think this is the part of the press kit that we would be building from meta / talking points… what is the deliverable format of this in the context of the press kit? Is it a PDF? Fedora Magazine articles targeted by audience? How would we build the feature module in a way that we can repeat and practice each release?
14:28:26 <jwf> I'm trying to get an image in my head of what that would look like.
14:28:32 <bkp> I say PDF
14:28:40 <bkp> With a nice layout
14:28:46 <jwf> And also making sure it's reproducable in a way we can follow with some kind of process.
14:28:47 * jwf nods
14:28:51 <bexelbie> do we know how many of our press folks use a press kit vs just want to get stats from a fixed location on our site?
14:29:01 <bkp> That way we can email blast it to press lists, and then print as needed.
14:29:03 * bexelbie is thinking of hte federally mandated stat sites for Universities in the US
14:29:06 <bexelbie> they keep them updated for all
14:29:22 <jwf> bkp: Okay, I follow.
14:29:46 <jwf> bexelbie: That would be a good question to answer. I think it depends on the site – I don't have enough background knowledge or experience to know about how outreach to the press was done in the past.
14:30:04 * jwf wonders if a past Fedora Marketeer might know, perhaps Ruth?
14:30:34 <bkp> I hate to say this, because I hated spam, but depending on press to come to you would be non-optimal.
14:31:12 <jwf> Since my time being involved, I have not been aware of any outreach done that was inside of Fedora Marketing
14:31:35 <bkp> If we were smart, we would throw the raw tet for these documents on GitHib for collaboration and version control, and then pull what we need for each release/event.
14:31:41 <bexelbie> bkp, I agree I just want to make sure the effort we put into making the content in a "press kit" object is useful as opposed to focusing on other presentations.  I also think content trumps all here
14:31:58 <bkp> bexelbie: CONTENT RULZ
14:32:14 <bexelbie> +1 for a pagure repo of hte content with constant efforts to get it exposed
14:32:20 <jwf> I see this as something we could improve on if we establish some sort of process or way to do that each release. Could help to coordinate with Matt / jzb there, since I know there is some RH outreach that happens with Fedora, but I am not aware of it
14:32:23 <bexelbie> and contributed too
14:32:46 <jwf> Yeah, a Pagure repository was something we had on our wishlist two or three releases ago, now that I remember, but I'm not sure where that one fell off at.
14:33:10 <jwf> #idea Creating the press kit in a git forge to encourage community participation and engagement to help expose the content
14:33:23 <x3mboy> +1
14:33:24 <bexelbie> I am not sure we should pin coordination with RH to this.  It isn't htat I don't like RH, but I think any content we develop and find useful they will inherently find useful
14:34:04 * bexelbie goes on a call
14:34:05 <jwf> Also, to cap off on the feature module content, I'm going to log that as an individually crafted PDF that we would try to build based on our release notes / meta points / other things we want to highlight to a wider press audience?
14:34:22 <bkp> jwf: Sounds good.
14:34:38 <jwf> bexelbie: Err, I didn't mean coordination, but it would help to know more about the process for communicating with the press and getting news out, because right now, that's something that's only being done by Red Hat, as far as I know.
14:35:15 <jwf> It would be helpful, I think, to try to engage Fedora Marketing as a medium for communicating with the press and enabling us to do outreach outside of release times, when there is already a lot of eyes on us
14:35:52 <jwf> #idea Feature modules: Individually crafted PDFs based off of release notes / meta points / other things we want to highlight to wider press audience
14:36:06 <Southern_Gentlem> bexelbie,  idea of what would be good would be an update of the pamplets that Ruth and Mizmo did for SXSW several years ago
14:36:38 <bkp> Southern_Gentlem: Yes. We updated the Python one in early 2016.
14:36:54 <jwf> As far as past press coverage goes, we (more or less) have that from some of our recent meetings with the "In the news" section. That lives in wiki and Meetbot currently, but if we go the Pagure route, we could extract that to a Markdown text file in a git repository and keep it updated during a release.
14:37:12 <jwf> Southern_Gentlem: Ooh, could be helpful – what were the SXSW pamphlets?
14:37:24 <Southern_Gentlem> jwf no idea
14:37:41 <Southern_Gentlem> but that is the type of things that would really help the ambassadors
14:38:01 <jwf> Hmm, okay. I can try to do some digging then to find them then. Were they just "About Fedora" or something more specific, or do you not know?
14:38:11 <bkp> jwf Southern_Gentlem Looking...
14:38:18 <jwf> bkp: Thanks!
14:38:45 <Southern_Gentlem> they were about different things from photograpy to music to general linux apps
14:39:10 <bkp> Yeah, I have them on my desk. Trying to find their online homes.
14:39:52 <jwf> #idea Past press coverage: Currently happening in meeting announcements as "In the news", but could be extracted to the press kit in a file that is maintained during the release and kept current
14:40:37 <bkp> Here's the Python one: https://fedoraproject.org/wiki/Marketing/Python_brochure
14:40:52 <jwf> Oh, wow, 20 minutes left already, I misjudged time today…
14:40:53 <jwf> #link https://fedoraproject.org/wiki/Marketing/Python_brochure
14:41:24 <bkp> #link https://fedoraproject.org/wiki/Design/SXSW_Materials#Brochures
14:41:35 <bkp> ^^^ There's the rest
14:42:00 <jwf> Oh, nice!! That really does fit into our earlier discussion about shaping content for audiences…
14:42:14 <bkp> Which, holy mackerel, includes flyers and all sorts of reusable content!
14:42:39 <jwf> Yes… that is actually really awesome to see… :)
14:43:02 <bkp> Our work is done. It's Miller time.
14:43:10 <bkp> :)
14:43:12 <jwf> #idea Integrating targeted brochures / flyers into the press kit especially as a deliverable for Ambassadors to use at events
14:43:14 <jwf> :)
14:44:13 <jwf> Hmm, so as a capping point for this ticket since we're getting down to the last 15 minutes… would it help to create a "press kit" repository to demo the idea of what this might look like, and if we want to pursue this actively as part of our release cycle activities, we look more closely at updating our release cycle activities to reflect the content we want to update there?
14:44:36 <jwf> Even though this is just the press kit, I feel like there's enough discussion happening here to keep us busy for a release without being overwhelmed
14:44:54 <jwf> Some of this is able to easily be abstracted outside of just a press kit too
14:45:18 <Southern_Gentlem> also add the spins to that as well
14:45:45 <Southern_Gentlem> workstation, server and cloud stuff
14:46:03 <Southern_Gentlem> yes a presentation kit
14:46:15 <jwf> I think we're looking at hopefully rounding out the talking points to be based on audience, which would leave room for something like that.
14:47:38 <jwf> bkp / x3mboy / et al. - does the above idea of creating a mock talking point repository to demo the idea seem like a good stopping place, with the intent to follow up with possibly adopting this as part of our release activities and updating our documentation to reflect that?
14:48:05 <bkp> jwf: I would be down for that
14:48:09 <jwf> This is a longer process than it sounds, but I think moving this direction helps move us in a direction to build up Fedora Marketing in present and future tense. :)
14:48:16 <x3mboy> jwf, +1
14:48:56 <jwf> bkp: One thing that might deserve a mailing list discussion is the idea of a what git forge we want to use (I was thinking GitHub might be preferred because of its web editor, making it easier for less tech savvy people to help), but I will action myself to open that discussion on the list.
14:49:22 <bkp> jwf: Noted
14:49:31 <jwf> #action jwf Start mailing list thread about using a git forge for maintaining and creating a press kit for our release cycle activities
14:49:45 <jwf> I have a lot of love for Pagure, but I want to make sure we're using the right tool for our potential audience of contributors too.
14:50:50 <jwf> #agreed Stopping point: Creating a mock press kit repository to demo the idea of where we create our release activities, with the long-term intent to possibly adopt this as a permanent part of the Marketing release cycle activities and updating our documentation to reflect that
14:51:25 <jwf> Since we're down to just 10 minutes, I'm only going to jump to #245 on talking points, and we can revisit the education discussion next week, since that's a big one but we're also a little more flexible on time than the TPs
14:51:30 <jwf> #info === Ticket #245: "Create Fedora 26 talking points" ===
14:51:34 <jwf> #link https://pagure.io/fedora-marketing/issue/245
14:51:39 <jwf> #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.
14:52:33 <jwf> This is definitely one where I'd like to defer to the expertise of some folks who have more experience working in Marketing activities, as far as filtering our target audiences down or figuring out how we want to do that.
14:52:53 <jwf> Context being that x3mboy_ proposed a broad list of some audiences we could try crafting our TPs towards near the bottom of the ticket
14:54:20 <jwf> I have ideas, but they're more off things I think we could shape our talking points to reflect – but this is definitely an area outside of my stronger knowledge area and I'd be interested to hear what you all think.
14:54:43 <jwf> I would think maybe filtering that list down to 4-5 targets and using those for the release
14:55:08 <jwf> But I also just want to make sure we're doing something we can maintain – for example, the entire list would be pretty hard to do until we as a team grow more
14:56:09 <jwf> Thoughts?
14:57:23 * jwf notes we do have a hard stop time now, the KDE SIG meets right after us
14:57:37 <bkp> Triming this down would be good.
14:57:53 <jwf> Do we want to move some discussion about trimming this list to the channel?
14:58:01 <bkp> Yes
14:58:16 <jwf> #agreed Will move the discussion about trimming the list to our channel to free up the meeting channel
14:58:27 <jwf> #info === Ticket #248: " Create an education-focused marketing campaign" ===
14:58:32 <jwf> #link https://pagure.io/fedora-marketing/issue/248
14:58:41 <jwf> #info Not enough time in agenda, will revisit this next week
14:58:45 <jwf> #topic Upcoming Tasks
14:58:51 <jwf> #link https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
14:58:56 <jwf> #info (1) Change Checkpoint: Completion deadline (Tue 2017-02-28)
14:59:02 <jwf> #info (2) Create Talking Points (start: Tue 2017-02-28)
14:59:07 <jwf> #info (3) Proposed Changes Profiles (start: Tue 2017-03-07)
14:59:13 <jwf> #info (4) Email WGs to solicit bullet points for Alpha release announcement (start: Thu 2017-03-09)
14:59:19 <jwf> #topic Open Floor
14:59:40 <jwf> Okay, made it to the end with 30 seconds to spare. We can just go ahead and hop over to #fedora-mktg and finish this discussion.
14:59:50 <jwf> Thanks all to everyone who participated this meeting! :)
14:59:51 <jwf> #endmeeting