GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/8919
[SPARK-10833] [BUILD] [WIP] Inline, organize BSD/MIT licenses in LICENSE
*Work in progress -- don't merge yet*
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srowen/spark SPARK-10833
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/8919.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #8919
----
commit b271388385c5724e7daa6c0e70a10102ce85e737
Author: Sean Owen <[email protected]>
Date: 2015-09-25T13:33:31Z
First step in BSD/MIT license update: move inlined BSD/MIT licenses from
LICENSE to a licenses/LICENSE-*.txt file
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
