The Board *would* prefer to see more TLPs rather than complicated structures under one large PMC. The problem here is based on one PMC trying to oversee way too many projects. Partitioning should help.
So, (after much thought and rumination), can we just turn XML into a federation of TLPs with a common web site, e-mail etc? Most of the projects in XML would stand on their own, with one or two exceptions that we could look at gathering together to create a single TLP.
For those that don't particularly want to set up their own web site, change e-mail lists etc. leave everything as it currently is and have a group of vulunteers from each member project of the group who take care of those issues.
Means a few more TLPs = more PMCs for the board to look after, but might fit more with the spirit of what you are looking for. At the same time, it prevents an explosion of web-sites and all the stuff that comes with a TLP.
Any current sub-project preferring their own web site etc. could head down that path. But keeping everything together gives the grouping of projects (I believe) a greater focus and wider community.
Also, we could leave the current smaller sub-projects in XML, but have the XML PMC reduced to members in those sub-projects and require they be accross all of them (i.e. an active part of -dev in each).
Cheers, Berin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]