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

Add full A/L/G PL/FDL texts to "plus"/"or-later" variants of the licenses #2327

Closed
pombredanne opened this issue Nov 18, 2020 · 4 comments
Closed

Comments

@pombredanne
Copy link
Member

Today we only have a notice for the text of the "or later" variants licenses.
Such as here: https://github.com/nexB/scancode-toolkit/blob/a78fda974392c08dfcec3a41a283a303a6978b46/src/licensedcode/data/licenses/gpl-2.0-plus.RULE
We want to also have the full text there.
I suggest simply to do this:

< text of the "or later" notice >
---------------------------------------
< full license text >
@pombredanne
Copy link
Member Author

@DennisClark FYI

@pombredanne
Copy link
Member Author

@chinyeungli this also means that these texts will be usable as-is in Attribution generation

@sankha555
Copy link
Contributor

Hello @pombredanne, I have tried to study the specifications of this issue and would like to work on it.

From what I understood in the specifications and seeing the license files in the codebase, I could find many "plus" variants of licenses. As an example, am I correct in understanding that it is required to append the gpl-1.0 license text after the notice in the gpl-1.0-plus.LICENSE file? There were many other examples like numerous variants of the gpl-2.0 license as well. If you think that I have understood the issue properly, could you please assign it to me and also provide other necessary inputs for the same? Thanks!

pombredanne added a commit that referenced this issue Feb 24, 2021
pombredanne added a commit that referenced this issue Feb 24, 2021
Add notice in text to avoid ambiguous detection per
#2327

Signed-off-by: Philippe Ombredanne <[email protected]>
pombredanne added a commit that referenced this issue Feb 24, 2021
pombredanne added a commit that referenced this issue Feb 24, 2021
@pombredanne
Copy link
Member Author

This has been fixed and merged. Closing

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

2 participants