incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Hunt <>
Subject Re: [DISCUSS] Graduating from the Incubator
Date Thu, 06 Feb 2014 01:13:27 GMT
Does everyone understand the process and requirements necessary for a
functioning project that "gets the Apache Way(tm)" :-)

So far I only see Aaron as the RM, it would be good for other folks to
take a turn (ensure someone else is available, Apache never wants to
have a single point of failure on this stuff).

Doug makes a good point
should highlight how to download the released artifacts. The site
needs some work, you should review the branding and site guidelines
(esp the incubator ones as they are more prescriptive)

You're missing the incubation disclaimer from what I see. (a big
no-no, should be fixed asap)

iirc the name search is complete, is that right?

Probably would be a good idea to clean up the site a bit and do a
release or two under different RMs. I don't see any other major issues
though. Continuing to build community is great, but you have the
minimum imo.


ps. keep in mind that graduation to TLP is really nothing "magical".
There's less oversight, but all the basic things that you did during
incubation still need to get done.

On Wed, Feb 5, 2014 at 10:01 AM, Doug Cutting <> wrote:
> Tim,
> Good question.  You've made a few releases, you have 3+ active
> developers, so perhaps its time to start the graduation process.
> Looking at the website, I'd prefer it better distinguish between users
> downloading release tarballs and contributors getting sources from
> git.  For example, the "download it now" link only mentions git, and
> the "getting started" page in the released documentation tells how to
> build from git rather than from the released sources.  This is in part
> a legal issue: Apache's legal product is source code tarballs, and
> that's what end users (folks outside of Apache) should be steered
> towards.  Contributors are insiders, part of Apache, and can be
> directed towards git.  We want users to transition to contributors,
> but there should be a distinction.  A best practice is to put
> contributor-oriented documentation on separate pages from end-user
> documentation.
> Doug
> On Wed, Feb 5, 2014 at 9:18 AM, Tim Williams <> wrote:
>> Does anyone know if anything holding up our graduation?  I can update
>> the status page but AFAICT all the key boxes have been properly
>> checked and we could move on?
>> Doug? Patrick?
>> Thanks,
>> --tim

View raw message