Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Thu, 7 Jul 2016 17:56:10 +0000 (UTC)
From: "Dennis E. Hamilton (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.12987544.1467912411000.50329.1467914170979@Atlassian.JIRA>
In-Reply-To: <JIRA.12987544.1467912411000@Atlassian.JIRA>
References: <JIRA.12987544.1467912411000@Atlassian.JIRA> <JIRA.12987544.1467912411206@arcas>
Subject: [jira] [Comment Edited] (LEGAL-262) NOTICE requirements of
 dependencies with overly verbose NOTICE files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 07 Jul 2016 17:56:13 -0000


    [ https://issues.apache.org/jira/browse/LEGAL-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366496#comment-15366496 ] 

Dennis E. Hamilton edited comment on LEGAL-262 at 7/7/16 5:55 PM:
------------------------------------------------------------------

I think cleaning out inherited NOTICE information that is not relevant is a good idea (and one might want to suggest that to the dependencies that are on Apache project code).

However, there is a common misunderstanding that it is important to underline. The ASF does not require, nor does it obtain, copyright transfers in its receipt of contributions.  It obtains licenses from those who do have the exclusive rights that pertain to copyright holders.

That is why it is inappropriate to remove in-the-code copyright notices of third parties, except under the provisions that are established for that being done.

And, of course, IANAL

That is why, at the code file level, the stock ASF Notice is *not* a copyright notice (and should not be described as such).  It is a license notice.

ASF copyright can subsist in the releases made by Apache projects, but that applies only to the original ASF-project bits and not bits in which the copyright of others subsist.


was (Author: orcmid):
I think cleaning out inherited NOTICE information that is not relevant is a good idea (and one might want to suggest that to the dependencies that are on Apache project code).

However, there is a common misunderstanding that it is important to underline. The ASF does not require, nor does it obtain, copyright transfers in its receipt of contributions.  It obtains licenses from those who do have the exclusive rights that pertain to copyright holders.

That is why it is inappropriate to remove in-the-code copyright notices of third parties, except under the provisions that are established for that being done.

That is why, at the code file level, the stock ASF Notice is *not* a copyright notice (and should not be described as such).  It is a license notice.

ASF copyright can subsist in the releases made by Apache projects, but that applies only to the original ASF-project bits and not bits in which the copyright of others subsist.

> NOTICE requirements of dependencies with overly verbose NOTICE files
> --------------------------------------------------------------------
>
>                 Key: LEGAL-262
>                 URL: https://issues.apache.org/jira/browse/LEGAL-262
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andrew Wang
>
> We're working on cleaning up our L&N over at HADOOP-12893. One question that came up is what we should add to our NOTICE for dependencies that have overly verbose NOTICE files.
> For example, this is the Jetty NOTICE file:
> https://github.com/eclipse/jetty.project/blob/jetty-9.3.x/NOTICE.txt
> It lists out its dependencies and licenses, but that's not what NOTICE is for. We also already have LICENSE and NOTICE entries for all of these transitive dependencies.
> This is the Xerces NOTICE:
> https://svn.apache.org/repos/asf/xerces/java/trunk/NOTICE
> We're also an Apache project, so it seems like the ASF lines are unnecessary. The copyright attributions also seem potentially unnecessary, considering this code was donated to the ASF when it became an ASF project.
> Finally, here is the snappy-java NOTICE:
> https://github.com/xerial/snappy-java/blob/master/NOTICE
> These don't look like legally required notices either. 3-clause BSD doesn't require a NOTICE IIUC, we don't need to NOTICE our own code from Hadoop, and listing contributors isn't what NOTICE is for either. Not sure about the statically linked libstdc++, but LEGAL-230 did clear snappy-java for ASF use.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org