On 2 September 2011 11:08, Christian Grobmeier <grobme...@gmail.com> wrote:
>> I agree. I'd say we are about 50/50 right now. My concern is that
>> nobody has yet addressed the real reasons why releases are not allowed
>> (in a nutshell that it would become a way to circumvent the
>> incubator).
>
> If a labs project cannot vote in an external committer - wouldn't this
> solve the "bypass the incubator" issue?

Quite possibly. I don't think that has been separated out in our
discussions before. Previously the two have been conflated (allow
external committers and allow releases). It might be useful to explore
these as separate issues.

That means the due diligence (see Simone's email) issue it the big
blocker. It's hard enough to get three binding +1s in the incubator,
how hard would it be here where there is no community building?

> Furthermore:
> - labs can only become assimilated by existing projects.

Not sure what you mean hear. Droids, for example, is going through the
incubator with a goal to being a TLP.

> - releases can be made, marked with -experimental
> - Labs is open for all kind of ideas; even plugins for existing
> projects, when asf people have no karma to the specific project.

This doesn't solve the other complaint about labs - no external
committers. However, I'd like to see if others feel it is beneficial
to separate out these two issues as you propose above.

Ross


>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org
> For additional commands, e-mail: labs-h...@labs.apache.org
>
>



-- 
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com

---------------------------------------------------------------------
To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org
For additional commands, e-mail: labs-h...@labs.apache.org

Reply via email to