I think where I am frustrated is that there are a LOT of smart developers here who wouldn't mind contributing [that's an understatement - we are begging to be allowed to contribute] - not only cash, which I and many others have done - but time as well.
Closed betas for open source projects? It just doesn't make sense to me, I guess. The core developers are ignoring their most valuable resource - the community.
We're seeing cathedral style development where (if this thread is any indication) there are 10's ... 100's maybe even thousands of people who are willing [begging] to help find and fix any issues, and even vet proposed patches before sending them so as not to overwhelm the core developers with additional work.
It's true that development can't easily be parallelized, but bug hunting (and bug fixing) certainly can - and that's where we've been for the last few months. I *bet* these bugs could be knocked out in a matter of days if not hours with a simple, alpha release - or better yet - anonymous read access to a subversion / CVS repository.
We aren't all "takers", we like to contribute because we (the CB community) also love the craft and want to contribute our not-insignificant expertise.
But with the current development methodology (closed, cathedral style releases) there isn't any way for me to contribute code - or even LOOK at the new API so I can make my modules work - JQuery issues or no.
Maybe it is time to re-visit the heart of open-source?
catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/index.html#catbmain
...
6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
7. Release early. Release often. And listen to your customers.
It's still not too lat to begin treating the community like co-developers.
I do appreciate the work of everyone involved ... I'm just hoping that there can be some "openness" to CB in the (very near) future.
Nick
Post edited by: commercemeister, at: 2008/05/28 20:03