[
https://issues.apache.org/jira/browse/SPARK-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908038#comment-14908038
]
Apache Spark commented on SPARK-10833:
--------------------------------------
User 'srowen' has created a pull request for this issue:
https://github.com/apache/spark/pull/8919
> Inline, organize BSD/MIT licenses in LICENSE
> --------------------------------------------
>
> Key: SPARK-10833
> URL: https://issues.apache.org/jira/browse/SPARK-10833
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.5.0
> Reporter: Sean Owen
> Assignee: Sean Owen
>
> In the course of https://issues.apache.org/jira/browse/LEGAL-226 it came to
> light that the guidance at
> http://www.apache.org/dev/licensing-howto.html#permissive-deps means that
> permissively-licensed dependencies has a different interpretation than we
> (er, I) had been operating under. "pointer ... to the license within the
> source tree" specifically means a copy of the license within Spark's
> distribution, whereas at the moment, Spark's LICENSE has a pointer to the
> project's license in the *other project's* source tree.
> The remedy is simply to inline all such license references (i.e. BSD/MIT
> licenses) or include their text in "licenses" subdirectory and point to that.
> Along the way, we can also treat other BSD/MIT licenses, whose text has been
> inlined into LICENSE, in the same way.
> The LICENSE file can continue to provide a helpful list of BSD/MIT licensed
> projects and a pointer to their sites. This would be over and above including
> license text in the distro, which is the essential thing.
> I do not think this blocks a current release, since there's a good-faith
> argument that the current practice satisfies the terms of the third-party
> licenses as well. (If it didn't, this would be a blocker for any further
> release.) However, of course it's better to follow the best practice going
> forward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
