Skip to content
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

Closed
Calinou opened this issue Aug 8, 2018 · 7 comments · Fixed by #641
Closed

Recommend the usage of SPDX license identifiers in the license field #221

Calinou opened this issue Aug 8, 2018 · 7 comments · Fixed by #641

Comments

@Calinou
Copy link

Calinou commented Aug 8, 2018

The specification currently states:

license

An OSI license name or an URL to a license file (String, recommended).

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.

@ysbaddaden
Copy link
Contributor

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.

@RX14
Copy link
Contributor

RX14 commented Jan 8, 2019

@ysbaddaden the SPDX URL makes it easier to find the indentifier for a licence, since it's all on one page.

@ysbaddaden
Copy link
Contributor

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 ysbaddaden added this to the v0.9.0 milestone Jan 9, 2019
@RX14
Copy link
Contributor

RX14 commented Jan 9, 2019

@ysbaddaden yeah that page is nice! I didn't see an OSI page like that before

@ysbaddaden
Copy link
Contributor

I'm not sure how to phrase the SPEC, thought.

@ysbaddaden ysbaddaden modified the milestones: v0.9.0, v0.10.0 Feb 9, 2019
@bcardiff
Copy link
Member

Removing this from milestone 0.10.0. When there is a PR this can be milestoned again.

@straight-shoota
Copy link
Member

Resolved by #641

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants