Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 66630 invoked from network); 4 Dec 2002 09:08:13 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 4 Dec 2002 09:08:13 -0000 Received: (qmail 24242 invoked by uid 97); 4 Dec 2002 09:09:28 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 24149 invoked by uid 97); 4 Dec 2002 09:09:26 -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 24137 invoked by uid 98); 4 Dec 2002 09:09:26 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: "Noel J. Bergman" To: "Avalon Developers List" Subject: RE: How to move forward? Date: Wed, 4 Dec 2002 04:08:05 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200212041947.20519.peter@realityforge.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I assume there will be multiple proposals going on > in which case we can get things like; > proposals/red > proposals/blue > proposals/green > when one of them looks like it is a winner and has enough > momentum split off a new CVS then. I've read Rules for Revolutionaries, too. But isn't the entire point of this exercise to move forward with ONE voice? I don't believe that institutionalizing factions is the best way to address that issue. The more I read the discussions here, the more it seems to me that the only thing that is going to get this community moving forward in unison is to have a single community container (scalable and profiled) under an Avalon CVS module, and preserve avalon-phoenix, avalon-excalibur/merlin, et al, for Avalon 4 container development while Avalon 5 is developed. --- Noel -- To unsubscribe, e-mail: For additional commands, e-mail: