-
Notifications
You must be signed in to change notification settings - Fork 55
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
Change license to LGPL #26
Comments
So what might help here is creating a list of the people we know have accounts on GitHub. This way we can address at least that part of yey/ney. Also I would limit the significant contribution to anything above 5 lines of code. It is somewhat arbitrary number but looking at the commits that is where I would personally draw the line. I have tried to find some references from other projects but I was not successful finding those yet. Also anything below 50 lines of code should be easy to replace even if people in that contribution range do not agree with the license change.
I hope I added everyone based on the criteria I mentioned before. If you know anyone who has ??? next to their name, their github account nickname or have their email address/contact please add it in the comments here so we can approach them too. If your name is listed in that list please state in the comments that you agree with the license change from GPL to LGPL + linking exception as @gautierhattenberger mentioned. :) Then we can check off your name in the list. @gautierhattenberger you are welcome to take over my table into your post. Maybe that is the correct place to track progress of this issue. :) Cheers, |
I have no problem with the licence change. My understanding is that this is for pprzlink only - are you considering to change the licence for the rest of pprz too? |
As far as I understand this is only pprz link related. |
And I guess the motivation is so you can use pprzlink in other projects? |
Yes this will allow other projects including closed source ones to use PPRZLink linked into their codebase. This will allow in the future for more devices and software packages to interact with paparazzi based systems. This does not change the fact that if someone makes changes to PPRZLink and distribute it in any form including binary, they will have to publish their changes to the library. But it allows them to use the library non virally. |
For what it's worth, I'd be fine with the license change. On Jul 13, 2016 17:07, "Piotr Esden-Tempski" [email protected]
|
I have no problem with the license change 👍 |
I'm fine with everything. |
Fine for me for pprzlink |
I support changing the pprzlink license to LGPL with linking exception. |
I indeed agree with the license change |
I agree with the license change from GPLv3 to LGPL On 14 July 2016 at 10:42, Piotr Esden-Tempski [email protected]
|
We currently have GPLv2 (or later), updated it above... |
I agree |
I agree to the proposed license change. On Jul 14, 2016 1:55 AM, "Piotr Esden-Tempski" [email protected]
|
I agree with the license change |
I agree with this license change. |
i agree |
I agree. |
I agree with this license change |
I agree |
Agree |
I agree :-) |
I agree |
I agree. |
I agree |
1 similar comment
I agree |
Little late to the party, but I agree with and support the change in license. |
What is the status here? @gautierhattenberger @esden Waiting for @Drumettaz ? |
No, we may consider @Drumettaz contribution small (changing a few lines in message definition). |
unless someone with a good knowledge of licensing issues tells me it is not relevant here... |
@gautierhattenberger just a confirmation here - according to our company lawyer you were right and have to get in touch with Pascal's family to figure out to whom his copyright passed on. So no easy solution here:-/ |
Add license text Keep Ocaml, C code and generators in GPL Python is now in LGPL as discussed in #26
Add license text Keep Ocaml, C code and generators in GPL Python is now in LGPL as discussed in #26
Changing the license of PPRZLINK to LGPL (with proper exceptions for static linking https://en.wikipedia.org/wiki/GPL_linking_exception) would make integration into non-GPL code easier.
Below is a list (maybe not complete yet) of contributors extracted from git + file headers, for the current pprzlink repository and also from the former code previously integrated to Paparazzi (paparazzi/paparazzi@22ca426 and before)
Main contributors are well known and easy to reach. What about minor ones, former student and so on. Do we set a limit and where ?
The text was updated successfully, but these errors were encountered: