On Tue, Jul 26, 2011 at 12:05:27PM +0100, Mark McLoughlin wrote:
Now that we're getting the plans for the next release in good shape, I
think it'd be a good idea for think hard about which of the features
we're adding is going to be the most interesting to users.
I think each of those features should have an owner who understands the
big picture and how all the pieces of the feature fits together. The
feature owner should understand what makes the feature interesting and
how to quickly show off the best bits. The owner should know what
remains to be implemented and which the tasks absolutely must be
finished before releasing.
I'm basically suggesting something similar to the Fedora feature
process, but without any bureaucracy. All we want to get out of this is
a sharper focus on the things that matter to users.
So, here's a template for what I have in mind:
And here's an attempt to describe Audrey in this format:
This is excellent, thanks Mark. It also lines up nicely with the
Redmine planning we're doing right now. Those of you who have chosen a
feature to own, could you also create a wiki page to go along with it
along these lines?
One question though: Which wiki are we using, this one or the Redmine
one? Or are they the same? And, can we stop having two wikis ASAP?
== Hugh Brock, hbrock(a)redhat.com ==
== Engineering Manager, Cloud BU ==
== Aeolus Project: Manage virtual infrastructure across clouds. ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."