quote:
Originally posted by Casey:<STRONG>
but what's to prevent Toady from using Sourceforge or something</STRONG>
Such a system would firstly expose the code to the possibility of someone copying it outright and creating an actual "anyone can write" repository. (Though it would be out and out copyright infringement, people don't seem to respect copyrights. -_-) And secondly, it would only benefit Toady if those submitting patches could be trusted outright, without requiring review, which brings it back to being a private project anyhow (see below). As it is, development is rapid with the coding team. It's just the areas that are focused upon vary from what any given observer would most desire.
quote:
Originally posted by Casey:
<STRONG>people could look at the code, squash bugs and/or write minor features or improvements, and then submit a patch.</STRONG>
Reviewing small patches for bug proofing (cure worse than the contagion) and accuracy takes longer than writing the patches themselves. Finding bugs in a reproducible manner is generally harder than fixing them. Which is to say, if these things were really that easy to fix, they'd be done by now. Often you're looking at an issue that's more systemic, and doing a fix right now will mean refixing things properly with more effort later. And that sort of thing is a pain.
Overall, as coding groups get larger than 5, you have to spend time managing group cruft instead of creating, which just drains the fun out of things.
</ramble>
Edit: (Whoops, forgot to snip the quotes and reorder my response to be in order.)
[ January 20, 2007: Message edited by: OldMiner ]