20:01:28 #startmeeting 20:01:38 Hey, JonRob. :) 20:02:01 * sdziallas is here :) 20:02:30 * ianweller 20:02:54 hi 20:02:58 * pbrobinson is here 20:03:02 hey mizmo, ianweller, pbrobinson. 20:03:16 Awesome. 20:03:20 * stickster 20:03:26 Let's get started; we've got logs for people who come in later 20:03:43 This meeting is a little different, in that I'm hoping to go *really* fast through our usual agenda 20:03:52 in the hopes that we'll have space to talk about some other things 20:03:59 https://fedoraproject.org/wiki/Marketing_F12_schedule is our usual 20:04:12 but http://fpaste.org/paste/20205 is what I'd like to do. 20:04:17 (I'll repaste it line by line here.) 20:04:28 1. Make sure we all understand the current (ideal) F12 schedule - where we're supposed to be according to our current plan. 20:04:36 2. Make sure we all understand our current completion status of the F12 schedule - where we are, according to our current plan. 20:04:47 2. Make sure we all understand our current completion status of the F12 schedule - where we are, according to our current plan. 20:04:51 er, I mean... 20:04:56 3. Make sure that the F12 schedule we have is the one we actually want to have. What do we want Marketing to be and do - and what can we do towards that for this release? 20:05:10 A little vaguer, but we should be getting as many of those things into actionable milestones as possible, as fast as possible. 20:05:19 4. Make sure our plan is sane - make sure it syncs up with other groups we need to work with on specific points (Design, News, Docs, Ambassadors, Websites... who else?) 20:05:27 We need to finish #4 by Monday. 20:05:51 ...and that's why I'm going to be sprinting full-out during this meeting and trying to move things super-fast. 20:06:04 mchua: Rah rah! 20:06:07 It may not work. Yell if it looks like we're about to careen into a wall. :) 20:06:18 Any questions? 20:06:19 * stickster finishes with stats junk and is paying full attention now 20:06:24 (Ask 'em anytime. Interrupting is good.) 20:06:30 So! let's look at https://fedoraproject.org/wiki/Marketing_F12_schedule! 20:07:00 I'm going to go down the list and skip the vast majority of stuff that looks like it's on track. 20:07:06 Yell if I'm skipping something you'd like to discuss. ;) 20:07:32 "Docs/Marketing release notes workflow" is... of unknown status. If anyone knows anything about that, holler. 20:07:36 Otherwise I'll check with Sparks later. 20:07:43 skipping down. 20:07:50 can we get an update on list? 20:07:50 ianweller already ate his banana, so we're covered there. :) 20:07:55 i'd def like to know more about that! 20:07:55 JonRob: Yes, that's a great idea. 20:08:08 JonRob: Let's try to get task updates on the list instead of at this meeting, actually - that's a *great* idea. 20:08:12 mchua: I think the 1-pager is still going to happen; I'm not sure if Sparks has gone any further 20:08:27 #action mchua to make sure this is the last marketing meeting we do status-check-ins on individual tasks at. 20:08:46 mchua - awesome :) 20:08:49 * stickster agrees, the task list also ought to list those things that we clearly know when they get finished 20:08:54 So JonRob, that means we'll take the notes about your meeting with pcalarco to discuss News workflow for FI to the list, too. 20:09:02 stickster++ 20:09:14 i.e. "coordinate with so-and-so" is not clear to me... although that may be just me. 20:09:15 actually... 20:09:24 JonRob: Yessir? 20:09:33 i'm going on holiday tomorrow, will be out of action for 2 weeks 20:09:36 stickster: no, you're right, each task should also have a clear outcome. 20:09:44 JonRob: Yay, holiday! 20:09:45 JonRob: Anything we can handle while you're out? 20:09:46 need someone else to meet with pascal, who's just got back from hols himself 20:09:53 stickster: yes, lol 20:10:13 i'll forward a message to list, but will need someone to pick that up for me 20:10:24 JonRob: If you do that, we can surely pick it up. 20:10:30 great 20:10:32 JonRob: I'll reopen the item on the task list. 20:10:36 * stickster raises his hand since this is somewhat Zikula-related 20:10:36 JonRob: Thanks for the heads-up. 20:10:40 stickster: go! 20:10:53 mchua: Oh, I just meant raised my hand to help with JonRob's bit 20:11:10 stickster: Oh, then I'll s/JonRob/stickster in that case :) 20:11:19 JonRob: does that also go for "FI workflow/content plan"? 20:11:27 cool, shutting up now 20:11:44 yeah - that's linked with pascal meet 20:11:50 although, i'll post some thoughts i've had later 20:11:51 ...actually, wait, this is exactly the kind of thing I just said we should do on-list... 20:11:53 yessir. 20:11:56 lol 20:12:14 We are done with the "General tasks not tied to a particular Fedora release cycle" list. 20:12:22 now https://fedoraproject.org/wiki/Marketing_F12_schedule#The_6_weeks_leading_up_to_Alpha_.282009-07-07_-_2009-08-18.29 20:13:03 ...i think we're good there, unless stickster needs anything before sending the call for help on talking poings 20:13:06 er, points. 20:13:32 Nope, note that I already filled in the points raised on list, since there was no further input 20:13:36 Awesome. 20:13:39 So we're done with that section too. 20:13:42 http://fedoraproject.org/wiki/F12_talking_points 20:14:03 And I'd like everyone here to take a moment between now and our next meeting (and I'll ask people to do this on the list) to look at the remainder of the schedule and ask questions about the parts where I didn't fill in good enough descriptions. ;) 20:14:20 I want to make sure that anyone can walk in and look at a task and not have to go "well, what do you mean by /that/?" 20:14:53 ...and with that, I'm done with #1 and #2 on my meta-agenda for today ("what is our roadmap now?" and "where are we on it?") 20:15:04 a couple of ideas for the tasks: 20:15:09 (1) have u considered trac to track them 20:15:18 (the answers being https://fedoraproject.org/wiki/Marketing_F12_schedule, and we are on or ahead of schedule. 20:15:23 mizmo: That. Is a brilliant idea. 20:15:25 (2) maybe have a contact person for each besides owner? eg the person to ask for more info, for a task that nobody owns yet 20:15:36 mizmo, is that not the owner? 20:15:40 oh i c 20:15:51 oops, sorry for text talk and not reading properly 20:15:52 Right, "owner" seems to shout, "I'm under control! Move along!" 20:15:55 mizmo: ...ooh, what would you call that person? 20:16:01 POC 20:16:02 JonRob: well fore xample, in the design team queue, stickster might ask us for an icon, and if tatica decides to take that ticket, tatica is the owner but stickster is the requestor/contact 20:16:05 "Contact" 20:16:14 mchua: contact prolly 20:16:28 #action mchua ask mailing list to look at F12 schedule and ask questions about the parts where I didn't fill in good enough descriptions about tasks 20:16:40 mizmo: does trac work well for the Design team? 20:16:49 I'm a fan of using actual work-tracking systems to... track work 20:16:50 in general 20:16:59 mchua: ohmigod yes, it's a breath of fresh air & organization that we never had. we used to use the wiki and it was a nightmare to edit 20:17:09 so painful to keep updated we didn't as well as we should have :) 20:17:18 * mchua dances in joy 20:17:18 trac is much easier to work with and you get automatic notifications by email 20:17:36 mizmo, who put that system in place for the design team? 20:17:49 what i really love about it, if noobs come along asking to help, i can point them to the open & unassigned task list, and recommend categories they might want to try 20:18:00 mchua is the lord of the dance :p 20:18:00 mchua: stickster had the trac instance set up and ianweller transcribed the tasks into it 20:18:22 i believe it was originally sticksters idea :) 20:18:23 wow. 20:18:30 is anyone interested in making this happen for marketing? 20:18:36 (I am, if nobody else is) 20:18:40 (I <3 trac) 20:18:50 And it's actually pretty easy to add keywords like "easy" so you can have a report that just shows you tickets that are easy to handle 20:18:55 feh, I'll do it this week, it'll help me keep track of stuffs 20:19:03 #action mchua to make marketing task-tracking trac-o-riffic, like design 20:19:05 * stickster used the word "easy" like, five times there. 20:19:26 I will call for help on this and holler loudly at every step of the process so that people will have ample opportunity to take work off my shoulders ;) 20:19:34 mchua: I can help you 20:19:37 that was easy 20:19:52 yay for stickster! 20:19:54 It wouldn't be hard to integrate the tasks for release there, either, against e.g. a "F12" milestone 20:19:57 * mchua nods 20:20:05 ok, so trac discussion continuing on ze list 20:20:16 * stickster tries to help with some of these things because he can't keep on one context long enough to do more helpful things for each team 20:20:21 bonzer 20:20:24 * mchua nods 20:20:47 so, I'd like to open up the floor for the Big Vague Question Of The Day 20:20:49 "Make sure that the F12 schedule we have is the one we actually want to have. What do we want Marketing to be and do - and what can we do towards that for this release?" 20:21:43 In other words... we've got our current todo list. But maybe it's not the todo list we need to have. 20:22:15 mchua: do you have thoughts about how to change it? 20:22:25 JonRob: Kind of. Half-formed ones. 20:22:31 a lot of what's on it is what i suggested in the original email where i proposed a release/time based schedule 20:22:42 things like content production/media outreach 20:22:45 mchua: Is poelcat's schedule available yet from the meeting you and I had with him? 20:23:04 so i'm quite happy with what's there, but open to improvements :) 20:23:05 Hm, maybe not yet 20:23:09 stickster: https://fedoraproject.org/wiki/Marketing_F12_schedule is updated from our discussion with poelcat yesterday. 20:23:16 mchua: Ooo, brilliant! 20:23:45 JonRob: wow. can you find the link to that? 20:23:48 * mchua trying to find the link to that 20:24:05 we should - we should definitely go off that list. 20:24:12 You've got much more context than I do on this. 20:24:31 mchua: it was a long time ago... a year or more 20:24:43 history is great. 20:24:51 We often don't learn enough from it. 20:24:53 was def end of term, so either december, aprilish, or juneish 20:24:59 i'll see what i can find 20:25:08 hey guys sorry im a little late 20:25:11 hey themayor! 20:25:16 glad to have you here. 20:25:34 hey themayor 20:25:53 mchua: http://www.mail-archive.com/fedora-marketing-list@redhat.com/msg07390.html 20:25:56 perhaps 20:26:01 #link http://www.mail-archive.com/fedora-marketing-list@redhat.com/msg07390.html 20:26:09 hey sorry, i went to meet up with someone here close to the office and we went a bit overtime and the cab was like hell trying to get back stuck in traffic 20:26:25 themayor: No problem 20:26:30 Wow. JonRob, your list includes most of mine, except it's *better.* 20:26:46 themayor: it's all cool. :) 20:27:03 mchua: Looking at your item underway... 20:27:14 #topic Make sure that the F12 schedule we have is the one we actually want to have. What do we want Marketing to be and do - and what can we do towards that for this release? 20:27:29 * stickster can't control M. Bot 20:27:39 stickster: thanks for the refocus. :) 20:27:48 So, https://fedoraproject.org/w/index.php?title=Marketing says that we... 20:27:54 "The Fedora Marketing team develops marketing strategies to promote the usage and support of Fedora worldwide. Through the development of processes and content, this project aims to support the efforts of other Fedora projects to spread Fedora and to provide a central repository of ideas and information that can be used to deliver Fedora to new audiences." 20:28:03 "For that, we are closely working with the Fedora Ambassadors, this is the grass-roots team that spreads Fedora on the ground and allows the Fedora Project to interact directly with its existing and prospective users. " 20:28:16 We advertised the call that Mel and I had with John Poelstra, where we talked a bit about that focus in hopes of making a better schedule. 20:28:21 is this thing on? *whack whack* 20:28:29 (I think we need to do a better job of the Ambassadors thing, but that's a later topic.) 20:28:40 themayor: *feeedback squeeeeeeal* 20:28:45 One of the things we talked about was the need to provide better out-reaching information 20:28:50 "Essentially, the Fedora Marketing team ensures that people in Fedora can consistently explain to everyone what Fedora is and why they should care!" 20:28:56 Right. 20:28:59 * mchua sits back and listens to stickster 20:29:31 I've said it before, and I'll say it again -- the focus of the Marketing group must be reaching outside the Fedora community to deliver and spread important messages about what we do, and how and why we do it 20:29:31 out-reaching information? 20:29:43 Sorry, *outward* reaching 20:29:48 stickster - we've had this conversation at least twice before i swear 20:30:04 and i've argued that fi/news.fp.o/foobar is the way to do it 20:30:12 ? 20:30:13 JonRob: And I'm not disputing that. 20:30:30 * mchua thinks FI/news.fp.o is a *crucial* way to do that. 20:30:59 i think we need to also always keep in mind, its not only outward facing 20:30:59 * stickster pointing out that the schedule items we have for release are trying to support that goal, and where we see gaps or cruft, we should make appropriate changees. 20:31:04 we need to strive for outward facing 20:31:27 for some portion of that is going to need to be inward facing, both inward to fedora, and inward to red hat 20:31:30 FI is not the only way we'll do that, but perhaps a huge portion of our "deliverables" - if not all - should ultimately be published there. (Trying out that idea for size, not sure if it's the right one yet.) 20:32:10 right yes agreed... sorry sometimes i get alittle frustrated the amount we retread the same ground, and often don't seem to progress, just go round in circles 20:32:12 mchua: is the plan for FI still calling for it to be a journal format? 20:32:40 JonRob: crap i totally forgot to mention you in my email for some reason 20:32:52 i will update my blog to reflect it 20:33:01 anyway, back to the topic 20:33:06 FI has the potential to take on whatever format we determine is best 20:33:07 themayor: it's no problem!! 20:33:18 just hope you enjoy whatever you end up doing :) 20:33:22 Journal, timed rotation, whatever. 20:33:25 JonRob: Yeah, I appreciate you being so patient as the newbies like me rediscover what you've known all along. :) 20:33:33 JonRob: how can we get out of that circle? 20:33:33 okay so at what point do we move past potential and start making solid decision as to format? 20:33:45 isnt it the sooner the better? 20:33:48 themayor: yes 20:34:30 themayor: afaik, we've got the meeting with News, and then we should just start pumping out stuff on whatever schedule's determined at that meeting with news. 20:34:45 if it's the wrong content, or the wrong format,or the wrong schedule, we'll realize it within a week or two, and change. 20:35:01 okay, sounds good, but also... 20:35:10 mchua: remember the meeting we had in westford 20:35:56 we had solid reasons for liking that journal format, and from experience, i think thats what will ultimately be most successful based on past experimentation and assessment 20:36:26 themayor: yep, but nobody else here other than you and me and mizmo recall that conversation, so it's going to take a little time (not much, but nonzero) to get everyone on the same bus 20:36:29 i think short release cycle news, plus longer release cycle journal format stuff would be the best possible balance 20:36:58 themayor: if you want to be there for the decision-making conversation with News, I'm pretty sure that can be arranged :) 20:37:21 when is that? i would love to be there 20:37:34 themayor: needs to be arranged since i'm going on holiday! 20:37:40 and pascal is just back from holiday 20:37:45 will be fwding info to the list later 20:37:49 As long as those decisions are being made openly and transparently, I'm sure we'll arrive at the right content model/schedulel 20:37:52 themayor: It isn't scheduled yet - stickster is on it right now - so you and stickster and pascal need to pick a time. 20:37:52 *schedule 20:37:52 * mchua nods 20:37:55 also, mchua why dont we get people up to speed on that conversation now, because we had solid logic that day and i think it was the best plan we conceived 20:38:07 themayor: already sent my notes to the list, and posted them to the [[Fedora Insight]] page. 20:38:21 themayor: Let's make sure that we are covering mchua's stated agenda for the meeting. 20:38:25 stickster: i agree, but isnt it better not to walk into it blind in one eye? 20:38:33 yes, sorry 20:38:35 back to the agenda 20:38:38 themayor: if you don't mind continuing the Fedora Insight conversation on-list later today, we can move it there 20:38:44 agenda-ize mchua 20:38:51 stickster has focus-magic today! 20:39:01 Ok, so we're still on 3. Make sure that the F12 schedule we have is the one we actually want to have. What do we want Marketing to be and do - and what can we do towards that for this release? Revise our plan, if needed. 20:39:19 (#4 is just "make sure the list of groups we need to coordinate our schedule with is actually complete," and should take all of 30 seconds, so we have time.) 20:39:34 I think there's broad consensus for what we want to be and do. The schedule is really where we want to focus, I think. 20:39:41 were links posted to current schedule above? 20:39:41 * mchua breathes for a second. 20:39:44 themayor: yep. 20:39:50 https://fedoraproject.org/wiki/Marketing_F12_schedule 20:40:03 is updated as of stickster + poelcat + me talking yesterday 20:40:08 at that meeting with gobby. 20:40:15 that was mentioned on the mailing list. 20:40:21 mchua: One thing I see on that schedule that could use a massage is the mention of a "preview" phase that doesn't really exist anymore 20:40:26 um. The F12 marketing scheduling meeting. Yes. That was it. 20:40:42 * stickster hmms for a mo' 20:40:56 so Between Beta and Preview Release and Between Preview and Final 20:41:06 should actually be collapsed to "Between Beta and Final"? 20:41:26 mchua: Correct, there is no F12 Preview 20:41:49 (For the record, the assumption that I'm going with - my phrasing for everything I've heard from various sites and people on what marketing is and should be - is "The role of Marketing is to help other groups, projects, and people interface with those outside the Fedora community, and vice versa.") 20:42:03 (that's what is in the back of my head as I do all this stuff.) 20:42:06 we got rid of the preview 20:42:07 (It may not be correct.) 20:42:11 engineering decision 20:42:19 #action mchua to update f12 schedule to reflect the non-existence of a preview phase. 20:42:56 There are two corollaries (really, prerequisites, actually) to my current mental model of the role of marketing 20:43:10 Prerequisite: those (Fedora) groups are interfacing well between each other, within the Fedora community. (If this blocker isn't taken care of, it's our job to fix it. 20:43:28 Prerequisite: that we do everything we can to get resources and help from Red Hat (and other external groups, like other projects that are really good at marketing) in order to do our job. 20:44:00 The primary way we do this seems to be by acting as a materials producer. You say "make us an X!" and we make an X. We think folks need an X, we make an X. Values of X may include slogans, interviews (with the News folks), banners (with the Design folks), etc. 20:44:17 Another way we seem to do this is by serving as a receptionist. 20:45:01 When people (reporters, etc) come in and they want information, we can point them in the direction of these materials - and if they aren't enough, the right people - the right people being "probaby not us." 20:45:20 mchua: i think reporters generally go in the direction of rh for info on fedroa 20:45:25 making sure developers, ambassadors, testers, designers, infra folks, etc. doing good work get public credit for that work. 20:45:32 JonRob: hrm. 20:45:47 but i totally agree with all you've said here 20:46:20 JonRob: Clearly I need more of a history crash course so I don't get in the way of folks who Know Stuff with my "learning on the job" thing. 20:46:23 In a business, marketing keeps the rest of the business focused on the customer. In Fedora, we could think of the Marketing team as making sure we are always effectively growing and developing our potential contributor base through development of content, contacts, and presentation. 20:46:30 mchua: don't worry about it! 20:46:38 JonRob: Mind if I ping you about that when you get back 2 weeks from now? I'll spend those 2 weeks cramming archives. ;) 20:46:48 JonRob: I want to make sure we *don't* keep going around in those circles you mentioned. 20:47:12 you're welcome to... but don't worry about going aruond in circles for a little hwle 20:47:15 while* 20:47:39 * JonRob notes battery is about to run out 20:47:49 * mchua notes time is also about to run out 20:48:00 * mchua braindumps 20:48:08 things I think we need on the schedule 20:48:09 * Get More External Press 20:48:09 * Make Things for Other People to spread (Ambassadors) 20:48:09 * Make Things that Other People ask for (listen more!) 20:48:09 * Provide Consulting for things within Fedora that want Marketing Awesomeness 20:48:42 mchua: sounds good 20:48:49 I *love* the fact that you have that #3 bullet 20:49:16 And I think these broad goals are precisely the right things for us to shoot for 20:49:48 now how do we turn them into action items with deadlines? ;) 20:49:49 I think everything on the Marketing schedule supports those broad goals, while certainly leaving room for other new ideas to come in that aren't necessarily tied to the release. 20:50:15 stickster: big nod 20:50:18 * mchua nods 20:50:26 so maybe we don't need to worry about adding more milestones right now? 20:50:40 and when needs are obvious, we can add another one. 20:51:04 and when we try something not on the list and it goes well, we can say "well, we'll do that for all releases, then" and put it in the generic Fedora marketing time-map 20:51:24 mchua: Amen to that 20:51:26 ...although the last one might have an upcoming milestone ( Provide Consulting for things within Fedora that want Marketing Awesomeness) 20:51:41 * JonRob must run 20:51:44 (it was inspired by how Design does consulting for just about everyone else in Fedora, and how they're awesome at that) 20:51:48 batter < 10% 20:51:51 thanks, JonRob! 20:51:59 catch up with you all in 2 weeks 20:52:06 i'll prob check some e-mail in that time 20:52:09 have a great vacation, JonRob. thanks for everything. 20:52:13 cheers all 20:52:29 sdziallas and the Fedora Edu SIG sound like they're willing to be Marketing's first "consulting customers" 20:52:34 so that's something we should start doing on-list 20:52:54 * stickster +1 for on-list. 20:52:56 * mchua breathes a little, looks at clock, looks at agenda 20:53:04 w00t! 20:53:07 ...if we're not adding any more milestones here, that just leaves one thing 20:53:09 4. Make sure our plan is sane - make sure it syncs up with other groups we need to work with on specific points (Design, News, Docs, Ambassadors, Websites... who else?) 20:53:24 do we have folks here who are already delegates for coordinating schedules with any of those groups? 20:53:26 or who want to be? 20:53:40 mizmo seems like the shoe-in for Design 20:54:05 * mchua nods 20:54:10 News: pcalarco's already on deck 20:54:29 Docs: Sparks is as well 20:54:39 Websites: ricky 20:54:41 Ambassadors: ? 20:54:48 Ambassadors: Do we have a single contact here? Or would it make sense to ask FAmSCo about this? 20:54:54 * lcafiero sneaks in and sits in the back of the room 20:54:54 ooh, yeah. 20:55:00 Ambassadors: FAmSCo 20:55:03 lcafiero walked right into it 20:55:09 * stickster kids 20:55:12 * mchua grins 20:55:19 * lcafiero looks at his shoe -- so that's what that is. 20:55:29 Let me read up for a sec 20:55:58 * mchua will move this to the list, and get conversations with each of the people (or in the case of FAmSCo, groups) we've listed 20:56:08 to make sure the schedule is all happy-synced 20:56:24 coordinate with ambassadors? 20:56:45 #action mchua to make sure syncing with each of the mentioned groups - Design, News, Docs, Ambassadors, Websites - happens 20:56:51 (though I probably won't be the one having most of those conversations) 20:56:59 * ianweller fails and got highly distracted for the last 50 minutes. 20:57:06 lcafiero: yeah, we want to make sure our f12 schedule syncs up with yours 20:57:19 lcafiero: and that we listen to what ambassadors actually need and want 20:57:29 instead of walking in and dumping shiny things on your lap :) 20:57:50 Okay, I can do that. 20:58:22 lcafiero: thanks! we'll catch up outside of meeting, I reckon? (on public list- ambassadors and/or marketing?) 20:58:28 Although dumping things on our laps is okay, as long as they're shiny 20:58:36 * stickster looks at clock and is amazed yet again at how much we covered in a short time 20:58:41 lcafiero: Oh, they'll be shiny. :) 20:58:52 meeting ending! 20:58:55 any last notes? 20:58:59 ianweller: jetpacks! 20:59:05 i returned for that. lol 20:59:10 onwards in 5 20:59:13 ...4 20:59:14 * mchua dons jetpack 20:59:16 ...3 20:59:18 * mchua dons helmet 20:59:19 * ianweller puts on jetpack upside down 20:59:23 ...2 20:59:29 * mchua looks askance at ianweller, shrugs 20:59:32 ...1 20:59:37 * mchua blasts off 20:59:50 * mchua waits for ianweller .... 20:59:53 * ianweller stands on his head and blasts off 20:59:55 #endmeeting