-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Re-licensing libzmq #2376
Comments
Thanks for kickstarting the process again! |
I contributed a one-line update to some documentation, is it necessary to go through an entire license grant to handle that? |
@vielmetti this is the specific commit you contributed: 92b1b2b Since it is only documentation and not a major addition to libzmq it is not required for you to send in a license grant. |
Hi, I believe my submissions were two fixes to fix compiling the FreeBSD port of zeromq. One for GCC not liking a missing newline (zeromq/zeromq4-x@2ac32f8) and one for fixing compiling with the documentation option by just shifting code (zeromq/zeromq4-1@c75cc9e). I personally don't consider either significant enough of a contribution. Good on you folks. Good luck! |
I believe i don't have to sign it, or? just added a option to zmq_has afaik, but how can i find out my contributions? |
https://github.com/zeromq/libzmq/commits?author=Asmod4n It's a few lines, so if you don't mind it would be better to. Thanks! |
Could someone elaborate what the 2nd or 3rd options could mean? I currently like the MPLv2 the most, because its compatible to pretty much every other license? |
I like MPL2 as well and it's 99/99% what is going to end up being, but given we are going through this ordeal it's worth, if the contributor agrees, to keep the options open. |
Where are we with the relicensing process? Any ETA? |
No ETA, there are still many old contributors missing. |
@sigiesec let's try to be more disciplined on this - GitHub actually helps and tells if someone is a "first time contributor" so when we see that, let's ask for the grant before merging |
@bluca Ok, I will try too :) |
It's been some time ago since I've been working on this topic as well. At the time of sending out the first request to submit a grant, I've kept track of the responses but it should be updated to include new contributors from the past couple of months as well. I'm still busy this week but will try to restart this process somewhere next week. As @bluca mentioned it indeed would be good to ask first time contributors to submit a grant before merging ;) |
@rlenferink hi - I am looking at this again. Did you have a script or set of scripts to compile the checklist? I'd be happy to run them myself |
@soundart We still don't know what is preventing you from agreeing to the MPLv2. Martin Sustrik’s aka @sustrik —who submitted a lot to libzmq—has initiated nanomsg precisely for licensing reasons. He wrote (cp. Why Communication Infrastructure Should Use Permissive Licenses): Consider following use cases that would not be possible with GPL'd codebase:
Is there a reason why libzmq has to degenerate into a Museeums piece? |
@bluca As seen on @lalebarde account he was active on github this year. Did @lalebarde already respond concerning the re-licensing of libzmq to MPLv2? |
No answer so far |
566 grants to collect, work done within 5 years:
Is there a way to complete this task? @lalebarde @soundart @thijsterlouw @hshardeesi @guidog If you could please come forward and make a decision for the MPLv2. Thanks a lot. |
Instead of continuing to ask for relicensing statements from new PRs, it might be worth exploring the LLVM relicensing approach where all contributions after |
I have done some work to remove contributions from the authors who did not grant permissions: The two removed APIs can be made non-stubs again if somebody is able to provide a clean-room reimplementation (ie: without looking at the old code that was removed). I can review such implementations, but for obvious reasons I cannot provide them, as my knowledge is 'tainted'. |
Note that none of this is true. The new license will be MPL2, which is very much intentionally still share-alike, and in layman's terms, for all intents and purposes, provides the same terms as the current LGPL3 + custom exceptions. The main purpose is to use a 'standard' license (no custom exceptions) and harmonize with the rest of the zeromq projects which are already on MPL2. e.g.: the current license already allows using libzmq in proprietary products or networking hardware, and it already routinely happens. |
Should clean-room reimplementations of the removed features be backwards compatible in terms of how they are used? Eg code setting the CMake option for using tweetnacl, or using the reimplemented functions should continue to work without the user having to make changes to their code to use the new MPL implementations? |
Yes - note that I am referring to zmq_proxy_steerable() and ZMQ_RECONNECT_IVL_MAX. I don't see any point in adding back tweetnacl, it just causes problems and it's unsafe to use anyway. libsodium is available everywhere. I don't think anybody should spend any time on tweetnacl, but obviously I can't stop anyone from doing so. |
@lalebarde I see that you were active in the past week on Github, so one last chance to please give us permission to relicense your libzmq contributions to MPL-2.0. Your contributions are otherwise going to be deleted, and you will be removed from the zeromq Github organization. |
Relicense permission collected from all relevant authors as tallied at: https://github.com/rlenferink/libzmq-relicense/blob/master/checklist.md The relicense grants are collected under RELICENSE/ and will be moved to the above repository in a later commit. Fixes zeromq#2376
Relicense permission collected from all relevant authors as tallied at: https://github.com/rlenferink/libzmq-relicense/blob/master/checklist.md The relicense grants are collected under RELICENSE/ and will be moved to the above repository in a later commit. Fixes zeromq#2376
Relicensing has now been completed. |
@rlenferink could you please transfer ownership of the https://github.com/rlenferink/libzmq-relicense repository to me? I will then transfer it to the org here, and archive it |
Prob im - the author of ZMQ_RECONNECT_IVL_MAX |
@shripchenko assuming you have not sent a relicense grant, you could send one just to clarify any doubt, simply copy the following text in a new comment filling with your data, I'll do the rest:
|
Permission to Relicense under MPLv2This is a statement by Sergey KHripchenko aka @shripchenko A portion of the commits made by the Github handle "shripchenko", with Sergey KHripchenko |
@bluca I just transferred the repository to you for archival |
great, thank you, will fix a rebase mistake, add the license grant from above, move it to this org and archive it |
Hello libzmq contributors,
I'm starting this issue because of the current libzmq license. At the moment, libzmq is licensed as LGPL with static linking exception and this makes it a complex "one of a kind" license.
Almost a year ago the ZeroMQ project team started to collect license grants to re-license libzmq to a clearer license, namely the MPLv2. Collecting these license grants stopped for a while, because Pieter Hintjens, the former BDFL (Benevolent Dictator for Life) behind ZeroMQ, got sick and passed away.
We want to continue Pieter's work with collecting these contributor license grants. We want to ask you to send us a license grant to permit the libzmq to relicense to a different license. At the moment, libzmq is licensed as LGPL 3 with a static linking exception (http://zeromq.org/area:licensing). This makes it hard to make use of libzmq in projects with some other Open Source licenses (e.g. projects using the Apache License). The existing LGPL 3 with exceptions is also a non-standard license that some corporate lawyers are unwilling to accept for use in their companies.
For relicensing the libzmq project, we need to collect a license grant from each individual contributor who wrote a major piece of code in the development process of libzmq.
We are requesting contributors to send in a license grant to relicense libzmq to one of the options listed below:
If a contribution was made during working hours for an employer then we will also need a license grant (or "quit claim") from the employer.
We would like to follow a certain template as license grant to ensure all the necessary information is included. There are three templates, one for each option. Please choose the template that best represents your wishes.
The templates can be found at: https://github.com/zeromq/libzmq/tree/master/RELICENSE/templates
To include the license grant, please:
See the existing files in:
https://github.com/zeromq/libzmq/tree/master/RELICENSE
or this specific example: https://github.com/zeromq/libzmq/blob/master/RELICENSE/rlenferink.md
for a guide for how to fill out the template.
If there are any questions, don't hesitate to ask them below.
Roy
The text was updated successfully, but these errors were encountered: