: > An approach to this would be for the CNET developers to back off on : > the commits (even though they are faster/more experienced at them) and : > let others step up.
in general that seems really counter intuative to me, but i think Doug's right on the money... : I'd hate to see this. I think the key is to get more folks using it. : Contributions come from use. So the focus should be on attracting : users, rather than adding features. Missing features are opportunities : for new developers. You'll get users with a great out-of-box : experience, that does most (but perhaps not quite all) of what they want. So it seems like CNET folks should focus on making the existing functionality easier to use, and make it easier for developers who are less familar with the code base to add new featrues -- rather then adding new features ourselves. So things like the improving javadocs and unit testing of the existing code base are "good commits" for yonik and i to work on, because they will (hopefully) encourage other new developers to contribute. but adding new functinality (like a plugin supporting for faceted searching, or autoloading of data from a DB) are best left for future (non-CNET) commiters. is that what you had in mind Ian? -Hoss
