20:49:43 <mchua> #startmeeting
20:49:43 <zodbot> Meeting started Tue Dec 22 20:49:43 2009 UTC.  The chair is mchua. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:49:43 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:49:47 <mchua> go zodbot go!
20:50:15 <mchua> Okay, this is going through the F13 schedule to get a sanity-check and revisions together for poelcat so he can keep us on track
20:50:22 <mchua> #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-marketing-tasks.html
20:50:26 <mchua> is our current gameplan
20:50:51 <mchua> rbergeron had some questions on that which I'm trying to find in my email archives (as I send the notes from the meeting we just finished to the list...)
20:51:03 <mchua> QUESTION: axe tasks 13 and 15?
20:55:01 * mchua back, done sending minutes to marketing list
20:55:55 <mchua> Ok, found Robyn's email, there are 3 questions
20:56:05 <mchua> 1. tasks 13 and 15 are to update / freeze the Fedora tour page. Since we're doing the one-page release notes in lieu of the Fedora tour page, should we remove those tasks from the schedule?
20:56:09 <mchua> 2. Should the one-page release notes draft / completion dates be rearranged to be more in line with when the Fedora tour pages were done, or are we comfortable with those dates and how they fall into the grander scheme of things?
20:56:13 <mchua> 3. Shall we put a note on https://fedoraproject.org/wiki/Tours reflecting that we now do one-pg release notes instead of Tours, so that anyone looking for a Tour isn't wondering why the heck we didn't have one for F12 (or F13, and so forth)?
20:56:40 <mchua> Before I go into them, I should note a few things about our schedule this release cycle
20:57:14 <mchua> (I'm basically doing the equivalent of talking out loud to myself into a tape recorder right now... totally feel free to interrupt me or keep talking about what you were working on, folks, don't let me take over the channel ;)
20:57:23 <mchua> #topic How the F13 marketing schedule works
20:57:57 <mchua> We're working in 3 stages, roughly corresponding to (the time leading up to) Alpha, (the time leading up to) Beta, and (the time leading up to) GA day.
20:58:18 <mchua> Alpha: anything before March 2nd.
20:58:36 <mchua> The focus here is on infrastructure - tools and resources that will make it easier for us to produce our release deliverables.
20:59:02 <mchua> #info Alpha (pre-March-2nd): focus on infrastructure
20:59:56 <mchua> Example tasks would be summarizing our F12 activities and looking back on a "so how did we do" thing, cleaning up and updating our wiki page, reviewing our Join process and new-member queue, making the F13 schedule
21:00:24 <mchua> planning for the FAD, writing SOPs, and getting tools (limesurvey, zikula/Insight, fedora-tour, etc) up and running in production.
21:01:15 <mchua> #info example: F12 retrospective, F13 schedule, FAD planning, join process, SOPs, software tools (limesurvey, zikula, fedora-tour)
21:01:35 <mchua> Beta: between March 2nd and April 6
21:01:51 <mchua> ...april 6? wow.
21:01:53 * mchua checks again
21:01:59 <mchua> Yep. Just barely over a month.
21:02:00 <mchua> Wow.
21:02:14 <mchua> Okay. Anyway, that's our time to focus on deliverables, and *just* on deliverables.
21:02:17 <mchua> One deliverable per week.
21:02:25 <mchua> Our deliverables for this release:
21:02:27 <mchua> * talking points
21:02:28 <mchua> * slogan
21:02:30 <mchua> * feature profiles
21:02:48 <mchua> * one-page release notes
21:03:00 <mchua> * screeenshots library
21:03:38 <mchua> and then something that's not a deliverable per se, but also on our to-do list for that portion of the cycle
21:03:45 <mchua> which is briefing ambassadors / the press.
21:05:26 <mchua> We *may* want to put in a press release item there, but I'm leaving that out for the time being because I don't know what things will look like at that point, and Kara/Paul/Max have usually stepped in around then to work on PR stuff
21:06:02 <mchua> I'd very much like us to write the press release, and hold a press conference (that's something that came up on-list - I forgot who proposed that, perhaps asamaras?)
21:06:10 <mchua> but the deliverables are the "if we don't do them, they will not get done" things
21:06:50 <mchua> These deliverables will be published on Fedora Insight as they're made, or put into the queue for later publishing.
21:07:11 <mchua> Marketing research will almost certainly be running in parallel with that.
21:07:36 <mchua> And the FAD will happen during this timeframe, during which we'll be working on a project that *isn't* a release deliverable (while work on release deliverables continues ;)
21:08:28 <mchua> Also, the Desktop team will be joining us for this time period - we'll have at least one Desktop delegate with us at the beginning of our meeting/sprints to fill us in on cool stuff to highlight, give feedback, suggestions, help out, etc. and otherwise help us be closer to the developers this cycle.
21:08:36 <mchua> Many thanks to Jon McCann for setting that up.
21:08:45 <mchua> But to summarize:
21:09:01 <mchua> #info Beta (March 3rd - April 6th): focus on deliverables
21:09:18 <mchua> #info talking points, slogan, feature profiles, one-page release notes, screenshots library, briefing Ambassadors
21:10:18 <mchua> #info other activities: FAD happens during this time, marketing research ongoing, Fedora Insight publishing materials, Desktop team liasons, gear up for PR (press release, press conference) if we have bandwidth.
21:10:25 <mchua> Finally, there's the time leading up to GA day.
21:10:32 <mchua> That's May 11th this year.
21:11:41 <mchua> Since we'll be loading our deliverable work between Alpha and Beta, we should be able to breathe easy during this time.
21:11:59 <mchua> The only thing we'll need to update, deliverables-wise, is the screenshots for the one-page release notes, since those can't be taken until right before release.
21:12:04 <mchua> But that's quick and fun.
21:12:27 <mchua> What this means is that we can concentrate on 2 things - the first, and obvious one, is PR.
21:12:49 <mchua> Getting stuff out to journalists, monitoring the press, holding a press conference (as mentioned before - the Beta timeperiod would be more for planning for that)
21:12:57 <mchua> more press releases, that kind of thing.
21:13:31 <mchua> But I'd like to also be able to do something we haven't really done before - which is to have the Marketing team go into outreach mode, because we'll have capacity to help out other teams.
21:13:36 <mchua> Especially on two things:
21:13:47 <mchua> 1) help other teams publicize and make deliverables for the stuff they're doing
21:14:10 <mchua> (for instance, if the KDE SIG wants one-page release notes, we should be able to use our F13 one-page release notes and the SOP as examples to help them make their own.)
21:14:59 <mchua> (or if Infrastructure wants to present its setup at a conference that's coming up, we can help them figure out press targets and talking points, again using our own work as an example.)
21:15:15 <mchua> Basically, being a Marketing center of excellence for Fedora that can serve other teams, and also serve as an example to other projects.
21:15:41 <mchua> (Who are already starting to look at what we're doing - one-page release notes from F12 being a big example, Fedora Insight being another thing that other projects are watching us on.)
21:16:04 <mchua> The second one is a little more unconventional, and I'm not sure how to phrase it yet.
21:16:28 <mchua> 2) help other teams with capacity-building
21:16:33 * mchua takes a brief typing break
21:18:17 <hiemanshu> wow all i see is mchua, mchua you could type it all alone and email it
21:18:51 <PhrkOnLsh> lol
21:18:59 <PhrkOnLsh> rbergeron took off I think, hiemanshu
21:19:21 <PhrkOnLsh> mchua: I will probably end up being the one to write the KDE release notes
21:26:01 * mchua back with happier hands.
21:26:18 <mchua> hiemanshu: I'm typing this here in case rbergeron gets back, and also to encourage people to interrupt me. ;)
21:26:27 <mchua> I'm almost done, likely <10m left.
21:26:32 <mchua> Where were were?
21:26:40 <mchua> 2) help other teams with capacity building.
21:27:00 <mchua> One of the big opportunities we miss in Fedora is the chance to help new contributors get started.
21:27:07 <mchua> Why? Because new contributors want to come when it's exciting.
21:27:14 <mchua> And when it's exciting is when we're really, really busy.
21:27:19 <mchua> In other words, right around a release.
21:28:13 <mchua> I'm willing to bet that if we were more conscious of, and better about, reaching out via the press we're already doing, to extend a hand to help new contributors get started,
21:28:18 <mchua> we'd have a lot more for the next release cycle.
21:28:36 <mchua> Ambassadors do this at Events already, but they're usually *totally* swamped.
21:28:57 <mchua> I remember seeing a small flood of "hi, I want to join Infrastructure!" emails around the F12 release, when things were getting frantic.
21:29:11 <mchua> Generally, new people come in when the teams they're trying to join don't have the bandwidth to on-board them very much.
21:29:34 <mchua> And when you're new, you want to know, *right away,* how to get started helping - you want immediate feedback that this is a community you'd like to contribute to and stay in.
21:30:15 <mchua> So I'd like Marketing to be able to work with each team - and each subgroup and SIG, if possible - and any other group that's interested - between Beta and GA on this.
21:30:50 <mchua> Working on their Join process, publicizing (on Fedora Insight, etc) good starter opportunities for new contributors to help with
21:31:13 <mchua> hopefully we'd do this in conjunction with Classroom, so they could organize some training for each team, and we could get new folks and point them there.
21:31:45 <mchua> This comes directly from something that's been discussed a bit before, which is the idea of Fedora's "revenue" equivalent being contributions.
21:32:08 <mchua> Most Marketing departments exist to maximize monetary revenue; our job is to increase our currency, which is contributions.
21:32:35 <mchua> Anyway. So, overview of that last part:
21:33:24 <mchua> # GA (April 7th - May 11th): focus on PR, center-of-excellence for increasing contributions
21:33:32 <mchua> argh
21:33:38 <mchua> #info GA (April 7th - May 11th): focus on PR, center-of-excellence for increasing contributions
21:34:22 <mchua> #info examples: interfacing with press, press conference, helping other teams make their marketing deliverables, partnering with Classroom to make on-boarding training opportunities for other teams, Join process consulting, getting-started marketing via Insight for other teams, etc
21:34:55 <mchua> That's pretty vague and fuzzy right now, but we'll figure it out when we get there, and I wanted to give a heads-up on where we're looking for that far horizon.
21:35:08 <mchua> It means we've got to be on top of our game, because we need to know our stuff before we can teach it to others.
21:35:16 <mchua> Anyway. That having been said.
21:35:20 <mchua> #topic F13 schedule questions
21:35:50 <mchua> Let's look again at
21:35:54 <mchua> #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-marketing-tasks.html
21:36:40 <mchua> and make sure we get rbergeron's 3 questions answered
21:36:48 <mchua> 1. tasks 13 and 15 are to update / freeze the Fedora tour page. Since we're doing the one-page release notes in lieu of the Fedora tour page, should we remove those tasks from the schedule?
21:36:52 <mchua> 2. Should the one-page release notes draft / completion dates be rearranged to be more in line with when the Fedora tour pages were done, or are we comfortable with those dates and how they fall into the grander scheme of things?
21:36:56 <mchua> 3. Shall we put a note on https://fedoraproject.org/wiki/Tours reflecting that we now do one-pg release notes instead of Tours, so that anyone looking for a Tour isn't wondering why the heck we didn't have one for F12 (or F13, and so forth)?
21:37:56 <mchua> 1-6 look good; we can frontload the talking points and slogan as soon as feature freeze is in place. Those won't take very much of our time at all.
21:38:07 <mchua> er, that's 1-5
21:38:27 <mchua> 6 should start a day later, on Alpha day (also our meeting day)
21:39:46 <mchua> wait, sorry. that's "end a week later"
21:40:03 <mchua> tasks running full weeks, using marketing meeting times during that period to sprint on deliverables
21:40:17 <mchua> #action #6 should end a week later, on 4/05
21:41:40 <mchua> ...wait, no it shouldn't, because that's when the one-page release notes is going.
21:41:51 <mchua> Mrgh, this schedule format is hard to read.
21:42:15 <mchua> #action actually, #6 is fine the way it is. nm.
21:43:01 <mchua> 13 and 15 refer to the deprecated fedora tour page (we're going to have a real fedora-tour this time ;) so rbergeron is totally right, they should be axed.
21:43:23 <mchua> #action tasks 13 and 15 refer to a deprecated deliverable we don't do any more (one-page release notes have replaced the tour) and should be deleted.
21:44:05 <mchua> however, we need to add a "brief ambassadors" item for 3/30-4/6
21:44:13 <mchua> #action add a "brief ambassadors" item for 3/30-4/6
21:45:19 <mchua> to answer rbergeron's 2nd question, the one-page release note dates are good as they are - we'll get pretty much everything done right before beta, and then if you look at tasks 16 and 18 right now that's where the final screenshots/fine-tuning for the diff between beta and final release will be applied.
21:45:39 <mchua> as opposed to our former game plan which was "AHH! DO EVERYTHING RIGHT BEFORE GA DAY!!! AAAHHH!"
21:46:08 <mchua> finally, third question: yes, we should update the Tours wiki page to note that we're replacing them with one-pagers.
21:46:25 <mchua> #action when updating SOPs, note on Tours page that Tours has been replaced by one-page release notes
21:46:44 <mchua> And that's it!
21:47:03 <mchua> I'll try to turn these notes into a blog post and a mailing list update, and use the action items to ask poelcat to update our schedule.
21:47:07 * mchua closes logs
21:47:10 <mchua> #endmeeting