1. What are the 'functional groupings' that we'd like to organize around? 2. What are the sizes of the 'functional groups'?
In order to properly answer #2, I think we'd need to get a handle on #1 first. So, I'd like to solicit suggestions for #1 with approx. 1-line summaries for each functional group to allow people to say, "Okay, I understand what this functional group is doing."
Projects could easily fit into multiple categories (like SF's Trove), however my concern is that if a functional group is 'too big,' I think we should start an effort to spin it off as its own TLP.
To start off:
So far, I've heard (from Stephen): - XML - HTTP/HTML/Networking - Database - Enterprise - Pooling
Here's my commentary on the above:
- XML: Should this be under xml.apache.org instead?
- HTTP/HTML/Networking: I'd split HTTP and HTML up as they aren't related. (HTTP client and an HTML renderer should/would be separate codebases, I think)
- Database: Should this be under db.apache.org instead?
- Pooling: Can we be more specific? Memory pooling? Connection pooling?
I've also heard 'Collections' and 'IO', but don't profess to know what that means in context.
As far as the ownership, I don't profess to know what the right thing is here. What is the right thing for the XML and Database projects to own? Perhaps we should create a dialogue with the appropriate PMCs? However, before doing that, I'd like to know what the candidate projects are. What exactly are we thinking of that would be 'database' and/or 'XML'?
Thanks! -- justin
