You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently SPDX license identifiers are encouraged, with #22 required.
SPDX defines LicenseRef-.* to use custom licenses (See here and here).
I think cps should also define something so that custom license ids could be defined and used in the license expression so that custom licenses could be represented.
We could use the fields from https://spdx.github.io/spdx-spec/v2.2.2/other-licensing-information-detected/:
Maybe something like this:
{
"Name": "sample",
"Description": "Sample CPS",
"License": "LicenseRef-MyLicense",
"license-definitions": {
"LicenseRef-MyLicense": {
"name": "MyLicense maybe with special characters",
"see-also": "http://example.com/licenses/our-license",
"comment": "This is a comment",
"extracted-text": "Do whatever you want with this code"
}
}
}
The text was updated successfully, but these errors were encountered:
Currently SPDX license identifiers are encouraged, with #22 required.
SPDX defines
LicenseRef-.*
to use custom licenses (See here and here).I think cps should also define something so that custom license ids could be defined and used in the license expression so that custom licenses could be represented.
We could use the fields from https://spdx.github.io/spdx-spec/v2.2.2/other-licensing-information-detected/:
Maybe something like this:
The text was updated successfully, but these errors were encountered: