Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 60781 invoked from network); 5 Dec 2002 10:40:42 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 5 Dec 2002 10:40:42 -0000 Received: (qmail 17137 invoked by uid 97); 5 Dec 2002 10:41:57 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 17121 invoked by uid 97); 5 Dec 2002 10:41:57 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 17109 invoked by uid 98); 5 Dec 2002 10:41:56 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DEF2CBD.1000401@apache.org> Date: Thu, 05 Dec 2002 11:38:53 +0100 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5 codebase (Re: How to move forward?) References: <000c01c29c49$c7afd450$0801a8c0@Lagrange> In-Reply-To: <000c01c29c49$c7afd450$0801a8c0@Lagrange> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Leo Sutic wrote: > > From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] > > Nicola Ken Barozzi wrote: > [...] > >>I propose we have a new "avalon" CVS repository where to > > develop the > >>new >>Avalon5 system. Things will be discussed and committed only > > when decided > >>upon, and still eventually changed when again decided upon. >> >>This will make us do a clear cut with previous development methods, >>and >>clearly indicate that it's a new effort and that the old will be >>nevertheless maintained. >> >>+1 for a new "avalon" CVS repository >> >>Alternatively it can be called avalon5, avalonV, aValon, avalon-5, >>avalon-ng... the important thing is that it's there. > > Despite a feeling by some that a decision has been taken on this, > current votes stand in a tie like this: > > o Creation of an "avalon" CVS repository for new Avalon5 > codebase > +1: nicolaken, mcconnell > +0: cziegeler > -0: proyal > -1: leosimons, leif > > > Anyone else wants to say his? > > > I think the deadlock (and the few votes) is reason enough to just hit > the "pause" button on this voting for say, two-three days, and then > try again. Let's have a go at the charter first, and then re-visit > this one. > > Does that sound sensible? More than sensible, I'm on the same track. :-) > I am +1 for the new CVS (I think we should have an avalon CVS instead of > a > jakarta-avalon anyway), and I think that this new unified effort should > have a CVS of its own (no need to have "proposal" directories and stuff > like that + it doesn't make the new effort a sub-project of some > existing module). OTOH, I am reflexively against creating "new > playgrounds", > maybe irrationally so. But the fact that this vote ran into a deadlock > makes me not want to tip the balance. I'll not put this vote in the STATUS file then myself, and wait till we find more agreement on it. When you feel it's time to place your vote, post it or commit it. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: