On Wed, Feb 18, 2009 at 06:18:02PM -0500, Jack Aboutboul wrote:
The proposed solution:
A better, calendar based, workflow! The reality is that our workflow is
cyclical in nature, it is based on a release schedule and we have mostly
the same, or a majority of similar tasks/milestones that need to be done
for each release. If we shift our current workflow and task tracking to
a similar scheme, it may be easier for us to stay on top of things and
operate more efficiently. It also allows us to have clear "due dates"
for each item, and have it clearly marked with an owner. Right off the
bat I see us knocking out two of our major issues. Plus, clarity when it
comes to responsibility and accountability will facilitate better
communications amongst ourselves. Also, I propose that part of this
schedule system includes 2-3 meetings with members of the other relevant
projects, and this way, anything that hinges on us for them, or them on
us, will be clearly defined, we achieve mutual understanding, and can
delegate those tasks to people in Marketing.
So for example, we start out at T-Minus 6 weeks from the alpha, have
everything necessary from that until the alpha on a grid marked with a
task, date, owner. Same for Beta, same for GA. A Good example can be
found at John Poelstra's Schedule Pages found here
http://poelstra.fedorapeople.org/schedules/f-11/ .
Also, this should all be kept under
https://fedoraproject.org/wiki/Marketing/Schedule with trailing
/releasever and an anchor from that main page to whatever the current
release is.
+1 to Karsten's suggestion. Make sure we're following the wiki
guidelines for pages so that when someone searches, they get what they
need to participate.
As for the overall solution, IMHO the schedule for release-based tasks
does need to be coordinated with the other teams on the release
calendar, so +1 to that.
I thought this was something the group had more or less agreed at a
previous meeting, but I could be wrong. If we do have consensus, then
we need to see real dates pronto and start dealing with concrete "to
do" items. Maybe set a time limit on discussion of the plan in
today's meeting, and then move on to turning it into action items that
can be assigned and achieved.
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug