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

Detecting licenses declared in LICENSE file and LICENSES folder #2214

Open
NicolasToussaint opened this issue Apr 27, 2022 · 1 comment
Open

Comments

@NicolasToussaint
Copy link
Member

Description

As discussed in Issue #1592, and to improve adoption of REUSE (https://reuse.software/) standards, Fossology could detect and display the licenses included in the LICENSE file, as well as licenses found in the LICENSES folder, both located in root folder.

The goal here is to process and report these license texts a bit differently compared to license texts found in other places in the source code. That will help verifying that the license texts are properly declared.

Steps followed and expected result

Rough idea, to be challenged :-)

  1. When clearing a file, specifically add an attribute to a license (Declared license ?)
    It could be a new icon next to the "Main License" yellow star, or a new column in this table:
    image
  2. When displaying the licenses lists, add a table recapping the "Declared" licenses, above Summary:
    image

Not sure if it should and how it could be used in the reports though.

@NicolasToussaint
Copy link
Member Author

NicolasToussaint commented Aug 16, 2022

Notes after discussion:

  • Every file in the LICENSES folder will be considered as a Declared License automatically, once it has been cleared.
  • The feature can be [de]activated via a new option in the Conf page (for each Upload) ; Feature activated by default for all new Uploads.
  • Add a new table in the Summary section of the Upload

To do next:

  • For every Declared License, find a way to show in the UI

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

No branches or pull requests

1 participant