spdx / spdx/LicenseListPublisher
Utilize the OSI API's to automatically populate the isOsiApproved flag in the listed license
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 23
- Forks
- 29
- Avg merge
- 6h 31m
- Merged PRs (30d)
- 2
Description
https://api.opensource.org/licenses/ can access the SPDX license ID and OSI status. This can be used to do one of the following:
- Fill in the OSI approved text on spdx.org/licenses based on JavaScript and real time access to the OSI API and deprecate the isOsiApproved attribute in the license list XML
- Set the value for osiApproved in the listed licenses based on the OSI API information at the time the license list is generated and deprecate the isOsiApproved attribute in the license list XML
- Continue to use the isOsiApproved attribute in the license list XML, but generate a warning if the OSI API does not agree with the isOsiApproved XML attribute value.
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
Start with the LicenseListPublisher generation path described in the repository and trace how isOsiApproved is read from the license-list-XML source. Review the OSI API response for SPDX license IDs and OSI status, then resolve which of the three proposed approaches is intended. Done means the generated license data reflects the chosen synchronization behavior and any deprecation or warning behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100