task #1112 - aeolus-configure documentation

[Justin Clift]

On 19/04/2011, at 5:03 AM, Mo Morsi wrote:
> <configure.txt>_______________________________________________

Hmmm, can I grab the first few intro paragraphs from that, to use
in a "What is Aeolus-configure?" page on the new website?

Was trying to think of what to write, so "good timing". :)

Regards and best wishes,

Justin Clift

--
Aeolus Community Manager
http://www.aeolusproject.org

[Mo Morsi]

On 04/21/2011 12:37 AM, Justin Clift wrote:
> On 19/04/2011, at 5:03 AM, Mo Morsi wrote:
> > <configure.txt>_______________________________________________
>
> Hmmm, can I grab the first few intro paragraphs from that, to use
> in a "What is Aeolus-configure?" page on the new website?
>
> Was trying to think of what to write, so "good timing". :)
>
> Regards and best wishes,
>
> Justin Clift
>
> --
> Aeolus Community Manager
> http://www.aeolusproject.org

Sure thing, feel free to grab as much as you need from it.

-Mo

[Mike Orazi]

On 04/18/2011 03:03 PM, Mo Morsi wrote:
> aeolus-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/aeolus-devel

Mo,

Thanks for taking a run at this.  I like the document and I think it
calls out more than a few areas where there is some internal debate 
(does package installation fall inside or outside of -configure, how
much data can/should be pre-seeded, etc).  I'm cc:ing Andy & Hugh to see 
if we get some clarification on expectations of the tooling as well as 
get some sense of prioritization of the features outlined.

My suspicion is that it will be difficult for people to collaborate very 
extensively on this.  I'd like to suggest that after a round of comments 
(or at the end of the current sprint) this should land on a wiki 
somewhere for further discussion.  Additionally, I hope that we can use 
this document as a base to help frame the creation of user stories for 
the backlog so we can get down to doing the work.

Thanks,
Mike