Discussion:
relicensing libunistring to "dual LGPLv3+ or GPLv2"
(too old to reply)
Bruno Haible
2016-11-12 01:44:47 UTC
Permalink
Raw Message
Hi,

It has been decided that libunistring is going to be relicensed under
"dual LGPLv3+ or GPLv2" license. See
http://lists.gnu.org/archive/html/bug-libunistring/2016-11/msg00003.html

To this effect, the libunistring modules in gnulib that are currently under
LGPLv3+ need to be relicensed to 'LGPLv3+ or GPLv2'. Those modules that
are under LGPLv2+ stay under LGPLv2+.

1)
This proposed patch does this. It also extends gnulib-tool so that
* the option --lgpl accepts the form --lgpl=3orGPLv2
* the compatibility checks consider this 'LGPLv3+ or GPLv2' license
(namely, the allowed relicensings are:
LGPLv2+ --> 'LGPLv3+ or GPLv2'
'LGPLv3+ or GPLv2' --> LGPLv3+ = LGPL
'LGPLv3+ or GPLv2' --> GPLv2+
'LGPLv3+ or GPLv2' --> GPLv3+ = GPL

2)
Some libunistring modules depend on gnulib modules with an LGPL license:

unicase needs:

Module Authors of the lib/* files (modulo trivial changes)
memcmp2 Bruno
amemxfrm Bruno

unistdio needs:

Module Authors of the lib/* files (modulo trivial changes)

fpieee --
fpucw Bruno
frexpl-nolibm Bruno
frexp-nolibm Bruno
isnand-nolibm Bruno, Paul, Eric, Ludovic
isnanf-nolibm Bruno, Paul, Eric, Ludovic
isnanl-nolibm Bruno, Paul, Eric, Ludovic
printf-frexp Bruno
printf-frexpl Bruno
printf-safe --
signbit Bruno, Paul

I am willing to relicense these modules to 'LGPLv3+ or GPLv2' or to the even
weaker license LGPLv2+.

lib/float+.h is already under LGPLv2+, per the modules 'integer_length' and
'vasnprintf'.

=== Paul, Eric, Ludovic, ===

Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?

The history is here:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=history;f=lib/isnan.c

Bruno
--
In memoriam Moustapha Akkad <http://en.wikipedia.org/wiki/Moustapha_Akkad>
Paul Eggert
2016-11-12 01:51:03 UTC
Permalink
Raw Message
Post by Bruno Haible
Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
Yes, that's fine with me.
Ludovic Courtès
2016-11-12 11:09:41 UTC
Permalink
Raw Message
Hi Bruno,
Post by Bruno Haible
=== Paul, Eric, Ludovic, ===
Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
Yes, sure.

Ludo’.
Eric Blake
2016-11-12 19:32:54 UTC
Permalink
Raw Message
Post by Bruno Haible
Hi,
It has been decided that libunistring is going to be relicensed under
"dual LGPLv3+ or GPLv2" license. See
http://lists.gnu.org/archive/html/bug-libunistring/2016-11/msg00003.html
To this effect, the libunistring modules in gnulib that are currently under
LGPLv3+ need to be relicensed to 'LGPLv3+ or GPLv2'. Those modules that
are under LGPLv2+ stay under LGPLv2+.
1)
This proposed patch does this. It also extends gnulib-tool so that
* the option --lgpl accepts the form --lgpl=3orGPLv2
* the compatibility checks consider this 'LGPLv3+ or GPLv2' license
LGPLv2+ --> 'LGPLv3+ or GPLv2'
LGPL can always be tightened to GPL, and the + means it can be upgraded
from 2 to 3, so this is correct.
Post by Bruno Haible
'LGPLv3+ or GPLv2' --> LGPLv3+ = LGPL
This says you are picking only one of the two options, so it is correct.
Post by Bruno Haible
'LGPLv3+ or GPLv2' --> GPLv2+
This one is possible because LGPLv3+ can always be tightened to GPLv3+;
it is written GPLv2+ because of the GPLv2 option.
Post by Bruno Haible
'LGPLv3+ or GPLv2' --> GPLv3+ = GPL
And this says you are picking only the LGPLv3+ option, then tightening
it to GPLv3+.

Okay, I agree with all four of those transitions.
Post by Bruno Haible
=== Paul, Eric, Ludovic, ===
Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
I'd lean towards the more-permissive LGPLv2+, but 'LGPLv3+ or GPLv2' is
also fine.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
Bruno Haible
2016-11-13 02:57:54 UTC
Permalink
Raw Message
Hi Paolo,

For the 'frexpl-nolibm' module I also need your approval, since you
contributed lib/frexpl.c on 2003-02-18.

Would you agree to relicense your initial lib/frexpl.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?

Bruno
Post by Bruno Haible
It has been decided that libunistring is going to be relicensed under
"dual LGPLv3+ or GPLv2" license. See
http://lists.gnu.org/archive/html/bug-libunistring/2016-11/msg00003.html
To this effect, the libunistring modules in gnulib that are currently under
LGPLv3+ need to be relicensed to 'LGPLv3+ or GPLv2'. Those modules that
are under LGPLv2+ stay under LGPLv2+.
1)
This proposed patch does this. It also extends gnulib-tool so that
* the option --lgpl accepts the form --lgpl=3orGPLv2
* the compatibility checks consider this 'LGPLv3+ or GPLv2' license
LGPLv2+ --> 'LGPLv3+ or GPLv2'
'LGPLv3+ or GPLv2' --> LGPLv3+ = LGPL
'LGPLv3+ or GPLv2' --> GPLv2+
'LGPLv3+ or GPLv2' --> GPLv3+ = GPL
2)
Module Authors of the lib/* files (modulo trivial changes)
memcmp2 Bruno
amemxfrm Bruno
Module Authors of the lib/* files (modulo trivial changes)
fpieee --
fpucw Bruno
frexpl-nolibm Bruno
frexp-nolibm Bruno
isnand-nolibm Bruno, Paul, Eric, Ludovic
isnanf-nolibm Bruno, Paul, Eric, Ludovic
isnanl-nolibm Bruno, Paul, Eric, Ludovic
printf-frexp Bruno
printf-frexpl Bruno
printf-safe --
signbit Bruno, Paul
I am willing to relicense these modules to 'LGPLv3+ or GPLv2' or to the even
weaker license LGPLv2+.
lib/float+.h is already under LGPLv2+, per the modules 'integer_length' and
'vasnprintf'.
=== Paul, Eric, Ludovic, ===
Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=history;f=lib/isnan.c
Bruno
--
In memoriam Moustapha Akkad <http://en.wikipedia.org/wiki/Moustapha_Akkad>
Bruno Haible
2016-11-19 10:26:27 UTC
Permalink
Raw Message
Hi Paolo,

For the 'frexpl-nolibm' module I also need your approval, since you
contributed lib/frexpl.c on 2003-02-18.

Would you agree to relicense your initial lib/frexpl.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?

If you don't voice an objection within a week, I'll assume you agree.

Bruno
Post by Bruno Haible
It has been decided that libunistring is going to be relicensed under
"dual LGPLv3+ or GPLv2" license. See
http://lists.gnu.org/archive/html/bug-libunistring/2016-11/msg00003.html
To this effect, the libunistring modules in gnulib that are currently under
LGPLv3+ need to be relicensed to 'LGPLv3+ or GPLv2'. Those modules that
are under LGPLv2+ stay under LGPLv2+.
1)
This proposed patch does this. It also extends gnulib-tool so that
* the option --lgpl accepts the form --lgpl=3orGPLv2
* the compatibility checks consider this 'LGPLv3+ or GPLv2' license
LGPLv2+ --> 'LGPLv3+ or GPLv2'
'LGPLv3+ or GPLv2' --> LGPLv3+ = LGPL
'LGPLv3+ or GPLv2' --> GPLv2+
'LGPLv3+ or GPLv2' --> GPLv3+ = GPL
2)
Module Authors of the lib/* files (modulo trivial changes)
memcmp2 Bruno
amemxfrm Bruno
Module Authors of the lib/* files (modulo trivial changes)
fpieee --
fpucw Bruno
frexpl-nolibm Bruno
frexp-nolibm Bruno
isnand-nolibm Bruno, Paul, Eric, Ludovic
isnanf-nolibm Bruno, Paul, Eric, Ludovic
isnanl-nolibm Bruno, Paul, Eric, Ludovic
printf-frexp Bruno
printf-frexpl Bruno
printf-safe --
signbit Bruno, Paul
I am willing to relicense these modules to 'LGPLv3+ or GPLv2' or to the even
weaker license LGPLv2+.
lib/float+.h is already under LGPLv2+, per the modules 'integer_length' and
'vasnprintf'.
=== Paul, Eric, Ludovic, ===
Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=history;f=lib/isnan.c
Bruno
--
In memoriam Farhád Asdaqí <http://www.iranhrdc.org/english/publications/reports/3149-a-faith-denied-the-persecution-of-the-baha-is-of-iran.html?p=29>
Paolo Bonzini
2016-11-19 11:53:54 UTC
Permalink
Raw Message
Post by Bruno Haible
Hi Paolo,
For the 'frexpl-nolibm' module I also need your approval, since you
contributed lib/frexpl.c on 2003-02-18.
Would you agree to relicense your initial lib/frexpl.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
If you don't voice an objection within a week, I'll assume you agree.
LGPLv2+ is fine for any gnulib module I wrote.

Paolo
Post by Bruno Haible
Bruno
Post by Bruno Haible
It has been decided that libunistring is going to be relicensed under
"dual LGPLv3+ or GPLv2" license. See
http://lists.gnu.org/archive/html/bug-libunistring/2016-11/msg00003.html
To this effect, the libunistring modules in gnulib that are currently under
LGPLv3+ need to be relicensed to 'LGPLv3+ or GPLv2'. Those modules that
are under LGPLv2+ stay under LGPLv2+.
1)
This proposed patch does this. It also extends gnulib-tool so that
* the option --lgpl accepts the form --lgpl=3orGPLv2
* the compatibility checks consider this 'LGPLv3+ or GPLv2' license
LGPLv2+ --> 'LGPLv3+ or GPLv2'
'LGPLv3+ or GPLv2' --> LGPLv3+ = LGPL
'LGPLv3+ or GPLv2' --> GPLv2+
'LGPLv3+ or GPLv2' --> GPLv3+ = GPL
2)
Module Authors of the lib/* files (modulo trivial changes)
memcmp2 Bruno
amemxfrm Bruno
Module Authors of the lib/* files (modulo trivial changes)
fpieee --
fpucw Bruno
frexpl-nolibm Bruno
frexp-nolibm Bruno
isnand-nolibm Bruno, Paul, Eric, Ludovic
isnanf-nolibm Bruno, Paul, Eric, Ludovic
isnanl-nolibm Bruno, Paul, Eric, Ludovic
printf-frexp Bruno
printf-frexpl Bruno
printf-safe --
signbit Bruno, Paul
I am willing to relicense these modules to 'LGPLv3+ or GPLv2' or to the even
weaker license LGPLv2+.
lib/float+.h is already under LGPLv2+, per the modules 'integer_length' and
'vasnprintf'.
=== Paul, Eric, Ludovic, ===
Would you agree to relicense your changes to lib/isnan.c
under 'LGPLv3+ or GPLv2'?
Or possibly even under LGPLv2+?
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=history;f=lib/isnan.c
Bruno
--
In memoriam Farhád Asdaqí <http://www.iranhrdc.org/english/publications/reports/3149-a-faith-denied-the-persecution-of-the-baha-is-of-iran.html?p=29>
Bruno Haible
2016-11-20 01:06:25 UTC
Permalink
Raw Message
Post by Paolo Bonzini
LGPLv2+ is fine for any gnulib module I wrote.
Thank you, Paolo.

With all approvals complete, I pushed the relicensing changes.

Bruno
--
In memoriam Kerem Yılmazer <http://en.wikipedia.org/wiki/Kerem_Yılmazer>
Bruno Haible
2016-11-21 18:46:30 UTC
Permalink
Raw Message
fseterr LGPL
mbchar LGPL
mbiter LGPL
mbsnlen LGPL
wcwidth LGPL
Oh, indeed. Somehow I missed these dependencies.

The file lib/stdio-impl.h is already under LGPLv2+, per modules
fflush, freadahead, freading, freadptr, freadseek, fpurge, fseeko, ftello.

The other files were written by:
lib/fseterr.h: Bruno
lib/fseterr.c: Bruno, Kevin Cernekee
lib/mbchar.h: Bruno, Paul (regarding 'inline')
lib/mbchar.c: Bruno, Paul (regarding 'inline')
lib/mbiter.h: Bruno, Paul
lib/mbiter.c: Paul
lib/mbsnlen.c: Bruno
lib/wcwidth.c: Bruno

I would be willing to put my contributions to these files under LGPLv2+.

=== Paul ===

Would you be willing to do the same for lib/mbchar.* and lib/mbiter.* ?

=== Kevin ===

Would you be willing to do the same for lib/fseterr.c ?

Bruno
Kevin Cernekee
2016-11-21 18:56:11 UTC
Permalink
Raw Message
Post by Bruno Haible
I would be willing to put my contributions to these files under LGPLv2+.
[...]
Post by Bruno Haible
=== Kevin ===
Would you be willing to do the same for lib/fseterr.c ?
Yes, approved.
Bruno Haible
2016-12-02 01:02:02 UTC
Permalink
Raw Message
Post by Bruno Haible
lib/fseterr.h: Bruno
lib/fseterr.c: Bruno, Kevin Cernekee
lib/mbchar.h: Bruno, Paul (regarding 'inline')
lib/mbchar.c: Bruno, Paul (regarding 'inline')
lib/mbiter.h: Bruno, Paul
lib/mbiter.c: Paul
lib/mbsnlen.c: Bruno
lib/wcwidth.c: Bruno
I would be willing to put my contributions to these files under LGPLv2+.
=== Paul ===
Would you be willing to do the same for lib/mbchar.* and lib/mbiter.* ?
=== Kevin ===
Would you be willing to do the same for lib/fseterr.c ?
Thanks Kevin for your approval.

I didn't get an approval from Paul, so I'll assume that he considers his
contributions to these files (about 'inline', and spello fixes) as not
relevant for copyright questions.
Paul, please cry loudly if you disagree :)


2016-12-01 Bruno Haible <***@clisp.org>

Relicense some modules under LGPLv2+.
Kevin Cernekee's approval is in
http://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00090.html.
* modules/fseterr (License): Change to LGPLv2+.
* modules/mbchar (License): Likewise.
* modules/mbiter (License): Likewise.
* modules/mbsnlen (License): Likewise.
* modules/wcwidth (License): Likewise.

diff --git a/modules/fseterr b/modules/fseterr
index 242fc2d..7fa7ecd 100644
--- a/modules/fseterr
+++ b/modules/fseterr
@@ -21,7 +21,7 @@ Include:
"fseterr.h"

License:
-LGPL
+LGPLv2+

Maintainer:
all
diff --git a/modules/mbchar b/modules/mbchar
index 08e4a14..2f7e11e 100644
--- a/modules/mbchar
+++ b/modules/mbchar
@@ -26,7 +26,7 @@ Include:
"mbchar.h"

License:
-LGPL
+LGPLv2+

Maintainer:
all
diff --git a/modules/mbiter b/modules/mbiter
index 66e0cb1..6375652 100644
--- a/modules/mbiter
+++ b/modules/mbiter
@@ -25,7 +25,7 @@ Include:
"mbiter.h"

License:
-LGPL
+LGPLv2+

Maintainer:
all
diff --git a/modules/mbsnlen b/modules/mbsnlen
index ea6fb72..9be1cdd 100644
--- a/modules/mbsnlen
+++ b/modules/mbsnlen
@@ -18,7 +18,7 @@ Include:
<string.h>

License:
-LGPL
+LGPLv2+

Maintainer:
all
diff --git a/modules/wcwidth b/modules/wcwidth
index b5bea24..5a27713 100644
--- a/modules/wcwidth
+++ b/modules/wcwidth
@@ -28,7 +28,7 @@ Include:
<wchar.h>

License:
-LGPL
+LGPLv2+

Maintainer:
all
Paul Eggert
2016-12-02 01:40:35 UTC
Permalink
Raw Message
Post by Bruno Haible
Paul, please cry loudly if you disagree :)
No, that's fine, thanks. (Sorry, I thought I already replied to this.)
Loading...