Skip to content

Re-license project as LGPLv3 #146

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Re-license project as LGPLv3 #146

wants to merge 1 commit into from

Conversation

amykyta3
Copy link
Member

@amykyta3 amykyta3 commented Jun 19, 2025

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.

Honorable Mentions

The following users are exempt from approval since their contributions did not impact code that would be affected by this change. Nonetheless, we appreciate their support!

  • jeremiah
  • motchy869

@Risto97
Copy link
Contributor

Risto97 commented Jun 19, 2025

Hello @amykyta3 ,

I welcome the decision, I think LGPLv3 is a good choice for the tool, it resolves some issues when using regblock in commercial environments.
I approve the change of license.

Best regards,
Risto.

@proukema-fidus
Copy link
Contributor

Seems good to me. I approve of the license change.

@mtdudek
Copy link
Contributor

mtdudek commented Jun 19, 2025

I'm also in favor of this decision and I approve the change of license.

@darsor
Copy link
Member

darsor commented Jun 19, 2025 via email

@hughjackson
Copy link
Contributor

This sounds like a positive change to me! I approve.

@amykyta3
Copy link
Member Author

@apstrike & @mkahane can you review and comment?

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

Successfully merging this pull request may close these issues.

6 participants