Well, it sounds like a wild ride, but I'm willing to
give it a shot. +1.
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > +1 - I can say I agree 100%.
> >
> > Regarding peer review and "releasing" - if the
> component is used in a
> > product, it'll be released as part of the product.
> >
> > If it is productized and released as stand-alone -
> normal jakarta rules should apply.
>
> How about this then:
>
> --
>
> (1) scope of the subproject
>
> The subproject shall create and maintain packages
> written in the Java
> language, intended for use in server-related
> development, and designed
> to be used independently of any larger product or
> framework. Each
> package will be managed in the same manner as a
> larger Jakarta product.
>
> (1.5) interaction with other subprojects
>
> The subproject CVS will be available to all Jakarta
> committers as a
> sandbox for new packages. Before release
> to the public, a sandbox package must either be
> accepted to the library,
> or be sponsored by another Jakarta
> subproject. The subproject will also catalog
> packages available to the
> public through other Jakarta subprojects and ASF
> projects.
>
> --
>
> Should we stick with calling this the Library
> project, or something
> else, like Agora, Rupert, or Zarf?
>
> -T.
=====
Morgan Delagrange
Britannica.com
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
