[EMAIL PROTECTED] wrote:
> In which case I think we are back to the initial position - as the
> original vote on library-dev was based on the assumption that jakarta
> subprojects can release and cooperate on sandbox projects, and the sandbox
> was supposed to be an sharing place, not a playground.
I believe Jakarta needs an unattached CVS where people can work on code
before proposing it somewhere else.
This would allow people to develop packages like the DBCP pool first,
and then propose it to the Commons once they had something to show.
This would also be a useful place for people to work on cross-project
code. Or draft entirely new subprojects without have to go off to
SourceForge.
But, I don't believe non-committers should have access to this area. If
we did permit public access, then politics regarding Apache
quality-control would kick in, and start to defeat the purpose.
So, to release the code, something developed in the sandbox would have
to be placed in a CVS where the public does have access, and ultimately
voted on by the committers for that subproject CVS.
I do truly believe that the functionality of Agora will be available
through the Commons. Committers from different subprojects can work
on a common package, and issue a stable release as needed. Each of
their subprojects can then use that release, the way Jetspeed uses
releases of Turbine and Velocity.
-Ted.
