Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

report to list complex licenses in definitions #1097

Open
elrayle opened this issue Apr 17, 2024 · 1 comment
Open

report to list complex licenses in definitions #1097

elrayle opened this issue Apr 17, 2024 · 1 comment

Comments

@elrayle
Copy link
Collaborator

elrayle commented Apr 17, 2024

Description

Complex licenses may reflect the actual license, but also may reflect false positives coming from the tools generating the license data. Identifying complex licenses reveals licenses that may benefit from human review and possible curation.

Write a utility to generate a report from ClearlyDefined data listing complex licenses.

Considerations:

  • define complex (e.g. any license with an AND, any license with more than one connector, etc.) - are there other characteristics that can be used to identify complex licenses?
  • consider presentation (e.g. group licenses by the number of connectors with the most appearing first)
  • determine a way to mark a license as verified to prevent it from showing up on a future report if a human has reviewed it and finds it to be correct
@elrayle
Copy link
Collaborator Author

elrayle commented Dec 17, 2024

Backfill

The proposed work to create a report addresses the need to identify existing definitions that could benefit from curation. This would be resource intensive and is more of a backfill procedure that would not be repeated.

Operational

To assist with the ongoing need for curation, the following can be done at definition compute time.

When a complex license is identified during compute definition, check if there were curations for other versions.

  • IF a curation doesn't exist
    • create an issue requesting human review and possible curation
  • ELSE
    • IF all versions have the same license, create a PR with that license for the new version reducing the work to review, approve, and merge
    • ELSE create an issue and link to the existing curation file to assist human exploration and possible curation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant