REUSE licenses. How to recognize this?

[dgarijo]

The REUSE specification allows for recognizing multiple licenses in part of a repo.

For example: https://github.com/softwarepub/hermes/tree/develop

How to recognize licenses of part of the repo? Documentation, logos, etc.

[dgarijo]

See https://github.com/EVERSE-ResearchSoftware/TechRadar/blob/main/REUSE.toml as well

[Anas-Elhounsri]

In the case of REUSE.toml, would it make sense to make SOMEF parse through the file collect the paths and the spdx concerned with it, and have a new element in LICENSE results where we point to these path and list the license related to it, Like this the users can know which parts of the project related to a specific spdx

[Anas-Elhounsri]

In the case of REUSE.toml, would it make sense to make SOMEF parse through the file collect the paths and the spdx concerned with it, and have a new element in LICENSE results where we point to these path and list the license related to it, Like this the users can know which parts of the project related to a specific spdx

With this we can address "How to recognize licenses of part of the repo? Documentation, logos, etc.", but in the other example, they used LICENSE.md, it will be tricky to make a stable implementation to extract it from this format

[Anas-Elhounsri]

The REUSE specification allows for recognizing multiple licenses in part of a repo.

For example: https://github.com/softwarepub/hermes/tree/develop

How to recognize licenses of part of the repo? Documentation, logos, etc.

Did some reading from their documentation, there are three ways to use REUSE specifications, header comments, REUSE.toml and dep5 file. When it comes to logos and files that cannot have comment headers they will have an adjacent file that has the same name with .license at the end, if not we will only expect it in the other two files which makes it straight forward. But if the user uses header comments for other commentable files, it will be tricky to detect these.

[dgarijo]

Please feel free to make a proposal and discuss it with me offline. We would need to see if additional properties are needed in case multiple licenses are declared (something like adding a scope for the license to indicate the affected files)

[dgarijo]

See https://github.com/oeg-upm/OOPS/tree/master as another example compliant with REUSE.
There is an open API which can be used to comply with the spec