Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 34485 invoked from network); 22 Apr 2004 13:08:09 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Apr 2004 13:08:09 -0000 Received: (qmail 38800 invoked by uid 500); 22 Apr 2004 13:08:04 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 38744 invoked by uid 500); 22 Apr 2004 13:08:03 -0000 Mailing-List: contact dev-help@avalon.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 dev@avalon.apache.org Received: (qmail 38730 invoked from network); 22 Apr 2004 13:08:03 -0000 Received: from unknown (HELO mail1.fw-sj.sony.com) (160.33.82.68) by daedalus.apache.org with SMTP; 22 Apr 2004 13:08:03 -0000 Received: from mail1.sgo.in.sel.sony.com (mail1.sgo.in.sel.sony.com [43.130.1.111]) by mail1.fw-sj.sony.com (8.12.11/8.12.11) with ESMTP id i3MD844e028730 for ; Thu, 22 Apr 2004 13:08:04 GMT Received: from us-sd-xims-1.am.sony.com (us-sd-xims-1.am.sony.com [43.131.1.30]) by mail1.sgo.in.sel.sony.com (8.12.11/8.12.11) with ESMTP id i3MD84Qf025013 for ; Thu, 22 Apr 2004 13:08:04 GMT Received: by us-sd-xims-1.am.sony.com with Internet Mail Service (5.5.2653.19) id <2K822W9V>; Thu, 22 Apr 2004 06:08:04 -0700 Message-ID: <03334AAF1DF8D2119B1000A0C9E32F58065EFD3F@us-pb-xmsg-2.am.sony.com> From: "Farr, Aaron" To: avalon-dev Subject: RE: [Proposal] Keeping Fortress/ECM within Apache Date: Thu, 22 Apr 2004 06:08:18 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Niclas Hedhman [mailto:niclas@hedhman.org] > > Execution > ========= > 1. Merlin becomes a TLP with the help of infrastructure@. > 2. Merlin codebase and documentation is moved. > 3. Avalon maintain Merlin as a "Related Projects" or similar. > 4. Merlin will still depend on Avalon, and will maintain its links. > 4. http://avalon.apache.org/merlin and a few others are maintained as > redirects. > 5. Possibly some other details needs resolution, like which pieces are > actually moved, what shall we do with the org.apache.avalon package names > used in Merlin sub-parts, and will any Merlin committers remain committers > at Avalon... #5 is the tricky part. Some things seem obvious to me, like composition and activation should go with Merlin. But what about repository? It's actually an independent tool, and a rather nice one. Should it go with Merlin? Stay in Avalon? Go to the depot group? And what about meta? The implementation should probably go to Merlin but will we at least have a unified set of meta-tags? And the new avalon-logging? Should it stay in Avalon or move with Merlin? I'm not saying we have to answer these questions now before we make a decision. I just want to point out that there would be plenty of details to work out. The issues are really there regardless of it being Fortress or Merlin which is promoted. Also, for the sake of everyone's sanity, if this proposal is the one accepted, it might make more sense to discuss the details in an IRC meeting so we could cut down on excessive traffic on the mailing lists. The real time communication would allow things to happen faster too. > > World Peace and Extinction of All Diseases will follow... > > > What do you all think? I'm all for World Peace and Extinction of All Diseases. Of course that would probably hurt the medical professions. I think promoting Merlin to a TLP is just as valid an option as promoting Fortress/Excalibur to a TLP. Personally, Merlin seems to make more sense since between the two it's a larger project. What about Leo's proposal? What does the Leo Gang of Nine think? J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org