incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <>
Subject Re: Explanation of the extra pain (was: Two other issues to discuss for Subversion)
Date Fri, 13 Nov 2009 20:50:31 GMT

----- Original Message ----
> From: Greg Stein <>
> To:
> Sent: Fri, November 13, 2009 12:23:04 PM
> Subject: Explanation of the extra pain (was: Two other issues to discuss for  Subversion)

> Okay. I *think* that is pretty much the background/rationale (please
> refine/add/etc). But that said, we recognize the pain. Are there
> *other* ways that we can achieve the same effects without the
> double-move? (of lists and repos) Are there avenues of communication
> that Incubator can manage? For example, rather than putting
> in all the mailing lists, can it have a
> mandatory header/footer for each message? Can the repository have a
> big README.INCUBATION at the root? The Incubator still has control of
> all releases, so it still can manage branding on all releases. Can we
> tweak ViewVC to dynamically insert a header "This repository area is
> part of an Apache Incubator podling". etc etc.

I am opposed to changing the typical resource layout for an incubating
project.  Release management is one of the most important aspects of
code management at Apache, and frankly there are incubating projects
(eg Thrift) that have no clue how that works.

Incubator is not only a training ground, it is a proving ground too.
We have low barriers to entry because we make clear to the public
that these projects are only granted provisional access to the brand.


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

View raw message