Optimize relationships to licenses
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 71
- Forks
- 44
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 7
Description
In SPDX 3.0, we moved to having relationships for all the licenses.
In addition, a license can be a simple license expression or a fully parsed license.
To remove redundancy, we should try to re-use existing relationships and/or existing licenses.
Discussed on the implementers call on 16 Oct 2024
Suggestion on the call - we create a relationship between the simple license expression to the complex license relationship - we could then identify similar expressions.
Contributor guide
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.
Research direction
No source file or test is named. Start by tracing the Java model and helpers for SPDX relationships and licenses, then review how simple license expressions and fully parsed licenses are represented. Done should be defined by the maintainers as a non-redundant relationship and license model, with tests covering equivalent or reusable objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100