Break up old/new license & clarify what we use #3548
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @yorickpeterse, that looks more clear. |
brixen
added a commit
that referenced
this pull request
Jan 3, 2016
Break up old/new license & clarify what we use
|
Thanks, @yorickpeterse! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I decided to move the BSD license to a separate file as I feel uncomfortable adding any extra clauses to the MPL 2.0 license. I also feel it would be too easy to miss the BSD license at the bottom of the already long MPL 2.0 license. As far as I'm aware the BSD license does not disallow renaming license files, thus I believe we should be fine.
cc @brixen @hintjens