update license metadata to use SPDX identifier as per recommendation #125
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
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 a housekeeping code change suggestion. This project is released under the MIT license as per the
LICENSEfile's contents, however the current metadata notation makes handling that information harder than it should be.The PEP621's license field info generally recommends using a SPDX-compatible license identifier, which in this case is "MIT". Before this proposed change, other tools that use metadata-extraction (such as pip-licenses) hiccups on the license value on this library, not being able to infer that it's the same license as many other projects as well.
Given how licensing applies, I believe this should be without downside and any loss of clarity or control on the side of the project's creators, while having definite (even if niche) upside for the project's users. Happy to bring in examples from other MIT-licensed projects that use the same format.