+1
Regards -Ramesh
Hello Xalan developers,
this is a motion to transform Xalan into a top-level Apache project. It is
exactly the same as the last time I sent the motion, except for point 4,
which was this:
4. The initial PMC members for this project will be Santiago
Pericas-Geertsen and Brian Minchau, who are the existing PMC members for Xalan. This point has been changed to include more PMC members.
I'm formally calling for a vote on this proposition which is to transform Xalan from a sub-project of the Apache top-level XML project into a top-level Apache project of its own.
1. The top-level Xalan project will contain the existing Xalan-J and Xalan-C projects. 2. The top-level Xalan project will initially contain no sub-projects. 3. The initial committers for this project will be the existing committers of the Xalan-J and Xalan-C. 4. The initial PMC members for this project will be: Dmitry Hayes Matthew Hoyt Christine Li Ramesh Mandava Brian Minchau (existing PMC member for Xalan) Santiago Pericas-Geertsen (existing PMC member for Xalan) Joanne Tong Arun Yadav Henry Zongaro
5. The initial PMC Chairperson will be Brian Minchau. 6. The initial mission statement will be http://xml.apache.org/mission.html , although terms such as "xml.apache.org project" should be read as "Xalan project".
-------------------------------------
In January and February of 2004 the idea of converting Apache XML project into a "Federation" of top-level projects was discussed. (see http://nagoya.apache.org/wiki/apachewiki.cgi?XMLProjectPages/FederationProposal )
The reason this proposal is that the Apache Software Foundation by-laws make assumptions about its structure, and the Board is concerened about legally defending itself, such as better accountability on whether a given release of a product was sanctioned. Releases, for example, are supposed to be voted on by the PMC members responsible for a product. There needs to be a verifiable link between the Board and the decision to make a release.
From a practical point of view I don't see that we are going to loose any connection with other sub-projects of the XML project. That connection is either there or not, and being a top-level project won't change that.
Being a top-level project will keep the management of Xalan clear of the other XML sub-projects.
In the future I see Xalan's own mission statement, with more realistic rules on voting, but that is not part of this proposal.
Here is my +1 vote.
---------- Brian Minchau XSLT Development, IBM Toronto e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
