> The two ideas are:
>
> (1) Any Jakarta committer is entitled to karma to the sandbox, and can
> work on whatever they like there. No questions asked.
>
> (2) A codebase developed in the sandbox can't be released to the public
> from the sandbox. To release the code to the public, you would have to
> move it to another Jakarta CVS, where a subproject could vote to release
> it.
"move" doesn't necesarily means a physical move, I hope.
( the code will continue to "live" in the common workspace, and be
used/shared by multiple projects ).
It can't have a public release without either beeing accepted ( voted ) as
a library project - i.e a general purpose utility that is maintained by
library, or included in an existing jakarta project - in which
case it will be exposed to the public anyway. If the component is included
in a project - that means it goes through testing, etc as part of the
project and is maintained as part of the project - so it should be ok to
be tagged and can be distributed "standalone" too.
AFAIK the reason for not exposing it to the public is that the component
may not have the support and quality that is needed. That's why a vote is
needed before releasing anything. I think support from jakarta-xxx for a
component is as good as support from jakarta-library.
Since the sandbox is open to all jakarta commiters, moving it to another
repository will make it more restrictive - I don't think this is a good
idea.
That's my understanding at least.
Costin
>
> The sandbox could just as easily be part of the Jakarta backbone site,
> but it making it part of the Commons proposal seemed like a convenient
> way to set it up.
>
> "Craig R. McClanahan" wrote:
>
> > In point 20, I understand how a sandbox project can get accepted by the
> > Commons (see 17), but what does "or sponsored by another Jakarta
> > subproject" mean? Does that mean I can bypass the voting in 17 if my
> > subproject's committers are willing to support the code, or what?
> >
> > Craig
>
