incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aidan Skinner" <>
Subject Re: [DISCUSS] Do we really need an incubator?
Date Wed, 09 Jul 2008 20:13:49 GMT
On Mon, Jul 7, 2008 at 10:09 PM, Davanum Srinivas <> wrote:

> Isn't it just a IP Clearance SVN now once people have their way with
> no distinction at all between incubator and non-incubator code?
> What incentives are there left to graduate? How come a little bit of
> pain that makes something obvious to end users is such a no-no? Why is
> it such a big deal to remove one tiny pebble in their path? A lot of

>From my PoV, the incubator isn't about stopping people getting code,
it's about helping the project build a mature, functioning community,
which is the hardest part of the process. Writing code in a public
repository, pushing releases out and accepting feedback through a
mailing list and a bugzilla/jira are all well documented standard
operating practice. It's so standard now that, modulo the publicness,
it's basically (AFAICT) how the majority of software is developed
these days in corporate towers.

The value of the incubator is in helping new projects build a
self-sustaining community around a project, something which the mentor
system helps a lot with, particularly those who are from a more
traditional background and find it less easy to air what they consider
dirty laundry in public.

Surely then, it should be as easy as possible for users to get the
code, and the incubator's role is interacting with the committers and

I realise this is quite carrot heavy, and I know the incubator has
another role in ensuring that the Apache brand is not compromised etc,
but surely the disclaimer on the website and artifact naming are
sufficent? I would be surprised if anybody actually using the software
does so without ever reading the projects website. That would be some
very impressive javadoc if so. ;)

If more stick is necessary with a project, that's probably so
concerning that a warning during the first build for a few developers
that they'll almost certainly just click yes to without reading
properly anyway isn't going to help much anyway.

- Aidan (who, having said all that, has many issues with maven as a
build system and is quite glad that Qpid just switched back, but
that's a deep, tangential rat hole)
Apache Qpid - World Domination through Advanced Message Queueing

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message