I've updated the F12 schedule according to the meeting
that Paul, John, and myself had today.
We've got some dates and such to coordinate with various teams (cc'd
here) before Monday in order to make sure our calendars sync up. One of
the things we'll be talking about at the Marketing meeting tomorrow
(https://fedoraproject.org/wiki/Marketing_meetings) is how to make sure
that each Marketing + OtherTeam coordination happens this week - some of
these connections already have delegates, others have people who
probably should be, others are wide open.
The notes below are very, *very* much drafts, and only starting points!
It's also entirely possible that I've put *too* much in the notes below
(that figuring out something shouldn't be Marketing's job, or its
focus). Patches welcome.
Design: We should make sure we get you a release slogan in time, and
give fast enough feedback/final-slogan turnaround based on your designs
that you can make release buttons/banners with time to spare. Also need
to see what sort of work we need to coordinate in order to make spiffy
Docs: We should commit to those 1-page shiny release notes you wanted,
and find other good points during the cycle to check in with each other.
We also need to talk (possibly with News) on who'd like to do what
portions of talking points and in-depth feature profiles. (How can we
market our documentation as awesome, too?)
Ambassadors: We need to schedule a briefing for you folks to happen once
the talking points are ready - but most importantly, we need to learn
how we can listen to you better so that we can make the things you
actually want and *need* to spread the word on the ground. What can we do?
Websites: We should talk - potentially with Design - about how we're
going to coordinate various webpage redesigns and revisions, and how our
respective roles complement each other.
News: We also need to talk (possibly with Docs) on who'd like to do what
portions of talking points and in-depth feature profiles. We should also
figure out what's going on with News and Marketing and Fedora Insight,
so we can schedule in coordination times with other teams if needed.
As I dug into John Poelstra's schedule in more detail, I noticed a few
issues that I hadn't noticed in earlier reviews. Specifically, very long
times on some short tasks with short times on some more difficult tasks, and
tasks out of order.
Since I don't have a really good feel for the guides, I put together what I
thought was a more workable schedule for release notes only. Eric was going
to look at guides. My strawman is at:
I fixed major milestones to the same dates that John had so hopefully we
don't affect other teams. However, I did put a couple of L10N tasks on the
list since they are tied closely to us. I have not, however, had any
discussion with L10N as to whether these times make any sense at all to
John suggested we get together in a Gobby/Talk meeting to get this schedule
into sync with his. I think we need to get the guides schedule integrated
with this and include a representative from L10N in that meeting.
Because of the new definition of alpha and beta, our schedule looks a lot
different than earlier releases. Specifically, since alpha should be
"feature complete", we should have almost everything we need for release
notes by alpha. That means the bulk of our work is between alpha and beta.
However, since Beta should include more or less complete release notes, L10N
will need time to translate them. That pushes Docs work forward some,
meaning we will have a real scramble right around alpha, and L10N will have
a pile of work just before beta. The upside is that the work before GA
should be a little less onerous, and there should be little left to
If we can make our plan of a table for all changes and prose only for
significant effort required to convert plus highlighting high-profile
features, there should be a lot less prose to write (and translate) than
previous releases. We will, however, need some pretty aggressive wiki
gardening to allow us to convert to XML quickly.
I would like everyone to take a really close look at this, and comment on it
on this list. I think I have the major tasks identified, but it is always
good to have more input.