README: clarify license #1211
Merged
README: clarify license #1211
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I stumbled on this issue because PTXdist specifies "LGPL-2.1-only" as software license in rules/rauc.make, which does not match the license in RAUC's meson.build or in meta-rauc. |
jluebbe
previously approved these changes
Aug 8, 2023
rohieb
force-pushed
the
license-clarification
branch
from
e7cbfb2
to
c138799
Compare
ejoerns
reviewed
Aug 8, 2023
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #1211 +/- ##
==========================================
+ Coverage 80.16% 80.29% +0.13%
==========================================
Files 58 61 +3
Lines 18176 18401 +225
==========================================
+ Hits 14570 14775 +205
- Misses 3606 3626 +20 ☔ View full report in Codecov by Sentry. |
Simply including the LGPL license text is not enough information to determine the license of a software project, as Section 13 of the LGPL allows licensees to choose the terms of "any later version of the license" if specified so by the copyright holders. The information in meson.build implies "LGPL-2.1-or-later" as project license. As a minimal measure to make this information explicit, add the usual license notice and warranty disclaimer as recommended in the GNU GPL How-To to the README file, and also add a minimal copyright notice as required by Section 1 of the LGPL. Let the LGPL badge at the start of the README point to the relevant section further down. Link: https://www.gnu.org/licenses/gpl-howto.html#why-license-notices Link: https://www.gnu.org/licenses/identify-licenses-clearly.html Signed-off-by: Roland Hieber <rhi@pengutronix.de>
rohieb
force-pushed
the
license-clarification
branch
from
c138799
to
b200025
Compare
jluebbe
approved these changes
Aug 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simply including the LGPL license text is not enough information to determine the license of a software project, as Section 13 of the LGPL allows licensees to choose the terms of "any later version of the license" if specified so by the copyright holders.
The information in meson.build implies "LGPL-2.1-or-later" as project license. As a minimal measure to make this information explicit, add the usual license notice and warranty disclaimer as recommended in the GNU GPL How-To (also see [https://www.gnu.org/licenses/identify-licenses-clearly.html]) to the README file, and also add a minimal copyright notice as required by Section 1 of the LGPL.
Let the LGPL badge at the start of the README point to the relevant section further down.