search

paparazzi / pprzlink

Message and communication library for the Paparazzi UAV system
Other
24 stars 55 forks source link

Change license to LGPL #26

Open gautierhattenberger opened 8 years ago

gautierhattenberger commented 8 years ago

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@22ca42632644f7dd90ab79e0e8a5a737316a94b3 and before)

#### PAPARAZZI ####
git ls-tree -r -z --name-only HEAD -- conf/messages.* conf/units.xml sw/tools/generators/gen_messages.ml sw/airborne/subsystems/datalink/*transport* sw/airborne/subsystems/datalink/xbee* sw/airborne/subsystems/datalink/uart_print.h sw/lib/python/**/* sw/lib/ocaml/pprz.ml* sw/lib/ocaml/xbee.ml* sw/lib/ocaml/serial.ml* sw/lib/ocaml/logpprz.ml* sw/lib/ocaml/convert.c | xargs -0 -n1 git blame --line-porcelain HEAD |grep  "^author "|sort|uniq -c|sort -nr 
   3591 author Felix Ruess
   1882 author Gautier Hattenberger
   1718 author Pascal Brisset
   1169 author Antoine Drouin
    218 author Martin Mueller
    217 author Allen Ibara
    129 author Christophe De Wagter
     82 author Freek van Tienen
     61 author John Stowers
     27 author podhrmic
     27 author Cameron Lee
     26 author Oswald Berthold
     20 author Ewoud Smeur
     16 author dewagter
     15 author fvantienen
     12 author kirkscheper
     11 author Bruzzlee
      9 author Loic Drumettaz
      9 author Allen
      6 author Stephen Dwyer
      5 author Tobias Muench
      5 author LodewijkSikkel
      5 author agressiva
      4 author Pranay Sinha
      4 author karlito139
      3 author Paul Cox
      3 author guidoAI
      2 author Roland Meertens
      2 author rad
      2 author k.n.mcguire@tudelft.nl
      2 author Christoph Niemann
      1 author OSAM-UAV Team
      1 author Louis Dugrain
      1 author Eric Parsonage

grep "Copyright" conf/messages.* conf/units.xml sw/tools/generators/gen_messages.ml sw/airborne/subsystems/datalink/*transport* sw/airborne/subsystems/datalink/xbee* sw/airborne/subsystems/datalink/uart_print.h sw/lib/python/**/* sw/lib/ocaml/pprz.ml* sw/lib/ocaml/xbee.ml* sw/lib/ocaml/serial.ml* sw/lib/ocaml/logpprz.ml* sw/lib/ocaml/convert.c 
sw/tools/generators/gen_messages.ml: * Copyright (C) 2003-2008 ENAC, Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/downlink_transport.h: * Copyright (C) 2003-2010 The Paparazzi Team
sw/airborne/subsystems/datalink/ivy_transport.c: * Copyright (C) 2003  Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/ivy_transport.c: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/ivy_transport.h: * Copyright (C) 2003  Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/ivy_transport.h: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/pprzlog_transport.c: * Copyright (C) 2014 Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/pprzlog_transport.h: * Copyright (C) 2014 Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/pprz_transport.c: * Copyright (C) 2006  Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/pprz_transport.c: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/pprz_transport.h: * Copyright (C) 2003  Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/pprz_transport.h: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/transport.h: * Copyright (C) 2011-2014 Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/xbee24.h: * Copyright (C) 2009  ENAC, Pascal Brisset
sw/airborne/subsystems/datalink/xbee24.h: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/xbee868.h: * Copyright (C) 2009  ENAC, Pascal Brisset
sw/airborne/subsystems/datalink/xbee868.h: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/xbee.c: * Copyright (C) 2006  Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/xbee.c: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/xbee.h: * Copyright (C) 2006  Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/xbee.h: * Copyright (C) 2014  Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/airborne/subsystems/datalink/uart_print.h: * Copyright (C) 2005 Pascal Brisset, Antoine Drouin
sw/airborne/subsystems/datalink/uart_print.h: * Copyright (C) 2015 Gautier Hattenberger <gautier.hattenberger@enac.fr>
sw/lib/ocaml/pprz.ml: * Copyright (C) 2003 Pascal Brisset, Antoine Drouin
sw/lib/ocaml/pprz.mli: * Copyright (C) 2003 Pascal Brisset, Antoine Drouin
sw/lib/ocaml/xbee.ml: * Copyright (C) 2006 ENAC, Pascal Brisset, Antoine Drouin
sw/lib/ocaml/xbee.mli: * Copyright (C) 2006 ENAC, Pascal Brisset, Antoine Drouin
sw/lib/ocaml/serial.ml: * Copyright (C) 2004 CENA/ENAC, Pascal Brisset
sw/lib/ocaml/serial.mli: * Copyright (C) 2004 CENA/ENAC, Pascal Brisset
sw/lib/ocaml/logpprz.ml: * Copyright (C) 2003 Pascal Brisset, Antoine Drouin
sw/lib/ocaml/convert.c:   Copyright (C) 2004 Pascal Brisset, Antoine Drouin

#### PPRZLINK ####

git ls-tree -r -z --name-only HEAD -- **/* | xargs -0 -n1 git blame --line-porcelain HEAD |grep  "^author "|sort|uniq -c|sort -nr 
  10923 author Felix Ruess
   8295 author Gautier Hattenberger
    246 author Rijesh Augustine
     82 author HooperFly
     65 author kevindehecker
     50 author kirkscheper
     41 author Christophe De Wagter
     11 author Ewoud Smeur
      9 author Roland Meertens
      9 author guidoAI

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 ?

esden commented 8 years ago

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, Piotr

podhrmic commented 8 years ago

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?

esden commented 8 years ago

As far as I understand this is only pprz link related.

podhrmic commented 8 years ago

And I guess the motivation is so you can use pprzlink in other projects?

esden commented 8 years ago

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.

aibara commented 8 years ago

For what it's worth, I'd be fine with the license change.

On Jul 13, 2016 17:07, "Piotr Esden-Tempski" notifications@github.com wrote:

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.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/paparazzi/pprzlink/issues/26#issuecomment-232522178, or mute the thread https://github.com/notifications/unsubscribe/AAP3e2ZhYedX9myAMY8LAjaw23A_HjCAks5qVX3MgaJpZM4JL7w_ .

fvantienen commented 8 years ago

I have no problem with the license change 👍

rmeertens commented 8 years ago

I'm fine with everything.

martinmm commented 8 years ago

Fine for me for pprzlink

flixr commented 8 years ago

I support changing the pprzlink license to LGPL with linking exception.

gautierhattenberger commented 8 years ago

I indeed agree with the license change

nzjrs commented 8 years ago

I agree with the license change from GPLv3 to LGPL

On 14 July 2016 at 10:42, Piotr Esden-Tempski notifications@github.com wrote:

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 GPLv3 to LGPL + linking exception as @gautierhattenberger https://github.com/gautierhattenberger mentioned. :) Then we can check off your name in the list.

@gautierhattenberger https://github.com/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, Piotr

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/paparazzi/pprzlink/issues/26#issuecomment-232520348, or mute the thread https://github.com/notifications/unsubscribe/AACjo_VM8nzrYlA9elTsGrkSweTtZENaks5qVfZngaJpZM4JL7w_ .

flixr commented 8 years ago

We currently have GPLv2 (or later), updated it above...

EwoudSmeur commented 8 years ago

I agree

poine commented 8 years ago

I agree to the proposed license change.

On Jul 14, 2016 1:55 AM, "Piotr Esden-Tempski" notifications@github.com wrote:

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 GPLv3 to LGPL + linking exception as @gautierhattenberger https://github.com/gautierhattenberger mentioned. :) Then we can check off your name in the list.

@gautierhattenberger https://github.com/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, Piotr

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/paparazzi/pprzlink/issues/26#issuecomment-232520348, or mute the thread https://github.com/notifications/unsubscribe/AAGTz0TAUgnQ_5QC7Su9gQ5us2fUA1_nks5qVXr0gaJpZM4JL7w_ .

Bruzzlee commented 8 years ago

I agree with the license change

camlee commented 8 years ago

I agree with this license change.

x75 commented 8 years ago

i agree

rijesha commented 8 years ago

I agree.

dewagter commented 8 years ago

I agree with this license change

kirkscheper commented 8 years ago

I agree

LodewijkSikkel commented 8 years ago

Agree

TobiasMue commented 8 years ago

I agree :-)

guidoAI commented 8 years ago

I agree

hooperfly commented 8 years ago

I agree.

agressiva commented 8 years ago

I agree

kevindehecker commented 8 years ago

I agree

scdwyer commented 8 years ago

Little late to the party, but I agree with and support the change in license.

podhrmic commented 7 years ago

What is the status here? @gautierhattenberger @esden Waiting for @drumettaz ?

gautierhattenberger commented 7 years ago

No, we may consider @drumettaz contribution small (changing a few lines in message definition). Actually what we (Enac) need to do to close this is to get into contact with Pascal Brisset's family.

gautierhattenberger commented 7 years ago

unless someone with a good knowledge of licensing issues tells me it is not relevant here...

podhrmic commented 7 years ago

@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:-/