LICENSE: Reference third-party licenses #4800
Merged
Conversation
This file contains hidden or 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 for this. It is nice and concise, and at least gives an overview of the state of the licenses in the whole project. Users will of course need to dig deeper to read the full licenses/copyright to comply with them. |
tannewt
added a commit
to tannewt/circuitpython
that referenced
this pull request
May 27, 2021
Handle too many HID devices properly
ac872a0 to
2fa975c
Compare
This is to provide a summary of the licenses used by MicroPython. - Add SPDX identifier for every directory that includes non-MIT-licensed content. - Add brief summary. - Update docs license to be more explicit. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
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.
This is to provide a summary of the licenses used by MicroPython.
This was partially automated and cross-checked with the work by @dlech in #4432 I like the approach outlined there but my aim here is to provide a simple "at a glance" summary of just the licenses used and clarify the overall purpose of the root-level LICENSE file.
Related to #4363