I've been having LAPTOP FAIL issues, so here's a low-tech version until
such time as my new netbook is running Fedora and I can sit down to type
these into notes*: http://mchua.fedorapeople.org/fi-whiteboard.jpg
Everything on this image will be captured on the [[Fedora Insight]] wiki
page, and I'll ping this list when that's done, so if you don't look
now, you won't be missing anything. Just wanted to give people a chance
to see what was going on, because Transparency Is Good.
*instead of stacking books behind my monitor's hinge to keep my hardware
from falling physically apart, say.
Looks like we've got ourselves a discussion topic. ;)
-------- Original Message --------
Subject: Fedora 12 Alpha Release Readiness Meeting :: Wednesday, August
12, 2009 @ 17:00 UTC
Date: Thu, 06 Aug 2009 16:28:07 -0700
From: John Poelstra <poelstra(a)redhat.com>
To: logistics(a)lists.fedoraproject.org, Fedora Translation Project
When: 2009-08-12 at 17:00 UTC (1 PM EDT/10 AM PDT)
Next Wednesday we are scheduled to have the Release Readiness meeting
for the Fedora 12 Alpha. I'm hoping representatives from each of the
teams will be able to attend. Please discuss with your teams to see if
there are any issues they would like to bring forward. This cross team
meeting is held to coordinate and discuss release day issues in real
time and to make sure we are ready for a smooth release day.
The following list shows the people that represented these teams in past
releases. If you cannot attend or no longer wish to represent your team
please coordinate and alternate and let me know.
>> I still need to know who is representing the translation team <<
Ambassadors -- David Nalley
Design -- Máirín Duffy
Documentation -- Eric Christensen
FESCo -- Jon Stanley
Fedora Engineering Manager -- Tom "Spot" Callaway
Fedora Project Leader -- Paul Frields
Infrastructure -- Mike McGrath
Marketing -- Mel Chua
Quality -- James Laska
Release Engineering -- Jesse Keating
Translation -- ??
Websites -- Ricky Zhou
I will send conference call information privately next week. A recap of
this meeting will appear on this list.
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
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.
...after making sure no schedule conflicts with other teams ensued. Yay!
Schedule attached, and also available at
https://fedoraproject.org/wiki/Marketing_F12_schedule in extraordinarily
ugly formatting. (John, is there a better way to format this for you? I
followed the Gobby format you wanted, but the items aren't listed in
strictly chronological order.)
Once this schedule is posted on
Extraordinarily Ugly Formatting will be replaced by a much nicer-looking
Of course, the real question (now that we have a schedule with
milestones and all) is how on-track are we for hitting them? Stay tuned,
because the answer is coming... *dun-dun-DUNN* at the start of the next
Marketing meeting. (In other words, I get to go and calculate that