Ted Husted wrote:
>
> [EMAIL PROTECTED] wrote:
> > Yes, that's exactly what I said - a jakarta subproject should be able to
> > vote and take responsibility for distributing a product - it can be
> > developed in it's own workspace or in a shared CVS.
>
> I just don't understand what the problem is, Costin. Doesn't the
> proposed #20 say that?
>
> If it makes any difference, we could probably strike "the accepted to
> the commons part", and just say
>
> "20. A CVS repository will be available to all Jakarta 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 subproject will distribute the code
> or documentation along with the rest of their codebase."
That seems to solve it all - If Commons is that subproject, then
Commons would have to approve accepting it as part of its
'distributables'. Further, it places no restrictions on the activities
within that CVS repository...
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
