Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jpjhughes@gmail.com
 designates 209.85.161.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type;
        b=JHaaMc+hTa7wW0Gz+8K7KwCryZN0PceKldW7my3VOTKLsTjHfKBmxp4ujNVlFT3gl5
         /iCq1xVEX5i1fBTyaeyZpGj4DYk19UgwUZ7/o/8hzmRtnz2xHYxBKhwAhMoHpqN8IMjD
         RJO5cTTTKtDuu0lsVdDLPVizPszPRqGieTyDI=
MIME-Version: 1.0
Sender: jpjhughes@gmail.com
In-Reply-To: <FA606272-AD1D-4BF2-A6FD-B76B11A284CE@gmail.com>
References: <o2padbf02b11004221039l503ed264scc187f5ba83d7347@mail.gmail.com>
	<0EC9D5EE-8B6A-4488-A733-EBF8D8B57112@gmail.com>
 <u2sadbf02b11004270644v32a23bbcl629e1a893e1c51e7@mail.gmail.com>
	<3AB07336-B026-4ED2-A9D3-BB7F4AB27218@gmail.com>
 <o2uadbf02b11004271443wd316c8ebm764851108912e622@mail.gmail.com>
	<4BD83B02.4020307@apache.org>
 <r2jadbf02b11004280722n8cfaf066oe98db8a7c980a436@mail.gmail.com>
	<FA606272-AD1D-4BF2-A6FD-B76B11A284CE@gmail.com>
From: Jeremy Hughes <hughesj@apache.org>
Date: Thu, 29 Apr 2010 17:46:04 +0100
Message-ID: <p2padbf02b11004290946t783785e0j175d6ee439c373ca@mail.gmail.com>
Subject: Re: [VOTE] Apache Aries (Incubating) v0.1 release candidate #2
To: aries-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 29 April 2010 17:11, Kevan Miller <kevan.miller@gmail.com> wrote:
>
> On Apr 28, 2010, at 10:22 AM, Jeremy Hughes wrote:
>
>> I've raised it on legal-discuss. Has the following option been
>> considered to satisfy the "... and include the License file at
>> glassfish/bootstrap/legal/LICENSE.txt.":
>>
>> Include that LICENSE.txt file separately from the project's LICENSE
>> file in a directory called glassfish/bootstrap/legal directory within
>> the jar/zip AND include the CDDL only in the project's LICENSE file
>> located at the root of the zip.
>
> Well, you could remove the CDDL license from LICENSE and add an entry in LICENSE that points to the LICENSE.txt (i.e. the CDDL+GPL license file).

I was thinking keep the CDDL license in LICENSE, and not add the GPL
portion. The LICENSE would then represent the licensing of the files
in the zip - as we have elected to license the two schema files as
CDDL.

> Something like 'licenses/GLASSFISH-LICENSE.txt'. Some projects follow similar schemes -- one AL2 LICENSE file with multiple licenses in a 'license' subdirectory.

This would be to satisfy the text in the header in the schema file
which says "... and include the License file at
glassfish/bootstrap/legal/LICENSE.txt." ... so this specifically says
to include the License file rather than append the License file to the
one we have.

>My personal preference (Geronimo consumes a lot of artifacts) is to have all licensing information within the LICENSE file. It's much easier for consumers of your artifacts to review/follow...

Which would normally be mine too, but I was trying to avoid confusing
consumers who review the LICENSE file and on doing so would see 'GPL'
even though none of the artifacts in the zip are licensed under the
GPL. AIUI, while the schema files were originally CDDL+GPL, because
we've elected to use the CDDL license, any consumers of our package
cannot subsequently relicense them as GPL.

I think both options have merits and pitfalls and since I want to get
on and create a new RC and the most agreed on approach is to put the
full CDDL+GPL in the LICENSE file, then that is what I'll do.

Thanks though, I do appreciate the discussion.

>
> --kevan
>
>