incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <>
Subject Re: Soliciting feedback for a detailed pTLP policy document
Date Fri, 06 Mar 2015 15:00:04 GMT
On 3/4/15 1:41 PM, Benson Margulies wrote:

> On Wed, Mar 4, 2015 at 1:12 PM, Doug Cutting <
> <>> wrote:

>     On Mon, Mar 2, 2015 at 5:31 PM, Roman Shaposhnik <
>     <>> wrote:
>     As a director, I still don't think the board needs to be involved in a
>     pTLP's "graduation".  As far as I'm concerned, any "provisional"
>     status is self-imposed by the PMC and can be removed at its pleasure.
>     From the board's perspective it's either an ASF project or it's not,
>     there's not a useful middle ground.  As a project it needs to provide
>     reports, release according to accepted standards, operate openly, etc.
>     It may be a young project, with a PMC dominated by old-timers who
>     aren't responsible for much of the contribution, but I don't see why
>     that requires a new formal status any more than we need a formal
>     status for old, slow-moving projects that rarely release.
>     Put directly, what does a pTLP's "graduation" change from the board's
>     perspective?  How should it change the way we review the project's
>     reports, etc.?  In short, why should we care about this label?  If a
>     PMC wishes to call itself "blue" that's fine too, but we don't need a
>     resolution when it decides to call itself "purple".
> What's your view of 'incubation disclaimers'? The above paragraph makes
> most sense to me if there are none for pTLPs.

The bigger question is: what does "pTLP" mean to the rest of the world?

Incubation disclaimers are there to inform the rest of the world that
the community working there, and the software it produces, are not (yet)
true Apache projects.  That is, we want end users to understand that
there may be different expectations of project behavior and software
product quality or availability for Incubator podlings than the world
has for full Apache projects.

How are we clearly describing to end users what differences they might
expect between the operations and functionality of pTLPs versus Apache
projects (i.e. formal TLPs)?  And who, specifically, decides when the
pTLP becomes a TLP?

While it's important to ensure that we're being clear within our
communities about how we operate and improve, in this case it's also
really important that we make it clear to the rest of the world what a
pTLP is.

- Shane

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

View raw message