Relicensing k-wave-python from GPL-3.0 to LGPL-3.0: Contributor Permission Request #525
Replies: 18 comments 1 reply
-
|
I, Walter Simson, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Fabian Schneider, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Kevin Tritz, hereby give permission for my contributions to
k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I
have the legal right to grant this permission for all my contributions to
the project.
…On Sun, Dec 8, 2024 at 1:16 PM Walter Simson ***@***.***> wrote:
Relicensing k-wave-python from GPL-3.0 to LGPL-3.0: Contributor Permission
Request
Since the topic was raised from some of our users, we're planning to
change our package's license from GPL-3.0 to LGPL-3.0 to enable broader use
while maintaining core freedoms and aligning with k-wave's licensing. This
change requires permission from all contributors.
How to Give Permission
If you've contributed to this project, please comment below with:
I, [Your Full Name], hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project.
Current Status Contributors Pending Response
- @waltsims <https://github.com/waltsims> (Walter Simson)
- @faridyagubbayli <https://github.com/faridyagubbayli> (Farid
Yagubbayli)
- @djps <https://github.com/djps> (David Sinden)
- @precicely <https://github.com/precicely>
- @peterhollender <https://github.com/peterhollender> (Peter Hollender)
- @guillefix <https://github.com/guillefix> (Guillermo Valle)
- @talg2324 <https://github.com/talg2324>
- @sepehrnour <https://github.com/sepehrnour> (Sepehr)
- @ktritz <https://github.com/ktritz>
- @brubbel <https://github.com/brubbel>
- @gordon <https://github.com/gordon> (Gordon Stevenson)
- @faberno <https://github.com/faberno> (Fabian Schneider)
- @KR616 <https://github.com/KR616> (Kai Riemer)
- @void-mckenzie <https://github.com/void-mckenzie> (Mukkesh Ganesh)
- @bvale1 <https://github.com/bvale1> (Billy Vale)
Permissions Received
- None yet
[Will be updated as people respond]
Timeline
- Response Period: December 8th, 2024 to December 22nd, 2024
- Planned License Change: December 24th, 2024
FAQ
*Q: Why align with k-wave's license?*
A: Since k-wave-python is a derived work of k-wave, which uses LGPL-3.0,
aligning our license provides consistency in the ecosystem and clearer
terms for users of both packages.
*Q: What exactly changes with LGPL-3.0?*
A: Currently under GPL-3.0, any project that imports our package must also
be GPL-3.0. With LGPL-3.0, others can import and use our package while
keeping their code under any license they choose. Here's what this means in
practice:
# This becomes allowed under any license with LGPL-3.0:from kwave import Medium, Sensordef user_code():
medium = Medium() # Only our package remains copyleft
# User's code can be any license
*Q: How does this affect different Python use cases?*
A: The LGPL-3.0 license allows:
- Combining with other open source projects regardless of their license
- Using the package in commercial Python applications
- Including in internal company tools
*Q: What if someone modifies the package?*
A: Any modifications to our package's source code must still be shared
under LGPL-3.0. The copyleft protection remains for our code, while
allowing flexible usage of the package as a dependency.
*Q: Does this affect PyPI distribution?*
A: No, the package will still be distributed the same way through pip.
Only the usage terms change, becoming more permissive.
*Q: What about existing projects using the package?*
A: This change only makes the license less restrictive, so existing
projects can continue using the package as before, with more flexibility.
Next Steps
1. We'll keep this discussion pinned until December 22nd, 2024
2. We'll follow up via email with contributors who haven't responded
3. Once we receive all permissions, we'll update the license and tag a
new release
Please feel free to ask questions or raise concerns in this discussion.
—
Reply to this email directly, view it on GitHub
<#525>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIR6YNMS4B2JSSEB2UAOUL2ESEHBAVCNFSM6AAAAABTHOK4XGVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGYZTIMRWGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I, Mukkesh Ganesh, hereby give permission for my contributions to
k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I
have the legal right to grant this permission for all my contributions to
the project.
…On Sun, Dec 8, 2024, 10:16 AM Walter Simson ***@***.***> wrote:
Relicensing k-wave-python from GPL-3.0 to LGPL-3.0: Contributor Permission
Request
Since the topic was raised from some of our users, we're planning to
change our package's license from GPL-3.0 to LGPL-3.0 to enable broader use
while maintaining core freedoms and aligning with k-wave's licensing. This
change requires permission from all contributors.
How to Give Permission
If you've contributed to this project, please comment below with:
I, [Your Full Name], hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project.
Current Status Contributors Pending Response
- @waltsims <https://github.com/waltsims> (Walter Simson)
- @faridyagubbayli <https://github.com/faridyagubbayli> (Farid
Yagubbayli)
- @djps <https://github.com/djps> (David Sinden)
- @precicely <https://github.com/precicely>
- @peterhollender <https://github.com/peterhollender> (Peter Hollender)
- @guillefix <https://github.com/guillefix> (Guillermo Valle)
- @talg2324 <https://github.com/talg2324>
- @sepehrnour <https://github.com/sepehrnour> (Sepehr)
- @ktritz <https://github.com/ktritz>
- @brubbel <https://github.com/brubbel>
- @gordon <https://github.com/gordon> (Gordon Stevenson)
- @faberno <https://github.com/faberno> (Fabian Schneider)
- @KR616 <https://github.com/KR616> (Kai Riemer)
- @void-mckenzie <https://github.com/void-mckenzie> (Mukkesh Ganesh)
- @bvale1 <https://github.com/bvale1> (Billy Vale)
Permissions Received
- None yet
[Will be updated as people respond]
Timeline
- Response Period: December 8th, 2024 to December 22nd, 2024
- Planned License Change: December 24th, 2024
FAQ
*Q: Why align with k-wave's license?*
A: Since k-wave-python is a derived work of k-wave, which uses LGPL-3.0,
aligning our license provides consistency in the ecosystem and clearer
terms for users of both packages.
*Q: What exactly changes with LGPL-3.0?*
A: Currently under GPL-3.0, any project that imports our package must also
be GPL-3.0. With LGPL-3.0, others can import and use our package while
keeping their code under any license they choose. Here's what this means in
practice:
# This becomes allowed under any license with LGPL-3.0:from kwave import Medium, Sensordef user_code():
medium = Medium() # Only our package remains copyleft
# User's code can be any license
*Q: How does this affect different Python use cases?*
A: The LGPL-3.0 license allows:
- Combining with other open source projects regardless of their license
- Using the package in commercial Python applications
- Including in internal company tools
*Q: What if someone modifies the package?*
A: Any modifications to our package's source code must still be shared
under LGPL-3.0. The copyleft protection remains for our code, while
allowing flexible usage of the package as a dependency.
*Q: Does this affect PyPI distribution?*
A: No, the package will still be distributed the same way through pip.
Only the usage terms change, becoming more permissive.
*Q: What about existing projects using the package?*
A: This change only makes the license less restrictive, so existing
projects can continue using the package as before, with more flexibility.
Next Steps
1. We'll keep this discussion pinned until December 22nd, 2024
2. We'll follow up via email with contributors who haven't responded
3. Once we receive all permissions, we'll update the license and tag a
new release
Please feel free to ask questions or raise concerns in this discussion.
—
Reply to this email directly, view it on GitHub
<#525>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHLI5727NB7MN2NKEMUDMQL2ESEHDAVCNFSM6AAAAABTHOK4XGVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGYZTIMRWGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I, David Sinden, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Tal Grutman, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Kai Riemer, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project.
… On 8 Dec 2024, at 19:16, Walter Simson ***@***.***> wrote:
I, [Your Full Name], hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project.
|
Beta Was this translation helpful? Give feedback.
-
|
I, Sepehr Nourbakhsh, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Farid Yagubbayli, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Christopher Icely, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Billy Vale, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Guillermo Valle, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Peter Hollender, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
You tagged the wrong Gordon, you probably meant @gordon-n-stevenson. |
Beta Was this translation helpful? Give feedback.
-
|
I, Gordon Stevenson , hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, Ameya Deshmukh, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
I, brubbel, hereby give permission for my contributions to k-wave-python to be relicensed from GPL-3.0 to LGPL-3.0. I confirm that I have the legal right to grant this permission for all my contributions to the project. |
Beta Was this translation helpful? Give feedback.
-
|
Email sent with real name. |
Beta Was this translation helpful? Give feedback.
-
|
Dear contributors, Thank you all for approving the relicensing of k-wave-python from GPL-3.0 to LGPL-3.0. We will update the license on December 24th, 2024 with release v0.4.0. This change allows broader usage of k-wave-python and I look forward to our future progress on the project. Thank you, |
Beta Was this translation helpful? Give feedback.
-
Relicensing k-wave-python from GPL-3.0 to LGPL-3.0: Contributor Permission Request
Since the topic was raised from some of our users, we're planning to change our package's license from GPL-3.0 to LGPL-3.0 to enable broader use while maintaining core freedoms and aligning with k-wave's licensing. This change requires permission from all contributors.
How to Give Permission
If you've contributed to this project, please comment below with:
Since all contributions were made through GitHub, please respond using your GitHub account that made the original contributions - this will serve as verification of contributor identity.
Current Status
Contributors Pending Response
Permissions Received
[Will be updated as people respond]
Timeline
FAQ
Q: Why align with k-wave's license?
A: Since k-wave-python is a derived work of k-wave, which uses LGPL-3.0, aligning our license provides consistency in the ecosystem and clearer terms for users of both packages.
Q: What exactly changes with LGPL-3.0?
A: Currently under GPL-3.0, any project that imports our package must also be GPL-3.0. With LGPL-3.0, others can import and use our package while keeping their code under any license they choose. Here's what this means in practice:
Q: How does this affect different Python use cases?
A: The LGPL-3.0 license allows:
Q: What if someone modifies the package?
A: Any modifications to our package's source code must still be shared under LGPL-3.0. The copyleft protection remains for our code, while allowing flexible usage of the package as a dependency.
Q: Does this affect PyPI distribution?
A: No, the package will still be distributed the same way through pip. Only the usage terms change, becoming more permissive.
Q: What about existing projects using the package?
A: This change only makes the license less restrictive, so existing projects can continue using the package as before, with more flexibility.
Next Steps
Please feel free to ask questions or raise concerns in this discussion.
Beta Was this translation helpful? Give feedback.
All reactions