Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 16 May 2016 15:26:12 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12969961.1463392287000.197517.1463412372904@Atlassian.JIRA>
In-Reply-To: <JIRA.12969961.1463392287000@Atlassian.JIRA>
References: <JIRA.12969961.1463392287000@Atlassian.JIRA> <JIRA.12969961.1463392287252@arcas>
Subject: [jira] [Commented] (VFS-611) Clarify NOTICE is not required for
 JcrUtils from JackRabbit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 16 May 2016 15:26:19 -0000


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

Josh Elser commented on VFS-611:
--------------------------------

Thanks for the quick reply, [~busbey].

bq. We have to reproduce whatever parts of the NOTICE file are relevant. If the Day Software part isn't (and it sounds like it isn't), then all we need to do is make sure our NOTICE file has an appropriate copyright year span. If this file showed up in JackRabbit in 2009, then our current range of 2002 - present should cover it.

Yeah, I see this now -- ran into this same situation copying a Thrift source file into Accumulo. If we're copying a file from another ASF project, we should propagate the fact that we did this from Jackrabbit into our NOTICE (but not the "Day Software" piece). Does this jive with you [~sebb@apache.org]?

bq. If we're not going to call out the file as having provenance from outside of our project in NOTICE, then we should make a note in the file itself about the above so that in the future folks reviewing things don't have to deduce this for themselves. Perhaps a expanding the "copied from" note to include a reference to this JIRA?

SGTM. I'd guess if we need to reroll 2.1, we can clarify this too? If [~stain] doesn't beat me to it, I'll try to do this tonight.

> Clarify NOTICE is not required for JcrUtils from JackRabbit
> -----------------------------------------------------------
>
>                 Key: VFS-611
>                 URL: https://issues.apache.org/jira/browse/VFS-611
>             Project: Commons VFS
>          Issue Type: Task
>    Affects Versions: 2.1
>            Reporter: Stian Soiland-Reyes
>            Assignee: Stian Soiland-Reyes
>            Priority: Blocker
>             Fix For: 2.1
>
>
> In reviewing an RC for Apache Commons VFS 2.1
> https://lists.apache.org/thread.html/Zjouqd6cpmohrj3
> we wondered about a file
> https://github.com/apache/commons-vfs/blob/trunk/core/src/test/java/org/apache/commons/vfs2/provider/webdav/test/JcrUtils.java
> which we have adapted from Jackrabbit 2.4.0.
> Jackrabbit has a NOTICE which includes
> > Based on source code originally developed by
> > Day Software (http://www.day.com/).
> Looking at the git history
> https://github.com/apache/jackrabbit/commits/trunk/jackrabbit-jcr-commons/src/main/java/org/apache/jackrabbit/commons/JcrUtils.java
> I think this file was earliest added in JackRabbit in 2009 by Jukka Zitting:
> https://github.com/apache/jackrabbit/commit/0882a5cc1ed4ce1cf9d3c6b3a592f97c5772ce25
> (first released in 1.6.0 and 2.0-alpha1 )
> We believe that as this file was added 3 years after graduating from the Incubator it is not covered by the "Day Software" NOTICE requirement and is just made by Apache Software Foundation - in which case no special self-attribution is needed in VFS's NOTICE file.
> I've asked on dev@jackrabbit just to verify:
> https://lists.apache.org/thread.html/Zk01ufa8icmfvo8


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