Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <6.0.3.0.0.20050312163525.038648e8@mail.qos.ch>
References: <6.0.3.0.0.20050312134004.038d7ea8@mail.qos.ch>
 <NBBBJGEAGJAKLIDBKJOPKEFLABAC.noel@devtech.com>
 <6.0.3.0.0.20050312163525.038648e8@mail.qos.ch>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <d03b38a67cbc6950a349d51acbe047c4@gbiv.com>
Content-Transfer-Encoding: 7bit
From: Roy T. Fielding <fielding@gbiv.com>
Subject: Re: What is a healthy community? WAS: log4net 1.2.9 beta release  
Date: Sat, 12 Mar 2005 10:53:15 -0800
To: general@incubator.apache.org

On the contrary, the rule is that you must have at least three
binding +1 votes from the PMC in order to make a release of anything.

I don't believe in umbrella projects, so from my perspective log4net
is just one subdirectory in logging.  If logging wants to take
responsibility for it and logging has at least 3 people willing
to +1 its releases, then I don't see how keeping it in incubator
will help.  If logging later loses interest in the project, then
there won't be 3 +1s to do a release, the code will remain static,
and we are no worse off than if that code had died within incubator.
In any case, it is far more likely to gain community once it
leaves incubator, so making "community" a requirement for graduating
a subdirectory of an existing project is self-defeating.

....Roy


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