Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 72.14.220.155 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=wbLfNOLqTtj99bYOt7DWrnJt/RPkQauy8NJuBwb9aJKDN3XrEk0ZSXHZxn0iIc+SHYXkd+9PvlUMBT0Vy0S5c2WUexTqATguDSiSvtSJ05JSagPrEKaJreCIaKpLWujdPZCVKeyl4xdelfWue0xbY6oD1cvdDe6RJ1Y9XUArFOc=
Message-ID: <25aac9fc0806010933j56f70f37k90d68136ea3cc678@mail.gmail.com>
Date: Sun, 1 Jun 2008 17:33:02 +0100
From: sebb <sebbaz@gmail.com>
To: "ASF Legal Discuss" <legal-discuss@apache.org>
Subject: Re: Creative Commons Attribution License
In-Reply-To: <2d12b2f00805290046j3f36e2dcyfe34ec90e313939b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <25aac9fc0805280734g4f04c019le8c2f904cc940da0@mail.gmail.com>
	 <2d12b2f00805280834u5d853909qef29153f74052f53@mail.gmail.com>
	 <C4BC8DE6-23F3-4672-B314-7D3760D715E7@SUN.com>
	 <3d4032300805281708m340728t5198d5456a49519e@mail.gmail.com>
	 <2d12b2f00805281745j643049f3o67f0687c6a518e5f@mail.gmail.com>
	 <e9d8a2610805290015n2f049bben604a2a48fb633be5@mail.gmail.com>
	 <2d12b2f00805290046j3f36e2dcyfe34ec90e313939b@mail.gmail.com>

Going back to the original question, the concensus seems to be:

1) A project can unconditionally depend on a binary released under the
CCAL, e.g. jcip annotations.

2) A jar released under CCAL can be stored in the Maven repository;
how it gets there is a matter to be resolved.

As it happens, it looks like the annotations classes are already in
the M2 repository as part of Findbugs. However Findbugs is LGPL v2.1
licensed.

On 29/05/2008, Henri Yandell <bayard@apache.org> wrote:
> Fair point - their attribution clauses (section 3b) are a bit more
>  convoluted than such things normally are. I'll note it on the
>  resolved-questions page. Digging into the details of 3b:
>
>  *1* Keep copyright statements [no problem, we'd do the same for anything]
>  *2* Identify the original author [I'd expect the copyright statement
>  to do that, but maybe there if is none then we could slip up here]
>  *3* Sponsor if supplied [This is the one I wouldn't expect us to
>  usually look for]
>  *4* Title if supplied [It would get named in some way]
>  *5* URL
>  *6* Derivative work statement [This would then be in ASF source rather
>  than a 3rd party dependency and would go in the NOTICE]
>
>  Summarizing, we would generally do 1 and 6 by default. It seems
>  unlikely that we would not cover 2 and 4, unlikely that 3 happens very
>  often and quite likely that we would link to the URL.
>
>  Maybe however we should have a defined format for a third party notice
>  file. All of the above are good ideas (except sponsor) for any third
>  party dependency and having a common format for such things across our
>  projects seems good. I've seen some xml files in oss projects recently
>  (I think they were JBoss ones) so it might be that there is a nascent
>  standard available. Maven have also been digging into such things,
>  though they've been putting it in the NOTICE.
>
>  Hen
>
>
>  On Thu, May 29, 2008 at 12:15 AM, Gilles Scokart <gscokart@gmail.com> wrote:
>  > What about the attribution : "You must attribute the work in the
>  > manner specified by the author or licensor (but not in any way that
>  > suggests that they endorse you or your use of the work)."
>  >
>  >
>  >
>  > 2008/5/29 Henri Yandell <bayard@apache.org>:
>  >> On Wed, May 28, 2008 at 5:08 PM, Sam Ruby <rubys@intertwingly.net> wrote:
>  >>> On Wed, May 28, 2008 at 4:37 PM, Craig L Russell <Craig.Russell@sun.com> wrote:
>
> >>>> I don't have any problem with depending on a CC licensed artifact...
>
>
>  ---------------------------------------------------------------------
>  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
>
>

---------------------------------------------------------------------
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