Ceki G�lc� wrote: > We keep saying that Jakarta is not SourceForge. How can this be if > each project can act totally independently?
I think the ASF page says it best: "The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. We consider ourselves not simply a group of projects sharing a server, but rather a community of developers and users." In the US, we have a national community, state communities, and then county, city, town and village communites. For most matters, each sub-community can create many rules of their own. In one state you can turn right on red, in another you can't. This doesn't mean that both states are not part of the same national community. The Jakarta subprojects are the same way. Right now, we have give the subprojects permission to declare their own conventions, or use the project defaults. I think that's fine, we just have to remind the subprojects to use their own conventions. But if a subproject said, "We're going to scuttle the Apache Software License, let one Committer make all the decisions, and disband everyone else's veto power", they would quickly find their access to the CVS cut off. It's a matter of scope and tolerances. I think selecting a coding convention is within the scope of the subprojects, so long as they select one and stick to it. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
