21:56:08 <jflory7> #startmeeting Fedora Marketing meeting (2016-02-15)
21:56:08 <zodbot> Meeting started Wed Feb 17 21:56:08 2016 UTC.  The chair is jflory7. Information about MeetBot at
21:56:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
21:56:08 <zodbot> The meeting name has been set to 'fedora_marketing_meeting_(2016-02-15)'
21:56:14 <jflory7> #meetingname marketing
21:56:14 <zodbot> The meeting name has been set to 'marketing'
21:56:19 <jflory7> #chair mailga
21:56:19 <zodbot> Current chairs: jflory7 mailga
21:56:24 <jflory7> #topic Roll Call
21:56:32 <jflory7> #info Name; Timezone; Other sub-projects / interest areas
21:56:53 <jflory7> #info Justin W. Flory; UTC-5; Marketing (Magazine), CommOps, Ambassadors, Join, and more
21:57:17 <jflory7> We'll wait until 5 minutes after the hour to begin going through the agenda, to let people get settled in.
21:57:28 <mailga> .fas mailga
21:57:29 <zodbot> mailga: mailga 'Gabriele Trombini' <>
21:58:34 <jflory7> Oh, should probably #link the agenda
21:58:37 <jflory7> #link
21:58:57 <jflory7> #info ^ Above link is for the meeting agenda (see Comment 3 for agenda outline)
21:59:20 <jflory7> I think I recall stickster saying he was unavailable for this meeting
21:59:25 <mailga> jflory7: do we have to ping someone?
21:59:42 <jflory7> mailga: I believe I tagged everyone that replied on the poll, but let me double check
21:59:50 <jflory7> This time was the best time that worked for most folks
21:59:55 <mailga> Yes stickster was unvailable.
22:01:57 <jflory7> I know jzb also selected this time was not ideal for him, but decause, fale, mitzie, and cprofitt should be around
22:02:07 <jzb> howdy
22:02:13 <jflory7> #chair jzb
22:02:13 <zodbot> Current chairs: jflory7 jzb mailga
22:02:24 <jflory7> Hiya, jzb!
22:02:28 <jflory7> #chair ryanlerch
22:02:28 <zodbot> Current chairs: jflory7 jzb mailga ryanlerch
22:02:36 <jflory7> ryanlerch: o/
22:02:58 <mailga> jflory7: I spoke with fale an hour ago, he wasn't sure about to be here.
22:03:50 <decause> .hello decause
22:03:52 <zodbot> decause: decause 'Remy DeCausemaker' <>
22:04:03 <mattdm> .hello mattdm
22:04:04 <zodbot> mattdm: mattdm 'Matthew Miller' <>
22:04:09 <mattdm> (for the first 20 minutes or so)
22:04:24 <jflory7> #chair decause mattdm
22:04:24 <zodbot> Current chairs: decause jflory7 jzb mailga mattdm ryanlerch
22:04:41 <jflory7> You can find the details about the agenda today here:
22:04:45 <jflory7> Comment #3 has the full outline.
22:05:18 <jflory7> I think we can go ahead and get started?
22:05:33 <jflory7> #topic State of Marketing
22:05:41 <jflory7> #info === Determining active members of Marketing ===
22:05:52 <jflory7> mailga: Did you have any specific thoughts on this one?
22:05:57 <jflory7> #chair stickster
22:05:57 <zodbot> Current chairs: decause jflory7 jzb mailga mattdm ryanlerch stickster
22:06:05 * stickster lurking, has another meeting going on and will have to catch up later. Don't expect much chat from me
22:06:12 <jflory7> Acknowledged, thanks!
22:06:39 <jzb> jflory7: I'd say we look at people who were active in the last release cycle
22:06:55 <jflory7> I think that would be the best indicator
22:07:13 <jflory7> And I think mailga was wanting to do a clean-up of the FAS group for people who have not been active
22:07:15 <mailga> Yes I have, I think that if someone desn't follow some tasks in a cycle tey cannot be considered members.
22:07:41 <mailga> jflory7: yes, that was what I think.
22:07:58 <jflory7> So, I think this one is mostly just having someone take on responsibility to go through the FAS group and identify inactive members.
22:08:22 <decause> jflory7: we ran that script for ambassadors last year
22:08:30 <mailga> jflory7: I'm looking forward for doing that.
22:08:41 <jflory7> Oh, awesome, if we have something readily accessible to maybe repurpose that, that would be excellent
22:08:58 * decause will ask in Fedora-infra
22:09:16 <jflory7> decause: Sounds good -- in the event that we can't get the script, do you want to take this one, mailga?
22:09:25 <mailga> decause: that script parses fedmesg, afaik.
22:09:33 <jzb> how would a script determine that for mktg?
22:09:47 <mailga> jzb +1
22:09:49 <jzb> I mean, a lot of stuff (release announcement) is not tracked.
22:09:52 <jzb> by fedmsg
22:10:15 <decause> #action decause find the FAS inactive members script and if it exists
22:10:49 <jflory7> jzb: I would think it would probably look at general activity in some way, although I imagine if someone is editing the release announcement, they are probably doing some other things in marketing too :)
22:10:51 <mailga> decause: ask robyduck
22:11:06 <mailga> decause he's aware about it.
22:11:08 <jzb> jflory7: well, what is tracked by fedmsg?
22:11:16 <jzb> jflory7: that's related to marketing?
22:11:27 * robyduck here
22:12:01 <mailga> robyduck: do you think the script used for marking amby inactive is useful also for mktg?
22:12:21 <robyduck> yes
22:12:32 <jzb> jflory7: I'm pretty sure that about 0 of the marketing stuff is happening on fedmsg bus.
22:12:37 <jflory7> jzb: Hmmm, off the top of my head, it would be wiki edits and mailing list activity
22:12:56 <mailga> jflory7 jzb also tickets.
22:12:58 <jzb> jflory7: mailing list only shows you said something, though - not that someone actually did anything :-)
22:13:01 <jzb> wiki edits, OK
22:13:03 <jflory7> Yeah, Trac as well
22:13:12 <jzb> is that tracked (ahem) by fedmsg?
22:13:19 <decause> jzb: yes, tickets are
22:13:32 <jzb> ok
22:13:37 <decause> *not* bugzilla tickets though
22:13:39 <jzb> so
22:13:51 <jzb> I would also say we need to be OK with judgement calls
22:13:54 <jflory7> I think if we could run it and get the list of people before clearing it, we could use manual approval first
22:13:56 <jflory7> There's only 60 people
22:14:02 <jflory7> Much smaller number to work with Ambassadors
22:14:04 <decause> jflory7: yeah, that is what we did last time
22:14:12 <robyduck> mailga: decause: it uses FAS and datagrepper
22:14:13 <jflory7> In the interest of time, I say we delegate this one to decause and mailga, and we push on into the agenda
22:14:13 <jzb> honestly there's maybe 8 people who've done anything with marketing (not incl magazine) in the last release cycle.
22:14:15 <decause> we got the list of inactives, and then manually deactivated IIRC
22:14:29 <decause> jflory7: agreed
22:14:47 <decause> robyduck: plz send me/mailga a link after this if you got one
22:14:48 <jflory7> #info decause and mailga to look more into cleaning up the FAS group membership
22:14:57 <jflory7> Let's push on
22:14:57 <jflory7> #info === Looking at requirements for joining Marketing ===
22:15:06 <jflory7> Were there any specific thoughts on this one?
22:15:15 <jflory7> If I recall, we kind of discussed this in the ticket
22:15:18 <jzb> jflory7: wasn't that about the FAS group?
22:15:25 <jzb> jflory7: I think it was "you have to have done something"
22:15:29 <jflory7> Pretty sure that was too
22:15:29 <robyduck> decause: ok
22:15:31 <jflory7> Yeah.
22:15:44 <jzb> any objections on that?
22:15:47 <decause> this goes along with the "onboarding" and "join" process
22:15:58 <jflory7> So, I think this one goes hand-in-hand with waiting to approve new FAS members before having a record of active contribution
22:16:05 <decause> 1) create fas account 2) intro on mailing list 3) attend meetings 4) do something
22:16:06 <mailga> jzb: I agree but I think that a wiki cleanup is not enough.
22:16:47 <jflory7> mailga: So better monitoring of a member's activity?
22:17:22 <mailga> jflory7: yes. We should define some tasks.
22:17:23 <jzb> mailga: sorry?
22:17:54 <mailga> jzb: I think that someone could take care of a wiki page
22:18:08 <jflory7> mailga: I'm thinking we add a ticket to the Trac to identify some holes in our Join process and improve on our own judgment of what makes someone a member?
22:18:14 <mailga> but it isn't enough for being a member. IMHO.
22:18:28 <jzb> ah
22:18:29 <jflory7> I think ticketing that one might be best so we can push on -- we're about to hit the 20 minute mark
22:18:52 <decause> jflory7: agreed. lets create a ticket for both editing the wiki page, and a ticket for updating the join process
22:18:57 <mattdm> yeah, we've met the "time for me to run off" mark. :)
22:19:11 <decause> mattdm: thanks for being here, I'll update you when next we talk
22:19:12 <mailga> jflory7: +1 this will be a long discussion..
22:19:29 <jzb> so
22:19:30 <decause> mattdm++
22:19:30 <jflory7> #action jflory7 File a ticket on the Trac to open discussion about Marketing Join process
22:19:40 <jflory7> mattdm: Thanks for coming out!
22:19:45 <jzb> IIRC we *had* this discussion more than a year ago
22:19:56 <jzb> about membership, etc.
22:20:00 <jzb> we can revisit, but ...
22:20:04 <decause> #action decause create onboarding badge ticket for mktg based on join ticket in marketing trac
22:20:22 <jflory7> If we can get that linked in that ticket, it will help to have something to go off of than rebasing our entire discussion again then.
22:20:32 <jflory7> Let's move onto the next topic
22:20:33 <jflory7> #topic Comments on "Marketing - Year in Review"
22:20:34 <decause> I think we should have this conversation out of meeting on the ticket
22:20:35 <decause> yes
22:20:38 <jflory7> This one should be a quick rehash
22:20:43 <jflory7> #link ​
22:20:48 <jflory7> #info * Stickers identified as a major want, these are now available on UnixStickers?.com
22:20:52 <jflory7> #link ​
22:20:57 <jflory7> #info * Requested desire for updated banners and promotable digital material by users
22:21:01 <jflory7> #link ​
22:21:06 <jflory7> #link ​
22:21:11 <jflory7> #link ​
22:21:22 <jflory7> Are the updated images for F23 enough or do we want to request for updated versions of other, general banners (e.g. things to be used in forum signatures, embedded in websites, etc.)
22:21:47 <jflory7> I had opened a ticket in the Design Trac for these to be updated, but it was closed because there are updated images for F23 and each release
22:22:01 <jflory7> They're not the same types of images linked in the PromoBanners page, however
22:22:11 <jflory7> The ones used now are a much smaller subset
22:22:36 <jflory7> In either case, I think the main decision here is if we want to follow up with the Design Team to update the existing images or if we want to better promote the existing subset of current images.
22:24:25 <jflory7> I am personally +1 for following up on getting the images on that page updated
22:24:30 <jflory7> Or at least having that process initiated
22:24:43 <jflory7> Some of them are unique types, like signatures / banners versus the ones that are currently produced
22:24:50 <jflory7> I think we need to do a better job of highlighting those, however
22:25:47 <mailga> jflory7: +1 also from me
22:26:34 <jflory7> I will go ahead and action that to me to follow up -- we'll wait another minute or two for any last comments and then we'll push on
22:26:57 <decause> jflory7: you can cc me on those comms, you won't be going it alone.
22:27:08 <decause> I'm sensitive to the reduced cycles that design team has right now
22:27:19 <jflory7> #action jflory7 Follow up with Design Team Ticket #422 offering clarification and requesting for other existing images be updated for reusable, release-neutral images
22:27:27 <jflory7> decause: I'll CC you on that ticket as well.
22:27:30 <jflory7> decause++
22:27:31 <mailga> jflory7: if you need further help please ping to me.
22:27:36 <jflory7> mailga: Sure thing. :)
22:27:47 <jflory7> Let's go ahead and move on to the big parts of this meeting
22:27:51 <jflory7> #topic Marketing Tasks for F24
22:27:57 <jflory7> #link ​
22:28:02 <decause> mailga++
22:28:05 <decause> nice work updating the list
22:28:16 <jflory7> #info Past deadline: Cleaning up the wiki post-release (mailga already took care of these tasks)
22:28:25 <jflory7> #info Upcoming deadlines: Fedora change checkpoint and creating talking points (how do we want to handle this?)
22:28:50 <jflory7> Identifying what the next steps are for the upcoming tasks are important
22:28:51 <mailga> jflory7: I can take care of all the tasks, I like it
22:28:54 <decause> jflory7: IIRC the process is:
22:28:55 <mailga> bu
22:28:58 <mailga> but
22:29:02 <decause> ask the WG's for their PRD's
22:29:09 <decause> make talking points from those?
22:29:18 <decause> correct me if I'm wrong anyone
22:29:28 <mailga> what does it means checkpoints for mktg?
22:29:51 <jzb> decause: the PRDs are outdated
22:30:08 <jzb> and the talking points probably won't flow from the PRD but the features for F24 that are actually going forward.
22:30:11 <jflory7> I think this probably bleeds over with jzb's last comment on the ticket about working closer with devel
22:30:18 <jzb> right
22:30:23 <jzb> so...
22:30:26 <jzb> <soapbox>
22:30:47 <jzb> we're going to have to actually do some hand-holding with each workgroup and have people all over this for at least two release cycles
22:31:02 <decause> nod nod
22:31:09 <jzb> meaning, members of the marketing group need to divvy up areas -- or "beats"
22:31:18 <jzb> and commit to delivering the talking points and text for those areas
22:31:24 <jzb> this is a lot of legwork
22:31:36 <decause> kk, how many 'beats' are there?
22:31:41 <jzb> but we need to be visible talking to people outside marketing
22:31:45 <jzb> </soapbox>
22:31:59 <jzb> decause: one for each edition + spins + developer story
22:32:03 <jzb> off the top of my head
22:32:04 <decause> jzb: is devel list too visible?
22:32:14 <jflory7> I'm +1 to divvying up the tasks
22:32:23 <jzb> decause: sorry? how do you mean too visible?
22:32:26 <decause> err, bad wording, but I think you know what I mean.
22:32:27 <decause> yeah
22:32:46 <decause> would it be too noisey to be making those conversations visible on the devel list?
22:32:49 <jzb> ah
22:33:13 <jzb> well, I think we'd have a conversation on each edition mailing list
22:33:22 <decause> nod nod nod
22:33:23 <jzb> and maybe a "hey, we're here, I'm here to help" on -devel
22:33:29 <jzb> Shamefully
22:33:30 <decause> cool cool
22:33:30 <jflory7> So (3) editions, (6) spins, (?) developer story side of things
22:33:38 <jzb> I am not sure if we have a spins list or lists for each spin.
22:33:47 <jflory7> I don't think all of them do
22:33:58 <jzb> jflory7: I mean, one person can probably do multiple spins
22:34:04 <jflory7> Yeah, for the smaller ones
22:34:09 <jzb> and I don't know if each spin has a story for f24
22:34:14 <decause> jflory7: I am thinking a similar strategy to our "YiR" requests may fit the bill
22:34:16 <jzb> it might be a slow cycle for, say, KDE
22:34:34 <decause> jflory7: we give folks a template, and help them fill it in, post to commblog, and then point to the commblog on mailing lists
22:34:54 <jflory7> decause: I think providing the resources to make it easy is excellent
22:35:23 <decause> we already develop the talking points in public, and we got *good* feedback from folks like Fedora-infra on soliciting input and making it visible
22:35:38 <decause> so, we need a 'talking points" template then
22:35:55 <decause> what is the timeframe for this?
22:36:24 <jflory7> decause: I would assume the end goal is to get this info easily available to people like our Ambassadors pre-F24
22:36:42 <decause> jflory7: the talking points are part of the release tasks calendar though
22:36:45 * decause looks at it
22:37:04 <decause> 3/8
22:37:25 <jflory7> Ahh, yeah
22:37:37 <jzb> so we need talking points to start the alpha release, really
22:37:54 <jzb> not finished, but we need some skeleton by the time we do alpha so we can shape the alpha release announcement.
22:38:16 <jzb> otherwise the release announcement is basically "we did a thing!"
22:38:17 <jzb> :-)
22:38:19 <decause> let's try to get all of our feedback from the WG's by the 8th then?
22:38:37 <decause> and announce the official talking points on commblog EoW?
22:38:39 <decause> that week
22:38:47 <jflory7> Sounds like the beginnings of a plan to me... do we want to do some assigning now, and maybe take to the list for some others?
22:38:53 <mailga> decause:
22:39:00 <jflory7> I don't want them to stall out on the list, though
22:39:12 <jzb> I can take cloud/atomic
22:39:13 <decause> jflory7: this is the "hand-holding" that jzb was talking about
22:39:21 <decause> jzb++
22:39:36 <jzb> and I'm also interested in developer story
22:39:50 <decause> jzb: do we know who traditionally/historically has provided these before from the WG's?
22:40:11 <jzb> decause: yes, I've pinged the lists and typically stickster has helped on Workstation
22:40:21 <jzb> I think sgallagh has helped with server
22:40:40 <jzb> at least I dimly recall him replying when I'd ask "so, uh, what's up with Server?"
22:40:50 <decause> jzb: kk, we'll very politely ask stickster. I think sgallagh is dialing down his WG involvment and devving like mad on other things
22:40:59 <jflory7> I could take a spin or two
22:41:17 <mailga> jzb: was the approved features the starting point?
22:41:19 <jzb> yes
22:41:28 <jzb> sorry, the yes was directed at decause
22:41:36 <decause> jflory7: ok, I know it is going to be a *bunch* of tickets, but after this meeting lets create a ticket for each beat, and assign/cc the ones we know for sure.
22:41:39 <jzb> mailga: ish? Often we need a reality check there.
22:41:58 <jzb> mailga: just because it's filed and approved doesn't mean it's actually happening.
22:42:03 <jflory7> decause: +1
22:42:13 <mailga> jzb agreed, I saw some difference.
22:42:16 <decause> jflory7: commops hack session tonight is gonna be hoppin ;)
22:42:25 <jflory7> decause: I had it for tomorrow? :o
22:42:32 <decause> ok, then tomo
22:42:37 <jflory7> Hahah :)
22:42:37 * decause is too excited :P
22:42:43 <jflory7> decause++
22:42:49 <jflory7> I can make the tickets for all the spins + editions
22:42:56 * fale just arrived
22:42:59 <jflory7> If no one else had their heart set on doing it.
22:43:06 <decause> jflory7++
22:43:08 <decause> fale: welcome
22:43:12 <jflory7> #chair faffolter
22:43:12 <zodbot> Current chairs: decause faffolter jflory7 jzb mailga mattdm ryanlerch stickster
22:43:14 <jflory7> Whoops
22:43:17 <jflory7> #unchair faffolter
22:43:17 <zodbot> Current chairs: decause jflory7 jzb mailga mattdm ryanlerch stickster
22:43:18 <mailga> jflory7: do we work with tickets about talking points?
22:43:20 <jflory7> #chair fale
22:43:20 <zodbot> Current chairs: decause fale jflory7 jzb mailga mattdm ryanlerch stickster
22:43:36 <jflory7> mailga: Talking points for each spin + edition + general developer side of things
22:44:07 <decause> mailga: the talking points themselves don't have to go into the tickets, but we want to track the progress and own tasks officially with them
22:44:17 <mailga> jflory7: maybe we need to mark the ticket somehow.
22:44:21 <jflory7> #action jflory7 Create tickets for talking points for all of the different spins and editions, CC those who we know for sure to take them on
22:44:32 <decause> adding the talking points isnt' necessary, but could be helpful for keepign everything in one place
22:44:37 <jflory7> Time check, 15 minutes on the clock
22:44:40 <decause> jflory7: yep
22:44:45 <jflory7> Do we want to push on to the next topic?
22:44:49 <mailga> decause ok
22:44:59 <decause> jflory7: release announce is a big one, tickets we'll check in on next week for sure
22:45:07 <jflory7> Mhmm.
22:45:09 <faffolter> thanks for unchairing me
22:45:15 <jflory7> faffolter: My bad :P
22:45:19 <decause> plate is kinda full for this week, maybe we can target next week for the announcement and mail-list pushes?
22:45:40 <jflory7> decause: Seems reasonable to me
22:45:49 <decause> jflory7: kk, let's add it to commops agenda too
22:46:02 <jflory7> Mutual ticket, yeah
22:46:02 <decause> we're supporting mktg on this
22:46:06 * jflory7 nods
22:46:13 * mailga thinks we should skip also the magazine point.
22:46:21 <jflory7> So, last call for marketing F24 tasks, going once--
22:46:28 <jflory7> Going twice--
22:46:33 <jflory7> Going thrice--
22:46:39 <decause> we'll divvy up the beats next time if no one has claimed the remaining ones
22:46:42 <jflory7> #topic Future Plans: Marketing
22:46:53 <jflory7> How do we want to proceed with meetings (e.g. frequency and length)? How can we best keep on track of tasks? Fedocal reminders in the Marketing calendar for every deadline? What do we propose?
22:47:05 <decause> +1 for weekly meetings
22:47:07 <jflory7> These are what I put on the ticket, we can add other things in here as necessary
22:47:08 <decause> +1 for fedocal
22:47:16 <jflory7> +1 for weekly meetings too
22:47:23 <jflory7> mailga: Depending on time, dropping it might be best and deferring to next week
22:47:42 <mailga> +1 for weekly meetings and fedocal remind.
22:47:44 <jflory7> I think tickets will be the best way to keep track of tasks, in my opinion
22:47:53 <jflory7> I believe Fedocal should be set up that way, but I will double-check
22:48:00 <mailga> jflory7: sure thing.
22:48:05 <decause> +1 for trac
22:48:24 <jflory7> Here, I'll make a big proposal for all of these things:
22:48:28 <fale> +1 for weekly meetings, fedocal and trac to track tasks
22:48:44 <JohnMH> -1 for everything being written in Python :(
22:48:56 <decause> JohnMH: wat?
22:48:58 <jflory7> #proposed +1 for weekly meetings set up with Fedocal reminders, and using Trac tickets as the best way to keep on top of tasks in the release cycle
22:49:01 <jflory7> +1
22:49:08 <fale> +1
22:49:09 <decause> +1 proposal
22:49:12 <mailga> +1
22:49:20 <JohnMH> +1
22:49:24 <JohnMH> decause: Not relevant, just a remark
22:49:29 <decause> JohnMH: lol, k
22:49:29 <jflory7> Going once--
22:49:34 <jflory7> Going twice--
22:49:41 <jflory7> Going thrice--
22:49:46 <jflory7> #agreed +1 for weekly meetings set up with Fedocal reminders, and using Trac tickets as the best way to keep on top of tasks in the release cycle
22:50:00 <jflory7> Any other discussion items for this topic of Future Plans for Marketing?
22:50:15 <decause> jflory7: we're going to be focusing big-time on python outreach this year
22:50:20 <jflory7> Ahhh, right
22:50:20 <jzb> jflory7: all plans are future plans ;-)
22:50:26 <decause> with PyCon 5/28 being the deadline for much of our messaging
22:50:29 <jflory7> This is a good topic for now, decause
22:50:29 <JohnMH> decause: Funny
22:50:33 <decause> more to come on this, but needed to get it on the radar
22:50:37 <decause> and yes, that is funny JohnMH :P
22:50:37 <jzb> JohnMH: ?
22:50:50 <fale> also there are many other Python events/PyCon scheduled by EMEA Amby
22:50:55 <JohnMH> decause: Less of a Python approach, and more generalized would be nice, honestly
22:51:07 <decause> fale: did the EMEA ambassadors make a list of the python events?
22:51:07 <jflory7> #info Increased focus on Python outreach in 2016 -- PyCon on May 28th is on the radar, more information about this to come soon
22:51:15 <jzb> JohnMH: the idea behind focusing on Python is that we have limited resources
22:51:25 <jzb> JohnMH: let's focus on one area that we can show results in and then expand
22:51:34 <jzb> we've already seen we can't boil the ocean.
22:51:34 <jflory7> jzb: +1
22:51:36 <fale> decause: as far as I know not yet, but I can do it
22:51:39 <decause> JohnMH: so yes, it would be good, but falls under the same line of htinking as the editions strategy. Focus.
22:51:54 <JohnMH> I suppose that's a decent point
22:51:57 <fale> #action fale will create a list of EMEA Python events of 2016
22:51:59 <jzb> that said, there's nothing that restrains anybody from working up strategy for $other
22:52:01 <decause> fale: that would be super helpful, because then we can make sure we're taking regional deadlines into consideration as well
22:52:02 <JohnMH> Java outreach would be fairly easy
22:52:04 <decause> fale++
22:52:09 <jzb> so if we have a group that's interested in Java
22:52:13 <jzb> they are fully empowered
22:52:18 <jzb> we aren't going to block anything
22:52:23 <jzb> just declaring an area of focus
22:52:38 <JohnMH> Of course
22:52:47 <jzb> so if an army of Java folks roll up with materials and a plan, totally ready to greet them with open arms
22:52:48 <decause> JohnMH: we could *absoltely* use java specific talking points as well
22:52:53 <jzb> hugs and puppies all around
22:53:10 <decause> coming up with a list of java events, and java upstream partners and members would be helpful in making that list
22:53:24 <decause> JohnMH: is there a java sig?
22:53:31 <JohnMH> I don't know, looking now
22:53:36 <decause> that is the kind of place where we can ask for help as mktg as well
22:53:39 <JohnMH> Yes
22:53:40 <JohnMH> Seems to be
22:53:42 <jflory7> decause: There is a Java SIG
22:53:46 <jzb> is it active?
22:53:46 <decause> JohnMH: when is eclipsecon?
22:53:48 <jflory7> Not sure how active they are currently
22:53:51 <fale>
22:53:57 <jflory7> fale++
22:54:13 <jflory7> mailga: Yeah, I'm thinking we do push Magazine into next week's meeting
22:54:20 <decause> so, whatever python talking points process/infra we make, lets make sure that it can be generalized for other audiences too
22:54:25 <jflory7> Hopefully we can grab stickster too then, maybe ryanlerch if we're lucky :)
22:54:51 <decause> the process, the wiki templates, etc..
22:54:57 <fale> Since the majority of Fedora tools are written in Python, probably many python points _can not_ be generalized
22:55:16 <decause> fale: not the actual talking points themselves, but the ways that we create them and askf or them
22:55:24 <mailga> jflory7: I think actually we're losing the meeting focus. We cannot talk anbout each SIG in a meeting. Let's talk about them in ML.
22:55:36 <decause> the process, so that it isn't up to one person each year going forward
22:55:40 * fale is always pro sharing methodologies
22:55:45 <decause> s/year/release
22:56:03 <jzb> mailga: ok
22:56:04 <decause> mailga: agreed
22:56:07 <JohnMH> decause: March 7th
22:56:07 <JohnMH> on through the 10th
22:56:24 <decause> may be tight, but we can talk more about it off list
22:56:37 <decause> JohnMH: you should join #fedora-commops and #fedora-mktg and we can talk more there after
22:56:40 <decause> JohnMH++
22:56:49 <JohnMH> Alright
22:57:12 <jflory7> mailga: +1
22:57:22 <jflory7> So, I think that wraps up this topic for now then
22:57:26 <jflory7> Going once--
22:57:32 <jflory7> Going twice--
22:57:34 <decause> we're at 3 mins left
22:57:36 <jflory7> Going thrice--
22:57:44 <jflory7> #topic Open Floor
22:57:58 <jflory7> #info Magazine topic deferred to next week's meeting (low on time)
22:58:05 <jflory7> Anything else we want to get in now?
22:58:05 <decause> #info decause is very happy with the turnout today :)
22:58:23 <jflory7> jzb: Curious, will you be able to make this time in the future as well?
22:58:47 * mailga thinks there are enough stuff on which work on for this week...
22:58:54 <jflory7> mailga: Hahah, agreed
22:58:55 <jzb> jflory7: mostly, with objections to it being past EOD
22:59:04 <jzb> but, yes
22:59:19 <jflory7> Okay, I'm glad we are able to get you in this time slot then
22:59:19 <decause> jzb++
22:59:23 <jflory7> jzb++
23:00:01 <robyduck> decause: outputs in your mailbox, see you soon.
23:00:10 <jflory7> So, I think we can go ahead and gavel out... there will be a lot on the plate for the next week.
23:00:21 <jflory7> Closing out in: 5
23:00:23 <jflory7> 4
23:00:24 <jflory7> 3
23:00:25 <decause> robyduck++
23:00:25 <jflory7> 2
23:00:27 <decause> :)
23:00:27 <jflory7> 1
23:00:29 <jflory7> #endmeeting