Skip to content

cli/supported_licenses: simplify the license list #1150

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

perillo
Copy link
Contributor

@perillo perillo commented Mar 14, 2025

Remove the license reference, since it may not fit the terminal.

Move the license name before the license id, in order to improve the user experience.

Make the text width dynamic, in order to improve readability.

  • Added a change log entry in changelog.d/<directory>/.
  • Added self to copyright blurb of touched files.
  • Added self to AUTHORS.rst.
  • Wrote tests.
  • Documented my changes in docs/man/ or elsewhere.
  • My changes do not contradict
    the current specification.
  • I agree to license my contribution under the licenses indicated in the
    changed files.

Remove the license reference, since it may not fit the terminal.

Move the license name before the license id, in order to improve the
user experience.

Make the text width dynamic, in order to improve readability.
@perillo
Copy link
Contributor Author

perillo commented Mar 14, 2025

I started to use REUSE and I noted that the supported_licenses command it not very user friendly.

Each lines are too long, and on sway + foot I'm unable to select the license URL.

So I decided to remove the license reference.

If you agree to this change, it should possible to add an option to show all the details of a single license, with all supported metadata like link, OSI approved and FSFLibre approved;
see https://github.com/spdx/license-list-data/blob/main/licenses.md as an examples.

It would be useful to add filters based on OSI and FSFLibre compliance.

Thanks.

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

Successfully merging this pull request may close these issues.

1 participant