impossible - as my accumulated 1Gb of mail proves). i'd like to propose that apache-commons creates organizational substructures inspired by the jakarta-commons model each consisting of a group of related products so that products will feel at home.
Sure. We have consistently said that projects should be aligned on functional groupings. I'd like to ensure that we foster a language-neutral, but functional-specific groupings. That said, it's the responsibility of the Commons PMC to ensure that this behavior is fostered successfully.
here's my list of characteristics for groups:
1. products would still be affiliated with jakarta (and retain links from the jakarta site) but would be managed by the apache-commons pmc. 2. products would be grouped together with other similar products to form a group creating synergy. it should be easier to recruit new products since this synergy would be much clear than the general 'apache-commons'. 3, each group would have a name and a web page. each product within the group would also have web pages organized underneath. 4. each group would be language agnostic based upon a topic. 5. it would be possible for groups to be promoted to top level project status (given sufficient momentum). 6. there would be one development mailing list for each group. 7. there would be one user mailing list for each group but products would be entitled to retain their existing user lists.
Yup, I mostly agree. I'd add that we have tended to find that user and development lists should only be split out later rather than sooner. I think the incubator policy is to keep them together, and I think it fits here, too. If there's a *lot* of user traffic, then we can create new user-specific lists, but I don't think that should be the 'default.'
The other criteria that I'd add is that each functional group MUST have a Commons PMC member affiliated (hopefully, many more than one...). Now, during the bootstrap process, we can add a whole bunch of new PMCers to get the seeding right. But, no functional groupings should exist without representation in/from the PMC.
Additionally, *I* don't know what these functional groupings should be. Our approach so far has been to be passive: the Apache Commons project is up, but we haven't been very evangelical about spreading the word because we don't want to seem like we're forcing people to move over. Ideally, the Jakarta Commons projects that would like to migrate over can propose what they think the functional groupings should be for their projects. Then, we can create a dialogue between the current Commons PMC and the 'potential' projects to finalize the groupings..
Perhaps it'd be worth it to have a BOF/discussion at AC about how projects can migrate from Jakarta Commons to Apache Commons in a way that makes everyone happy? Are there going to be enough people there (both in Apache Commons and Jakarta Commons) to warrant a discussion? -- justin
