On Wed, 14 Mar 2001, Ted Husted wrote:
> [EMAIL PROTECTED] wrote:
> > The mechanics are simple - make it as open as possible to the needs of
> > jakarta subprojects. Don't force any pre-set solution, but let them choose
> > how to use the commons. After all, we are talking about clearly defined
> > entities that have the right to choose on their own.
>
> I believe the only area of concern are the points of public release.
>
That's a valid point of concern, but that is not the problem that *I* have
with the current proposal.
> As long as we are agreed that the sandbox CVS is
>
> (1) Open to all Jakarta Committers, and
> (2) Closed to the public
>
I'm in agreement on these two points.
> then I think everything else falls into place for all of us.
>
Except for the ambiguity pointed out in my previous message -- is the
sandbox code just experimental, or is it released? Costin's proposal is
that it could be either (if a subproject elected to tag some sandbox code
and include it in their release).
I can also guarantee you, from personal experience, that this will trigger
more "Building XYZ is Hard!" complaints because of the extra dependencies
it creates when people want to build subprojects from CVS.
> -Ted.
>
Craig
