Hi,
On Thu, Aug 19, 2010 at 2:54 PM, Jochen Wiedmann
<[email protected]> wrote:
> On Thu, Aug 19, 2010 at 2:19 PM, Jukka Zitting <[email protected]>
> wrote:
>> We can always change the Labs bylaws if we think it's OK to make
>> releases of lab codebases. [...]
>
> The current question is, though, whether we *want* such a change.
The rationale for the no-releases policy is:
"The reason why Labs are prohibited from making releases
is to simplify operation and avoid the legal oversight associated
with the release process and to avoid labs from becoming
ways to route around the incubator."
- http://labs.apache.org/bylaws.html
I think we could fairly easily take care of the extra responsibilities
of the release process.
The second part of the rationale is more important. I guess the main
point in here is that as soon as you're starting to build a user base
with your releases, you're in fact already building a community. If we
do allow releases from Labs, what's then our tripwire for pushing
projects into the Incubator?
I realize that the migration into the Incubator is a pretty big step
for an early codebase, and that by allowing releases we could make it
easier to see how much external interest there is about the project
and how likely it would be for it to "survive" incubation.
So yes, at least I could be persuaded to allow releases from the Labs.
Alternatively we could look for ways to make the migration into the
Incubator less complex.
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
