Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of hyandell@gmail.com designates
 209.85.146.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=O6IgZeWZElJMaUXtjuHFmwDIdd2TErvmJa0zKT+Rx0G0ex0LML0dvyQ7BV5xi9s4aU28oyCPWSnAD0po9WoetA0ZwjRh8/i0ZivBdZveZr+//LjQ6Nv73yhpEXGNfwujzM+ffsjG7maKxT92Ix+BiXhIUE5UAE4sY34x34d+5BI=
Message-ID: <2d12b2f00806031450s249bf00by55cd017e4da2446d@mail.gmail.com>
Date: Tue, 3 Jun 2008 14:50:56 -0700
From: "Henri Yandell" <bayard@apache.org>
Sender: hyandell@gmail.com
To: sebb <sebbaz@gmail.com>
Subject: Re: 3rd party policy
Cc: "ASF Legal Discuss" <legal-discuss@apache.org>
In-Reply-To: <25aac9fc0806031438s7a977c61ua5d4acde8ebb03ba@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <25aac9fc0806031420u5279fb5n827ff0c446ed67ea@mail.gmail.com>
	 <5c902b9e0806031426h49275575vcb6d068c3edc09d7@mail.gmail.com>
	 <25aac9fc0806031438s7a977c61ua5d4acde8ebb03ba@mail.gmail.com>

On Tue, Jun 3, 2008 at 2:38 PM, sebb <sebbaz@gmail.com> wrote:
> On 03/06/2008, Justin Erenkrantz <justin@erenkrantz.com> wrote:
>> On Tue, Jun 3, 2008 at 2:20 PM, sebb <sebbaz@gmail.com> wrote:
>>  > Can Creative Commons be added to the list?
>>
>>
>> CC isn't a single license, but a collection of licenses.  So, you'd
>>  need to be far more precise.  Some variants would be Category X, some
>>  would be A.  -- justin
>>
>
> I did not realise that.
>
> Let's start with
>
> Creative Commons Attribution License
> (http://creativecommons.org/licenses/by/2.5)

Yes - but we ought to discuss whether we want to have a 3rd-party.xml
file in each project as a part of that. CCA, as seen in an earlier
thread, has attribution clauses we are less likely to obey if we don't
have a standard approach to identifying projects distributed. It will
also help with CPL and its ilk.

> That reminds me - most of the licenses are identified only by their
> acronyms. As the number of licenses increases, it becomes more likely
> that these may be misread.
>
> It's also not obvious how to find the licence text given only the acronym.

Definitely need to improve that.

Hen

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org