Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org Received: (qmail 52984 invoked from network); 26 Mar 2002 19:00:40 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Mar 2002 19:00:40 -0000 Received: (qmail 27016 invoked by uid 97); 26 Mar 2002 19:00:42 -0000 Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org Received: (qmail 27000 invoked by uid 97); 26 Mar 2002 19:00:42 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 26989 invoked from network); 26 Mar 2002 19:00:42 -0000 Date: Tue, 26 Mar 2002 11:00:41 -0800 From: Brian Goetz To: Lucene Developers List Subject: Re: Action Item Vote Request Message-ID: <20020326110041.A27990@lx.quiotix.com> References: <1017147264.11829.1694.camel@linux2.superlinksoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from carlson@bookandhammer.com on Tue, Mar 26, 2002 at 07:14:59AM -0800 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > 1) Create a contributions area as part of the Lucene CVS. This area would be > used to bring together submitted to the Lucene mailing list (with permission > from the submitter). The code would need to be repackaged (i.e. Give it an > org.apache.lucene.contrib package), licensed (add the apache license), added > to the "build-contrib" target of the ant build script. > > There are a lot of great contributions out there that may or may not become > part of Lucene's core build. I am +1 and am willing to set this up and help > maintain it. I prefer instead to have the /contrib area a separate CVS repo. My experience in other OS projects is that (a) contrib areas rapidly get to be larger than then main distribution, making downloads slower, and (b) often get out of sync with the main distribution. The result is that a mix of core code and contributions of varying levels of quality, completedness, and maintainedness tends to lower the perceived level of quality of the distribution. So +1 for a /contrib area, -1 for making it part of the main CVS repo and distribution. > 2) Create a scratchpad area in the Lucene CVS > (org.apache.lucene.scratchpad). This area would be focused on creating new > parts of the Lucene core in an experimental mode. This code would be > considered unstable and unsupported. If a part becomes stable and is desired > to be moved into the Lucene core build, it must be approved through a > committers vote (+3 votes). Again, -1 if this is part of the main CVS repo, +1 on the concept. > 3) Adopt a more formal release plan. > a)Beta means feature freeze > b)Release candidate means code freeze (unless bugs) > To move into a beta or release candidate stage, you must a vote by the > committers (+3 votes). +1 -- To unsubscribe, e-mail: For additional commands, e-mail: