-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommend the usage of SPDX license identifiers in the license
field
#221
Comments
The SPEC should specify a license identifier instead of name, because this is what we expect, and add some examples, such as Apache-2.0, MIT, BSD-3-clause, ... OSI and SPDX use the same identifiers , so that doesn't really matter and could link to both. |
@ysbaddaden the SPDX URL makes it easier to find the indentifier for a licence, since it's all on one page. |
Same for OSI: https://opensource.org/licenses/alphabetical expect that it's not just a list of opensource licenses. We can reference the blunt SPDX table, but I'd still like to keep referencing OSI, for example the https://opensource.org/licenses/category page, which is nicer. |
@ysbaddaden yeah that page is nice! I didn't see an OSI page like that before |
I'm not sure how to phrase the SPEC, thought. |
Removing this from milestone 0.10.0. When there is a PR this can be milestoned again. |
Resolved by #641 |
The specification currently states:
It could be a good idea to rely on SPDX license identifiers for common licenses out there, which would make it easier to parse license fields programmatically. This is encouraged by many other package managers already, such as Cargo.
The text was updated successfully, but these errors were encountered: