Attached.
This is a draft of a skeleton schedule with all the milestones we'll have to hit every release, to be customized at the start of each cycle to create that cycle's particular schedule. (Because stuff like "alpha readiness meeting" will be repeated every cycle, stuff like "get Fedora Insight up and running" won't.)
Emphasis on the word *draft.* Are there any other tasks that *must* be completed every cycle? Tasks listed here that don't need to be done every cycle?
John, the formatting is pretty awful here - it might be easier to go through and change the dates from things like "beta readiness mtg+1wk" to things like "week 1 - week 3"... we can do that on gobby if you'd like.
F12 schedule coming on Monday.
--Mel
On Fri, Jul 31, 2009 at 04:11:15AM -0400, Mel Chua wrote:
Attached.
This is a draft of a skeleton schedule with all the milestones we'll have to hit every release, to be customized at the start of each cycle to create that cycle's particular schedule. (Because stuff like "alpha readiness meeting" will be repeated every cycle, stuff like "get Fedora Insight up and running" won't.)
Emphasis on the word *draft.* Are there any other tasks that *must* be completed every cycle? Tasks listed here that don't need to be done every cycle?
John, the formatting is pretty awful here - it might be easier to go through and change the dates from things like "beta readiness mtg+1wk" to things like "week 1 - week 3"... we can do that on gobby if you'd like.
F12 schedule coming on Monday.
Mel, I'd probably put the Red Hat Brand coordination meeting earlier, something like Alpha availability +1 week. They need significant headroom in their schedule for things like video production.
Paul
Cleanup the wiki from the obsolete marketing cycles start of cycle start of cycle+1wk
Cycle the wiki pages to the new release start of cycle start of cycle+1wk
Alpha Readiness Meeting mtgdate mtgdate
List potential talking points and feature profiles Feature freeze Feature freeze+1wk
Decide format (podcast, video, text, etc) and provider (Docs or News) for each talking point and feature profile Feature freeze+2wk Feature freeze+3wk
In-depth feature profiles from 0% to 75% completion Beta availability-6wks Beta availability-2wks
Contact News beats people about topics/features we cover as soon as feature profiles are 75% complete that date +1wk
Drafts of talking points completed beta availabiity-3wks Beta availability-2wks
Beta Readiness Meeting mtgdate mtgdate
Open the call for release slogan suggestions beta readiness mtg-1wk same
Release slogan selection beta readiness mtg+1wk same
Finish the in-depth feature profiles beta-2wks beta
Meet with RH Brand to discuss additional/supplemental RH-provided marketing materials that may be coming out (video, press blog, etc) beta beta+1wk
Brief FAMSCo on talking points and propagate link to Ambassadors beta-2wks beta-1wk
Update the press kits beta-1wk general avail-6wks
Final release slogan is ready for websites/design beta readiness mtg - 2wks same
Update and freeze the screenshots page beta availability +1wk Update and freeze the Fedora tour page beta availability +1wk
Brief News Distribution Network on tour page and other marketing materials created to date beta-1wk beta+1wk
Monitor community news sites and provide corrections and additional information as needed beta-4wk gen availability + 4wk
Final Readiness meeting mtgdate mtgdate
GA Day social media explosion sprint date date
-- Fedora-marketing-list mailing list Fedora-marketing-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list
Mel, I'd probably put the Red Hat Brand coordination meeting earlier, something like Alpha availability +1 week. They need significant headroom in their schedule for things like video production.
Paul
Thanks, Paul (and sorry for the belated answer) - edited. Here's the final generic one - final in the sense that we won't worry about this until the start of F13, since this will certainly be tweaked at the beginning of the next round.
https://fedoraproject.org/wiki/Marketing/Schedule/Generic
Incidentally, we need someone to convert this file to taskjuggler format - see https://fedorahosted.org/marketing-team/ticket/1. (yes, we're using a ticketing system now. You'll see more of this as tasks trickle in...)
--Mel
PS: Yeah, I know, I should have made the first ticket "not everybody contributes to Fedora" or something like that.
PPS: Note the level of detail at which I'm trying to write tickets. I went a little overboard; they don't all have to be this detailed. However, a relative newcomer should be able to read a ticket and immediately know how to start - at the very least, the ticket should point to instructions on how to find someone on IRC to ask about how to get started. This means using URLs instead of vague references ("that site thing") and putting in clear "here's how you tell when you are done" criteria. This will also help us remember what the heck a ticket referred to several years down the line.
I'll repeat all this in a "now we have Trac!" email (which will point to a wiki page asking people to do this sort of thing), but as a former QA person, I couldn't resist an opportunity to advocate for good ticket-writing skills. (Further suggestions welcome.)
On Tue, Aug 04, 2009 at 12:56:51AM -0400, Mel Chua wrote:
Mel, I'd probably put the Red Hat Brand coordination meeting earlier, something like Alpha availability +1 week. They need significant headroom in their schedule for things like video production.
Paul
Thanks, Paul (and sorry for the belated answer) - edited. Here's the final generic one - final in the sense that we won't worry about this until the start of F13, since this will certainly be tweaked at the beginning of the next round.
https://fedoraproject.org/wiki/Marketing/Schedule/Generic
Incidentally, we need someone to convert this file to taskjuggler format
- see https://fedorahosted.org/marketing-team/ticket/1. (yes, we're using
a ticketing system now. You'll see more of this as tasks trickle in...)
I'll ask John about this -- in the past I believe he's taken care of this for teams.
PS: Yeah, I know, I should have made the first ticket "not everybody contributes to Fedora" or something like that.
"Some people think Fedora is just a kind of hat." ;-)
PPS: Note the level of detail at which I'm trying to write tickets. I went a little overboard; they don't all have to be this detailed. However, a relative newcomer should be able to read a ticket and immediately know how to start - at the very least, the ticket should point to instructions on how to find someone on IRC to ask about how to get started. This means using URLs instead of vague references ("that site thing") and putting in clear "here's how you tell when you are done" criteria. This will also help us remember what the heck a ticket referred to several years down the line.
I'll repeat all this in a "now we have Trac!" email (which will point to a wiki page asking people to do this sort of thing), but as a former QA person, I couldn't resist an opportunity to advocate for good ticket-writing skills. (Further suggestions welcome.)
This is spot-on in my opinion. Actionable tickets are self-documenting and make collaboration and contribution a snap. Nice work.
marketing@lists.fedoraproject.org