Brainstorming tasks for next sprint

Jason Guiditta jguiditt at redhat.com
Tue Feb 14 15:50:22 UTC 2012


On 14/02/12 10:36 -0500, Matt Wagner wrote:
>On Tue, Feb 14, 2012 at 10:21:03AM -0500, Jason Guiditta wrote:
>> On 13/02/12 19:33 -0500, Wesley Hayutin wrote:
>> >
>> >I like your ideas, wanted to throw another out there..
>> >
>> >1. A scripted development environment.
>> >
>> >Why is it needed?? We have a complex application that pulls in resources from several different sources.
>> >It would be cool IMHO if we had some certainty we're all looking at the same thing.  Should help with our collaboration, and with
>> >automated unit/cuke tests.
>> >
>> >Right now everything is very stable, but think back to a year ago when rubygem hell rule the earth.
>> >It would also be cool if we didn't have to install the product first as well, but not sure if that's possible.
>> >
>> >Thanks..
>> >
>>
>> I have been thinking about something (I think) along similar lines.  I
>> have some beginnings of this in conductor/util (build-all and a git
>> pull script that is not yet pushed), and martyn had a 'get all aeolus
>> repos' script in his own repo, maybe he can respond here with the link
>> again, so we have it together.  My thought was to split out util into
>> its own repo, and have it contain developer tooling, possibly in the
>> form of a gem and optional rpm (that part highly tbd).  A developer
>> wanting to work on the project would clone that single repo.
>
>I think this would be great.
>
>I also have a few rake tasks I've cobbled together that might make sense
>there: https://gist.github.com/1827545
>
Good stuff.  Funny enough, I used the same namespace for my (not yet
sent) bundler/platform dev patches.  I will note that these are kind
of conductor specific, as are mine, so they may need to just end up
there.

-j



More information about the aeolus-devel mailing list