Sugestion: register this as a SPDX license
Lucas-C opened this issue · 2 comments
In order to foster the adoption of this license, I suggest that it is formalized as a SPDX document.
Quoting https://spdx.github.io/spdx-spec/1-rationale/:
The Software Package Data Exchange (SPDX®) specification is a standard format for communicating the component and metadata information associated with software packages. An SPDX file can be associated with a set of software packages, set of files or snippets and contains information about the software in the SPDX format described in this specification.
Quoting https://spdx.org/licenses/:
The SPDX License List is a list of commonly found licenses and exceptions used in free and open source and other collaborative software or documentation. The purpose of the SPDX License List is to enable easy and efficient identification of such licenses and exceptions in an SPDX document, in source files or elsewhere. The SPDX License List includes a standardized short identifier, full name, vetted license text including matching guidelines markup as appropriate, and a canonical permanent URL for each license and exception.
There are some detailed information on how to submit a new license here:
https://github.com/spdx/license-list-XML/blob/master/CONTRIBUTING.md#request-a-new-license-or-exception-be-added-to-the-spdx-license-list
It could also be submitted on https://tldrlegal.com
+1. For NPM NodeJS package authors, until this is done there's an active discouragement from using non-standard licenses (npm complains about an invalid SPDX license if you try setting "license": "Climate Strike (MIT)" in your package.json).
UPDATE - for anyone finding this, for now just do like this in your package.json:
{
"license" : "SEE LICENSE IN <filename>"
}
If you are using a license that hasn't been assigned an SPDX identifier, or if you are using a custom license, use a string value like this one… (see https://docs.npmjs.com/cli/v8/configuring-npm/package-json#license)