Open autoantwort opened 10 months ago
Currently SPDX license identifiers are encouraged, with https://github.com/cps-org/cps/pull/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:
LicenseRef-.*
{ "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" } } }
Currently SPDX license identifiers are encouraged, with https://github.com/cps-org/cps/pull/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: