--- "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
> "Craig R. McClanahan" wrote:
>
> > I don't like the ambiguity of what code in sandbox
> means
> > under this scenario. Alternatives to solve the
> problem include:
> >
> > (a) If a project wants to release something that
> includes code in the
> > sandbox, it must either get it accepted into
> commons, or copy the
> > code back into its own repository.
>
> +1
+1 for me as well. I think there needs to be a
gatekeeper (the Commons committers) who decide if a
sandbox component is truly in keeping with the Commons
charter. We should take the responsibility to insure
that released code is stable, good quality, and not
intrinsically tied to another subproject (in which
case it should probably live elsewhere). If a sandbox
component meets those criteria, we'll vote to release
the component in Commons and grant karma to its
commmitters. If a subproject cannot meet the
guidelines of the Commons charter, it should not be accepted.
=====
Morgan Delagrange
Britannica.com
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
