+1

stéphane ducasse wrote:
> Doing that with good software engineering practices
>     - Tests
>     - Test Server
>     - Building scripts
> 

Does this include 'management' practices? Having a backlog of features, 
force ranked in terms of priority, with estimates and people only 
working on features slated for the current iteration, is a very good way 
of breaking out of paralysis in commercial software development. Is 
there anything analogous you can do in a community driven development?

Cheers

Daniel