There are a number of differences between SourceForge and Apache. The
tooling aspects is just one difference. The community models are also
quite different. I personally feel the latter is more important.
I've been holding back as I really want to push this decision down, but my
preference is that
1) The scope starts small. Once the community aspects of getting disparate
projects (e.g., Struts and Turbine) to share common code are resolved,
determine an appropriate rate of growth.
2) The ability of "consumers" to trust the stability of the code base takes
precedence over establishing diversity.
3) Jakarta committers are considered "pre-approved", but are only
considered for inclusion if they express a commitment to maintaining a
portion of the code base.
4) The scope is aligned with, and complements, Avalon's scope.
- Sam Ruby
