Re-license project as LGPLv3#56
Merged
Merged
Conversation
Contributor
|
Sounds good from my side. Approved. |
Member
|
Approved from me |
Member
Author
|
Thanks all! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR changes the license of this project from GPLv3 to LGPLv3.
Explanation
The intent of using the copyleft GPLv3 license was to encourage PeakRDL community growth, and protect this library from being copied and re-distributed privately for profit. One unintended side-effect of GPLv3 is that it technically mandates that any program linking to this work (referencing this as a Python library/dependency) shall also be GPL-compatible. For Python libraries, this ends up being a pretty intrusive restriction, and was never my original intent.
Changing the license to LGPLv3 specifically removes this restriction. Wikipedia has a good summary on the difference.
Approvals Required
Despite this being a very minor change, it is considered good legal practice to get the approval of all contributors whose code would be impacted by the license change.
If your name is listed below, please comment in this PR explicitly approving the change from GPLv3 to LGPLv3.