On 07/26/2011 07:05 AM, 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:
Hm... and no work about the the security of the communication between
the instance and config server and how that would work. I expected it to
at least be covered in the future feature section.
aeolus-devel mailing list
Sr. Engineering Manager IPA project,
Red Hat Inc.
Looking to carve out IT costs?