search

crystal-lang / shards

Dependency manager for the Crystal language
Other
765 stars 100 forks source link

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

Open Calinou opened 6 years ago

Calinou commented 6 years ago

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 commented 5 years ago

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 commented 5 years ago

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

ysbaddaden commented 5 years ago

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.

RX14 commented 5 years ago

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

ysbaddaden commented 5 years ago

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

bcardiff commented 4 years ago

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