You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Scott Sanders <ss...@nextance.com> on 2002/03/29 19:54:25 UTC
[VOTE] Update charter to allow any Apache committer into the sandbox
Below is a diff of the proposed change to charter.xml. Basically says
any Apache committer is allowed to work in the sandbox, instead of any
Jakarta committer. The intention of this is that other Apache
subprojects (xml), also have some useful java code.
Here is my +1.
Scott Sanders
Index: charter.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
retrieving revision 1.5
diff -u -r1.5 charter.xml
--- charter.xml 13 Jan 2002 19:53:43 -0000 1.5
+++ charter.xml 29 Mar 2002 18:53:34 -0000
@@ -48,7 +48,7 @@
</p>
<p>
-The subproject will host a CVS repository available to all Jakarta
+The subproject will host a CVS repository available to all Apache
committers as a workplace for new packages or other projects.
Before release to the public, code or documentation developed
here must be sponsored by a Jakarta subproject. The sponsoring
@@ -240,7 +240,7 @@
</li>
<li>It is expected that the scope of packages may sometimes
overlap.</li>
<li>Anyone may propose a new package to the Commons, and list
themselves as the initial committers for the package. The vote on the
proposal is then also a vote to enter new committers to the subproject
as needed.</li>
- <li>A CVS repository will be available to all Jakarta committers as a
workplace for new packages or other projects.
+ <li>A CVS repository will be available to all Apache committers as a
workplace for new packages or other projects.
Before release to the public,
code or documentation developed here must be sponsored by Jakarta
subproject.
The sponsoring subproject(s) will distribute the code or documentation
along with the
@@ -327,7 +327,7 @@
<p><b>Should other Jakarta subprojects move their utility packages to
the Commons?</b></p>
-<p>They are welcome to do so. If they would like to experiment with
refactoring a package outside their own CVS tree, they can setup s
hop in the Commons sandbox. Any Jakarta committer is entitled to write
access to this CVS repository upon request. They
+<p>They are welcome to do so. If they would like to experiment with
refactoring a package outside their own CVS tree, they can setup s
hop in the Commons sandbox. Any Apache committer is entitled to write
access to this CVS repository upon request. They
could then decide to propose the package to the Commons, and thereby
become committers to the Commons, or to move it back to their own
CVS, and just list it in the Commons directory where other developers
and users can find it.</p>
<p><b>What will be listed in the Commons directory?</b></p>
@@ -339,7 +339,7 @@
<p>If Jakarta adopts an open-door policy for all its subprojects, then
of course the Commons will follow suit.</p>
-<p>We do have an open-door policy for the sandbox CVS
(jakarta-commons-sandbox). Any Jakarta committer is entitled to write
access to
the sandbox upon request, no vote required, no questions asked. Just
subscribe to jakarta-commons-sandbox, and request
+<p>We do have an open-door policy for the sandbox CVS
(jakarta-commons-sandbox). Any Apache committer is entitled to write
access to t
he sandbox upon request, no vote required, no questions asked. Just
subscribe to commons-dev, and request
authorization.</p>
<p><b>Why not just do this within Avalon, or another existing
subproject?</b></p>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the sandbox
Posted by Jeff Turner <je...@socialchange.net.au>.
+1
--Jeff
On Fri, Mar 29, 2002 at 10:54:25AM -0800, Scott Sanders wrote:
> Below is a diff of the proposed change to charter.xml. Basically says
> any Apache committer is allowed to work in the sandbox, instead of any
> Jakarta committer. The intention of this is that other Apache
> subprojects (xml), also have some useful java code.
>
> Here is my +1.
>
>
> Scott Sanders
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the sandbox
Posted by Ted Husted <hu...@apache.org>.
+1
If they have an Apache account, and access to another Apache CVS, they
know what's what, so why not.
-- Ted Husted, Husted dot Com, Fairport NY US
-- Developing Java Web Applications with Struts
-- Tel: +1 585 737-3463
-- Web: http://husted.com/struts
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the
sandbox
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 3/30/02 9:35 PM, "James Strachan" <ja...@yahoo.co.uk> wrote:
> +1.
>
> Though am not sure if jakarta-commons and xml-commons should be combined and
> moved to a top level project or if we should keep them seperate and allow
> cross-fertilization. I guess commons-dev gets enough traffic as it is so
> maybe keeping them seperate is no bad thing for now.
>
Why not do this incrementally?
For example, lets not modify charter regarding switching 'Jakarta' to
'Apache', but instead setup a jakarta-xml-commons-sandbox, that we then
allow in xml committers as well. That solves the immediate problem of
morphos having an xml committer, as well as test cross-fertilizing with more
of the pointy-bracket types...
It also means that for those who have concerns about the Jakarta->Apache
change, we don't have to do that now.
geir
> James
> ----- Original Message -----
> From: "Juozas Baliuka" <ba...@centras.lt>
> To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
> Sent: Friday, March 29, 2002 9:05 PM
> Subject: Re: [VOTE] Update charter to allow any Apache committer into the
> sandbox
>
>
>> +1
>> ----- Original Message -----
>> From: Scott Sanders <ss...@nextance.com>
>> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>> Sent: Friday, March 29, 2002 7:54 PM
>> Subject: [VOTE] Update charter to allow any Apache committer into the
>> sandbox
>>
>>
>> Below is a diff of the proposed change to charter.xml. Basically says
>> any Apache committer is allowed to work in the sandbox, instead of any
>> Jakarta committer. The intention of this is that other Apache
>> subprojects (xml), also have some useful java code.
>>
>> Here is my +1.
>>
>>
>> Scott Sanders
>>
>> Index: charter.xml
>> ===================================================================
>> RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
>> retrieving revision 1.5
>> diff -u -r1.5 charter.xml
>> --- charter.xml 13 Jan 2002 19:53:43 -0000 1.5
>> +++ charter.xml 29 Mar 2002 18:53:34 -0000
>> @@ -48,7 +48,7 @@
>> </p>
>>
>> <p>
>> -The subproject will host a CVS repository available to all Jakarta
>> +The subproject will host a CVS repository available to all Apache
>> committers as a workplace for new packages or other projects.
>> Before release to the public, code or documentation developed
>> here must be sponsored by a Jakarta subproject. The sponsoring
>> @@ -240,7 +240,7 @@
>> </li>
>> <li>It is expected that the scope of packages may sometimes
>> overlap.</li>
>> <li>Anyone may propose a new package to the Commons, and list
>> themselves as the initial committers for the package. The vote on the
>> proposal is then also a vote to enter new committers to the subproject
>> as needed.</li>
>> - <li>A CVS repository will be available to all Jakarta committers as a
>> workplace for new packages or other projects.
>> + <li>A CVS repository will be available to all Apache committers as a
>> workplace for new packages or other projects.
>> Before release to the public,
>> code or documentation developed here must be sponsored by Jakarta
>> subproject.
>> The sponsoring subproject(s) will distribute the code or documentation
>> along with the
>> @@ -327,7 +327,7 @@
>>
>> <p><b>Should other Jakarta subprojects move their utility packages to
>> the Commons?</b></p>
>>
>> -<p>They are welcome to do so. If they would like to experiment with
>> refactoring a package outside their own CVS tree, they can setup s
>> hop in the Commons sandbox. Any Jakarta committer is entitled to write
>> access to this CVS repository upon request. They
>> +<p>They are welcome to do so. If they would like to experiment with
>> refactoring a package outside their own CVS tree, they can setup s
>> hop in the Commons sandbox. Any Apache committer is entitled to write
>> access to this CVS repository upon request. They
>> could then decide to propose the package to the Commons, and thereby
>> become committers to the Commons, or to move it back to their own
>> CVS, and just list it in the Commons directory where other developers
>> and users can find it.</p>
>>
>> <p><b>What will be listed in the Commons directory?</b></p>
>> @@ -339,7 +339,7 @@
>>
>> <p>If Jakarta adopts an open-door policy for all its subprojects, then
>> of course the Commons will follow suit.</p>
>>
>> -<p>We do have an open-door policy for the sandbox CVS
>> (jakarta-commons-sandbox). Any Jakarta committer is entitled to write
>> access to
>> the sandbox upon request, no vote required, no questions asked. Just
>> subscribe to jakarta-commons-sandbox, and request
>> +<p>We do have an open-door policy for the sandbox CVS
>> (jakarta-commons-sandbox). Any Apache committer is entitled to write
>> access to t
>> he sandbox upon request, no vote required, no questions asked. Just
>> subscribe to commons-dev, and request
>> authorization.</p>
>>
>> <p><b>Why not just do this within Avalon, or another existing
>> subproject?</b></p>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
The cost of synchronization is much less that the cost of stupidity.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the sandbox
Posted by James Strachan <ja...@yahoo.co.uk>.
+1.
Though am not sure if jakarta-commons and xml-commons should be combined and
moved to a top level project or if we should keep them seperate and allow
cross-fertilization. I guess commons-dev gets enough traffic as it is so
maybe keeping them seperate is no bad thing for now.
James
----- Original Message -----
From: "Juozas Baliuka" <ba...@centras.lt>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Friday, March 29, 2002 9:05 PM
Subject: Re: [VOTE] Update charter to allow any Apache committer into the
sandbox
> +1
> ----- Original Message -----
> From: Scott Sanders <ss...@nextance.com>
> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> Sent: Friday, March 29, 2002 7:54 PM
> Subject: [VOTE] Update charter to allow any Apache committer into the
> sandbox
>
>
> Below is a diff of the proposed change to charter.xml. Basically says
> any Apache committer is allowed to work in the sandbox, instead of any
> Jakarta committer. The intention of this is that other Apache
> subprojects (xml), also have some useful java code.
>
> Here is my +1.
>
>
> Scott Sanders
>
> Index: charter.xml
> ===================================================================
> RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
> retrieving revision 1.5
> diff -u -r1.5 charter.xml
> --- charter.xml 13 Jan 2002 19:53:43 -0000 1.5
> +++ charter.xml 29 Mar 2002 18:53:34 -0000
> @@ -48,7 +48,7 @@
> </p>
>
> <p>
> -The subproject will host a CVS repository available to all Jakarta
> +The subproject will host a CVS repository available to all Apache
> committers as a workplace for new packages or other projects.
> Before release to the public, code or documentation developed
> here must be sponsored by a Jakarta subproject. The sponsoring
> @@ -240,7 +240,7 @@
> </li>
> <li>It is expected that the scope of packages may sometimes
> overlap.</li>
> <li>Anyone may propose a new package to the Commons, and list
> themselves as the initial committers for the package. The vote on the
> proposal is then also a vote to enter new committers to the subproject
> as needed.</li>
> - <li>A CVS repository will be available to all Jakarta committers as a
> workplace for new packages or other projects.
> + <li>A CVS repository will be available to all Apache committers as a
> workplace for new packages or other projects.
> Before release to the public,
> code or documentation developed here must be sponsored by Jakarta
> subproject.
> The sponsoring subproject(s) will distribute the code or documentation
> along with the
> @@ -327,7 +327,7 @@
>
> <p><b>Should other Jakarta subprojects move their utility packages to
> the Commons?</b></p>
>
> -<p>They are welcome to do so. If they would like to experiment with
> refactoring a package outside their own CVS tree, they can setup s
> hop in the Commons sandbox. Any Jakarta committer is entitled to write
> access to this CVS repository upon request. They
> +<p>They are welcome to do so. If they would like to experiment with
> refactoring a package outside their own CVS tree, they can setup s
> hop in the Commons sandbox. Any Apache committer is entitled to write
> access to this CVS repository upon request. They
> could then decide to propose the package to the Commons, and thereby
> become committers to the Commons, or to move it back to their own
> CVS, and just list it in the Commons directory where other developers
> and users can find it.</p>
>
> <p><b>What will be listed in the Commons directory?</b></p>
> @@ -339,7 +339,7 @@
>
> <p>If Jakarta adopts an open-door policy for all its subprojects, then
> of course the Commons will follow suit.</p>
>
> -<p>We do have an open-door policy for the sandbox CVS
> (jakarta-commons-sandbox). Any Jakarta committer is entitled to write
> access to
> the sandbox upon request, no vote required, no questions asked. Just
> subscribe to jakarta-commons-sandbox, and request
> +<p>We do have an open-door policy for the sandbox CVS
> (jakarta-commons-sandbox). Any Apache committer is entitled to write
> access to t
> he sandbox upon request, no vote required, no questions asked. Just
> subscribe to commons-dev, and request
> authorization.</p>
>
> <p><b>Why not just do this within Avalon, or another existing
> subproject?</b></p>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the sandbox
Posted by Juozas Baliuka <ba...@centras.lt>.
+1
----- Original Message -----
From: Scott Sanders <ss...@nextance.com>
To: Jakarta Commons Developers List <co...@jakarta.apache.org>
Sent: Friday, March 29, 2002 7:54 PM
Subject: [VOTE] Update charter to allow any Apache committer into the
sandbox
Below is a diff of the proposed change to charter.xml. Basically says
any Apache committer is allowed to work in the sandbox, instead of any
Jakarta committer. The intention of this is that other Apache
subprojects (xml), also have some useful java code.
Here is my +1.
Scott Sanders
Index: charter.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
retrieving revision 1.5
diff -u -r1.5 charter.xml
--- charter.xml 13 Jan 2002 19:53:43 -0000 1.5
+++ charter.xml 29 Mar 2002 18:53:34 -0000
@@ -48,7 +48,7 @@
</p>
<p>
-The subproject will host a CVS repository available to all Jakarta
+The subproject will host a CVS repository available to all Apache
committers as a workplace for new packages or other projects.
Before release to the public, code or documentation developed
here must be sponsored by a Jakarta subproject. The sponsoring
@@ -240,7 +240,7 @@
</li>
<li>It is expected that the scope of packages may sometimes
overlap.</li>
<li>Anyone may propose a new package to the Commons, and list
themselves as the initial committers for the package. The vote on the
proposal is then also a vote to enter new committers to the subproject
as needed.</li>
- <li>A CVS repository will be available to all Jakarta committers as a
workplace for new packages or other projects.
+ <li>A CVS repository will be available to all Apache committers as a
workplace for new packages or other projects.
Before release to the public,
code or documentation developed here must be sponsored by Jakarta
subproject.
The sponsoring subproject(s) will distribute the code or documentation
along with the
@@ -327,7 +327,7 @@
<p><b>Should other Jakarta subprojects move their utility packages to
the Commons?</b></p>
-<p>They are welcome to do so. If they would like to experiment with
refactoring a package outside their own CVS tree, they can setup s
hop in the Commons sandbox. Any Jakarta committer is entitled to write
access to this CVS repository upon request. They
+<p>They are welcome to do so. If they would like to experiment with
refactoring a package outside their own CVS tree, they can setup s
hop in the Commons sandbox. Any Apache committer is entitled to write
access to this CVS repository upon request. They
could then decide to propose the package to the Commons, and thereby
become committers to the Commons, or to move it back to their own
CVS, and just list it in the Commons directory where other developers
and users can find it.</p>
<p><b>What will be listed in the Commons directory?</b></p>
@@ -339,7 +339,7 @@
<p>If Jakarta adopts an open-door policy for all its subprojects, then
of course the Commons will follow suit.</p>
-<p>We do have an open-door policy for the sandbox CVS
(jakarta-commons-sandbox). Any Jakarta committer is entitled to write
access to
the sandbox upon request, no vote required, no questions asked. Just
subscribe to jakarta-commons-sandbox, and request
+<p>We do have an open-door policy for the sandbox CVS
(jakarta-commons-sandbox). Any Apache committer is entitled to write
access to t
he sandbox upon request, no vote required, no questions asked. Just
subscribe to commons-dev, and request
authorization.</p>
<p><b>Why not just do this within Avalon, or another existing
subproject?</b></p>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the sandbox
Posted by Remy Maucherat <re...@apache.org>.
+1
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the
sandbox
Posted by co...@covalent.net.
On Fri, 29 Mar 2002, Scott Sanders wrote:
> Below is a diff of the proposed change to charter.xml. Basically says
> any Apache committer is allowed to work in the sandbox, instead of any
> Jakarta committer. The intention of this is that other Apache
> subprojects (xml), also have some useful java code.
>
> Here is my +1.
+1
Costin
>
>
> Scott Sanders
>
> Index: charter.xml
> ===================================================================
> RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
> retrieving revision 1.5
> diff -u -r1.5 charter.xml
> --- charter.xml 13 Jan 2002 19:53:43 -0000 1.5
> +++ charter.xml 29 Mar 2002 18:53:34 -0000
> @@ -48,7 +48,7 @@
> </p>
>
> <p>
> -The subproject will host a CVS repository available to all Jakarta
> +The subproject will host a CVS repository available to all Apache
> committers as a workplace for new packages or other projects.
> Before release to the public, code or documentation developed
> here must be sponsored by a Jakarta subproject. The sponsoring
> @@ -240,7 +240,7 @@
> </li>
> <li>It is expected that the scope of packages may sometimes
> overlap.</li>
> <li>Anyone may propose a new package to the Commons, and list
> themselves as the initial committers for the package. The vote on the
> proposal is then also a vote to enter new committers to the subproject
> as needed.</li>
> - <li>A CVS repository will be available to all Jakarta committers as a
> workplace for new packages or other projects.
> + <li>A CVS repository will be available to all Apache committers as a
> workplace for new packages or other projects.
> Before release to the public,
> code or documentation developed here must be sponsored by Jakarta
> subproject.
> The sponsoring subproject(s) will distribute the code or documentation
> along with the
> @@ -327,7 +327,7 @@
>
> <p><b>Should other Jakarta subprojects move their utility packages to
> the Commons?</b></p>
>
> -<p>They are welcome to do so. If they would like to experiment with
> refactoring a package outside their own CVS tree, they can setup s
> hop in the Commons sandbox. Any Jakarta committer is entitled to write
> access to this CVS repository upon request. They
> +<p>They are welcome to do so. If they would like to experiment with
> refactoring a package outside their own CVS tree, they can setup s
> hop in the Commons sandbox. Any Apache committer is entitled to write
> access to this CVS repository upon request. They
> could then decide to propose the package to the Commons, and thereby
> become committers to the Commons, or to move it back to their own
> CVS, and just list it in the Commons directory where other developers
> and users can find it.</p>
>
> <p><b>What will be listed in the Commons directory?</b></p>
> @@ -339,7 +339,7 @@
>
> <p>If Jakarta adopts an open-door policy for all its subprojects, then
> of course the Commons will follow suit.</p>
>
> -<p>We do have an open-door policy for the sandbox CVS
> (jakarta-commons-sandbox). Any Jakarta committer is entitled to write
> access to
> the sandbox upon request, no vote required, no questions asked. Just
> subscribe to jakarta-commons-sandbox, and request
> +<p>We do have an open-door policy for the sandbox CVS
> (jakarta-commons-sandbox). Any Apache committer is entitled to write
> access to t
> he sandbox upon request, no vote required, no questions asked. Just
> subscribe to commons-dev, and request
> authorization.</p>
>
> <p><b>Why not just do this within Avalon, or another existing
> subproject?</b></p>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the sandbox
Posted by Morgan Delagrange <md...@yahoo.com>.
Can we defer this vote until after JavaOne? Changes
to the charter require consensus approval, and I have
a feeling that our numbers are depleted this week.
- Morgan
--- "Michael A. Smith" <ma...@apache.org> wrote:
> On Fri, 29 Mar 2002, Scott Sanders wrote:
> > Below is a diff of the proposed change to
> charter.xml. Basically says
> > any Apache committer is allowed to work in the
> sandbox, instead of any
> > Jakarta committer. The intention of this is that
> other Apache
> > subprojects (xml), also have some useful java
> code.
> >
> > Here is my +1.
>
> +1.
>
> I should note that while I agree with the change, I
> think it adds a bit of
> confusion. If the sandbox is apache wide, why is it
> named
> "jakarta-commons-sandbox" and why its hosted with
> Jakarta? Why not as
> xml-commons-sandbox? Why not a new top-level
> project? Just thinking out
> loud. Anyway, I welcome anyone from the XML
> project, and I welcome
> morphos.
>
> regards,
> michael
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - send holiday greetings for Easter, Passover
http://greetings.yahoo.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Update charter to allow any Apache committer into the
sandbox
Posted by "Michael A. Smith" <ma...@apache.org>.
On Fri, 29 Mar 2002, Scott Sanders wrote:
> Below is a diff of the proposed change to charter.xml. Basically says
> any Apache committer is allowed to work in the sandbox, instead of any
> Jakarta committer. The intention of this is that other Apache
> subprojects (xml), also have some useful java code.
>
> Here is my +1.
+1.
I should note that while I agree with the change, I think it adds a bit of
confusion. If the sandbox is apache wide, why is it named
"jakarta-commons-sandbox" and why its hosted with Jakarta? Why not as
xml-commons-sandbox? Why not a new top-level project? Just thinking out
loud. Anyway, I welcome anyone from the XML project, and I welcome
morphos.
regards,
michael
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>