[
https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633683#comment-14633683
]
Flavio Junqueira commented on ZOOKEEPER-2235:
---------------------------------------------
I've attached a patch that reflects my understanding of the Apache HOWTO for
assembling LICENSE and NOTICE files:
http://www.apache.org/dev/licensing-howto.html
According to this page, there is no need to change NOTICE or LICENSE for
dependencies under ALv2, unless there are transitive dependencies that need to
be bubbled up. The relevant quote is:
{quote}
Assuming once again that that the bundled dependency itself contains no bundled
subcomponents under other licenses and thus the ALv2 applies uniformly to all
files, there is no need to modify LICENSE.
If the dependency supplies a NOTICE file, its contents must be analyzed and the
relevant portions bubbled up into the top-level NOTICE file.
{quote}
The latest patch does not reflect an analysis of the bundled dependencies,
that's the main reason why I haven't submitted the patch to kick off the
workflow.
There are 4 dependencies, which are not under ALv2, and I've included license
files for them and added notes to the LICENSE file. The relevant quote from the
HOWTO page is this:
{quote}
Bundling a dependency which is issued under one of the following licenses is
straightforward, assuming that said license applies uniformly to all files
within the dependency:
BSD (without advertising clause)
MIT/X11
In LICENSE, add a pointer to the dependency's license within the source tree
and a short note summarizing its licensing:
This product bundles SuperWidget 1.2.3, which is available under a
"3-clause BSD" license. For details, see deps/superwidget/.
Under normal circumstances, there is no need to modify NOTICE.
{quote}
As far as I can tell, none of the BSD dependencies has the advertising clause.
Finally, servlet-api is under the CDDL license, and according to LUCENE-4431,
we need an entry added to NOTICE, which I did.
What's missing?
# It'd be great to have another pair of eyes validating my analysis.
# We need to go over NOTICE files in the dependencies and determine if there is
anything that needs to bubble up to our main LICENSE/NOTICE.
I'd really appreciate some help with these.
> License update
> --------------
>
> Key: ZOOKEEPER-2235
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2235
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.4.6, 3.5.0
> Reporter: Flavio Junqueira
> Assignee: Flavio Junqueira
> Priority: Blocker
> Fix For: 3.4.7, 3.5.1
>
> Attachments: ZOOKEEPER-2235.patch, ZOOKEEPER-2235.patch,
> ZOOKEEPER-2235.patch
>
>
> Updating license files and notice.txt as needed. Here is a list of the jars
> we are currently bundling with the release artifact with the corresponding
> license:
> # commons-cli-1.2.jar -- ASF
> # javacc.jar -- BSD license
> # jline-2.11.jar -- BSD license
> # servlet-api-2.5-20081211.jar - CDDL
> # jackson-core-asl-1.9.11.jar -- ALv2
> # jetty-6.1.26.jar -- ALv2
> # log4j-1.2.16.jar -- ALv2
> # jackson-mapper-asl-1.9.11.jar -- ALv2
> # jetty-util-6.1.26.jar -- ALv2
> # netty-3.7.0.Final.jar -- ALv2
> # slf4j-log4j12-1.7.5.jar -- MIT
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
