On Fri, 23 Feb 2001, Peter Donald wrote:
> At 07:41 22/2/01 -0500, Ted Husted wrote:
>
> >+ Committers join the library subproject in the same way they are
> >entered to any Jakarta subproject. Being a committer in another Jakarta
> >subproject is not a prerequisite, nor does it provide free entry to the
> >library subproject.
>
> unless they are moving code from the other project and are willing to act
> as caregiver and guardian ;)
Peter, I think this would be a reasonable middle ground.
I'll change my vote to a +1 if we agree on this issue:
1. A new package can be added by a majority vote of the commiters OR by a
vote in a jakarta project that decides that a piece of the code is
general and there are people willing to move the code and maintain it.
2. The maintainers of the piece that is going to be shared will become
commiters on the library.
If this is going to be a library, any "author" should be allowed in, even
if it duplicates existing books or we don't agree with it's ideas - that
should be fundamental in a library.
Existing jakarta projects should be able to move existing code that is
going to be shared in the library - and the vote should be in the source
project ( since it'll be affected in quite a few ways - a piece that was
under their control will be shared with other projects and some people
will have to spend extra time making the code reusable and change the
project to use the reusable component ). I don't think the library should
be able to reject any particular project ( as long as the code follows the
library standards ).
Regarding commiters - you can have your way, I'm too tired and I have
other things to do then argue.
In other words: I'll vote +1 if the final proposal will explicitely allow
projects to componentize and share thier code, as Peter proposed (with
the maintainers of the shared component becoming library commiters ).
Costin
