Custom Licenses
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- json
- Domain
- tooling
Research direction
Start by reading the SPDX references linked in the issue and the requirements introduced by PR #22. Define how custom license identifiers and their metadata would be represented in the CPS specification, including the example fields and license expression usage. Done means the proposal is precise enough to implement and review.
Written by the indexing model from the issue text.
Description
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:
{
"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"
}
}
}
- Dominant language
- Python
- Stars
- 191
- Forks
- 13
- Avg merge
- 6d 23h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cps-org/cps
-
Spec: `c-runtime-vendor` field also should document the "musl" typical value and "bionic"Possibly taken @leha-bot claimed this 10 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 40/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google-agentic-commerce/AP2#388 ·
-
area:codegen backend:cuda backend:hip bug direction:input
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CrossGL/crosstl#3061 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
rlaope/oh-my-hermes#2304 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mochan-tk/agentic-dev-kit-for-codex#64 ·
Maintainers usually reply within 1 day
-
bug docs performance
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 3 days