Federation of the XML Project
The XML PMC has been requested by the board to examine methods for ensuring code changes, releases and other such decisions are being made by groups appropriately authorised by the bylaws of the ASF. The current PMC is not actively involved in such activities, and added measures therefore need to be put in place.
One of the proposals that has been put forward is that the XML project be broken into a set of Top Level Projects reporting directly to the board. However, the current sub-projects have all expressed a desire to stay as an integrated group. In order to do this, it is proposed that a Federation of projects be created.
This document briefly discusses this approach and how it might be implemented.
Creation of Top Level Projects
The XML Project is currently divided into 12 sub-projects, with a 13th (XML-Beans) in incubation. These projects are :
- Xerces Java 2
- Xerces C++
- Xerces Perl
- Xalan Java 2
- Xalan C++
- XML Commons
- XML Security
As the first main step, the following Top Level Projects would be created :
- Xerces, comprising Xerces Java, Xerces C++ and Xerces Perl
- Xalan, comprising Xalan Java and Xalan C++
- XML Graphics (comprising FOP and Batik)
- XML Security
This would leave Forrest and XML-Commons. The Forrest sub-project is heavily integrated with the Cocoon project, and the developers have indicated an interest in moving to that project.
It is proposed that XML Commons remain within the XML project, as it is felt by the project that it is important a focus remains on XML related common code.
The above is a suggested breakup. Note that it would not be necessary to completely remove all the sub-projects. It would be enough to reduce the XML project to a set of small projects that can sensibly and realistically be oversited by a single PMC.
There are projects in jakarta.apache.org and ws.apache.org which deal with XML. The XML project could host links to these projects.
Rather than create new web sites and mailing lists for the newly created projects, these would remain as they are today. Over time, those projects that desire to migrate to a top level website or set of mailing lists can do so, on the decision of their PMCs.
Some work would need to be done on the front web-page to document the changed status of the sub-projects and the XML project itself. The focus of the site would also move to one of a single spot for collaborating XML based projects.
The current email@example.com would be cut back to just those developers involved in the sub-projects remaining in the XML projects. All those on pmc@ would be required to be subscribed to all *-dev@ mailing lists of the remaining sub-projects. New pmc@ lists would need to be created for the new projects. These could either be under new Top Level names (e.g. firstname.lastname@example.org) or remain under the XML name (email@example.com).
The firstname.lastname@example.org mailing list would still be used for general discussions on XML and for discussion between the developers working on different XML related projects.
The email@example.com mailing list would also be used for discussion of shared XML infrastructure (xml.apache.org and mailing lists).
The XML project
The XML project would still remain as a catalyst for new XML related projects and activities and as a holder for code in XML-Commons. New projects (that do not arrive by the Incubator) could be started and managed within the XML project and then migrated to TLPs if (and when) they became ready. However the XML PMC would need to remain heavily involved in all such growth projects to ensure the XML project does not return to its current state.