Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 33426 invoked by uid 500); 12 Jun 2003 12:14:51 -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 33406 invoked from network); 12 Jun 2003 12:14:50 -0000 Received: from dobit2.ugent.be (HELO dobit2.rug.ac.be) (157.193.42.8) by daedalus.apache.org with SMTP; 12 Jun 2003 12:14:50 -0000 Received: from allserv.UGent.be (allserv.ugent.be [157.193.40.42]) by dobit2.rug.ac.be (8.12.8/8.12.8) with ESMTP id h5CCEof3016309 for ; Thu, 12 Jun 2003 14:14:50 +0200 (MEST) Received: from otsrv1.iic.rug.ac.be (otsrv1.iic.ugent.be [157.193.121.51]) by allserv.UGent.be (8.12.8/8.12.8) with ESMTP id h5CCEnqg010611 for ; Thu, 12 Jun 2003 14:14:49 +0200 (MEST) Received: from outerthought.org (host104 [192.168.123.104]) by otsrv1.iic.rug.ac.be (8.11.6/8.11.6) with ESMTP id h5CCEnx14043 for ; Thu, 12 Jun 2003 14:14:49 +0200 Message-ID: <3EE86EB9.20708@outerthought.org> Date: Thu, 12 Jun 2003 14:14:49 +0200 From: Steven Noels Organization: Outerthought User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: Going going gone! References: <200306121907.23168.peter@realityforge.org> <3EE86D71.7060501@outerthought.org> In-Reply-To: <3EE86D71.7060501@outerthought.org> 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 On 12/06/2003 14:09 Steven Noels wrote: > On 12/06/2003 11:33 Ulrich Mayring wrote: > >> So Phoenix will go out of Avalon, but retain the Apache license? Or >> will it get a new license? Or will there be a fork and users have to >> decide which branch to use? > > > If development on Phoenix continues outside Apache CVS (which is > perfectly legal), it will be under a different name. Putting some dots on the i: * permission to use Avalon Phoenix as a 'brand name' will need to be granted by the Avalon PMC * the license won't be Apache's anymore since this requires its codebase to be residing in ASF CVS, and the Avalon PMC having oversight over the codebase * in case of a fork, I'm pretty sure package names for Phoenix' implementation classes will need to renamed, but unless you use Phoenix-specific classes or methods in your apps, that shouldn't have too much effects I hope this helps and can trigger some discussion. Kind regards, -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org