On 7/3/06, Jim Marino <[EMAIL PROTECTED]> wrote:
...and involve a lot less "upfront planning"? In other words, people work on what interests them and the community cuts a release when it decides a useful level of new functionality has been reached.
Can you provide pointers to any other Apache projects that work like this? I've never seen any other project of significant size, open source or otherwise, work like that. There's three main problems I see with the 'do whatever you like' approach. With no clear goals, direction, or coordination we wont end up with anything very useful that fits together and works in an elegant and seamless way. No one will do the boring work - documentation, testing, uninteresting bugs in JIRAs, etc. And it will be hard to grow the community. Over the past months I've been trying to get new people to come participate in Tuscany and they all complain about no roadmap of what we trying to achieve, no wish list of wanted function, and no plan of whats coming up in the next few milestones. Yes we need to encourage new people to come contribute whatever function they think is useful regardless of if or where we had that function in our plans, but surely the main development team need to have a bit more focus and coordination if we're to create something very useful. ...ant
