Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Date: Fri, 3 Oct 2003 05:53:05 -0700
From: Greg Stein <gstein@lyra.org>
To: general@incubator.apache.org
Cc: infrastructure@apache.org
Subject: Re: Disclaimer text for incubated projects
Message-ID: <20031003055305.F22087@lyra.org>
References: <3F7B0536.6050402@Golux.Com> <20031003040036.B22087@lyra.org>
 <20031003203611.FBE6.TETSUYA@apache.org> <20031003043900.D22087@lyra.org>
 <bljplr$q3a$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <bljplr$q3a$1@sea.gmane.org>;
 from nicolaken@apache.org on Fri, Oct 03, 2003 at 02:19:50PM +0200

On Fri, Oct 03, 2003 at 02:19:50PM +0200, Nicola Ken Barozzi wrote:
> Greg Stein wrote:
> ...
> > To what document do I need to add rule that says "a project ABSOLUTELY
> > MUST make clear that it is under incubation?"
> 
> If we kept all incubated projects under the incubator it would have been 
> clear enough.

I'm alright with that, but I think we need infrastructure sign-off first.
If they respond with, "holy crap. moving cvs repositories and mailing
lists are the biggest pains in the ass", then we may want to reconsider
"everybody under incubator.apache.org". If the response is, "pfft. no big
deal. we can easily move mailing lists and cvs repositories" then I'd
agree with you. Put *everybody* under incubator and only move them when
they exit.

[ cc'd infrastructure for commentary ]

> > We've already been through
> > this process where incubated projects are not being clear about their
> > status; that needs to be captured and retained for ALL incubated projects.
> 
> Proposal: if we still don't want to make incubator-xxx repositories for 
> these files, I would still suggest that:
> 
>    1 - the websites are placed in
>        incubator.apache.org/projects/subproject
>    2 - these projects have as project logo the Incubator Logo
>    3 - They all have as a bottom line disclaimer a note that the project
>        is in incubation

Since the web site is the primary "arrival point" for the projects, this
would do the trick. Depending on infrastructure@'s response, I'd totally
agree with this. I'll go one step further and note that the Board has
mandated that the Incubator is a required step for incoming projects;
thus, all PMCs must follow its rules for incoming projects. IOW, a PMC
cannot maintain a separate website, but must always defer to the incubator
pages pending exit-from-incubation.

> Greg, if you want to be more sure that it's done, IMO we need to be a 
> bit more normnative and say *exactly* what is needed to have.

Agreed. Thus my query: where? :-)

And with the "where" question, we are pending infrastructure's
recommendation.

> I think the above proposal is reasonable, as it minimizes the 
> infrastructure changes when the project is out of incubation (basically 
> 0) and keeps the project clearly in incubation.

Agreed. Great recommendation!

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org