Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Relicensing to LGPL-2.1-or-later from LGPL-2.1-only #1774

Closed
41 tasks done
kou opened this issue May 7, 2024 · 49 comments · Fixed by #2154
Closed
41 tasks done

Relicensing to LGPL-2.1-or-later from LGPL-2.1-only #1774

kou opened this issue May 7, 2024 · 49 comments · Fixed by #2154
Labels
Feature

Comments

@kou
Copy link
Member

kou commented May 7, 2024 •
edited
Loading

What is your problem?

Groonga is licensed under LGPL-2.1-only.

I want to relicense Groonga to LGPL-2.1-or-later from LGPL-2.1-only to improve Apache-2.0 compatibility.

Incompatibility between GPL-2.0 and Apache-2.0 is well known because both of FSF and ASF explain it:

Compatibility between LGPL-2.1 and Apache-2.0 isn't explained there but they may be incompatible too because LGPL-2.1 is based on GPL-2.0.

If LGPL-2.1 and Apache-2.0 are incompatible, LGPL-2.1-only licensed Groonga can't link with Apache-2.0 libraries such as Apache Arrow. LGPL-2.1-only licensed software can be also used as GPL-2.0-or-later licensed software because LGPL-2.1 has the following sentence:

  1. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.

So we can link with Apache-2.0 libraries by using Groonga as GPL-3.0-or-later licensed software. But this has a problem. If we use Groonga as GPL-3.0-or-later licensed software, we can't use Groonga with GPL-2.0-only licensed software such as MySQL.

If Groonga uses LGPL-2.1-or-later not LGPL-2.1-only, Groonga can link with Apache-2.0 libraries by using LGPL-3.0-or-later (LGPL-2.1-or-later includes it).

We need to ask all patch authors of Groonga to relicense Groonga to LGPL-2.1-or-later from LGPL-2.1-only.

Here are patch authors of Groonga:

$ git shortlog -sn
 11409	Kouhei Sutou
  3485	Sutou Kouhei
  1818	HAYASHI Kentaro
  1078	Daijiro MORI
   647	Kentaro Hayashi
   619	Susumu Yata
   449	Tasuku SUENAGA a.k.a. gunyarakun
   408	Horimoto Yasuhiro
   371	susumu.yata
   304	Yasuhiro Horimoto
   267	mori
   262	Ryo Onodera
   254	Masafumi Yokoyama
   162	naoa
   120	t2001
   110	Takashi Hashida
    94	Naoya Murakami
    93	cosmo0920
    86	Abe Tomoaki
    66	Nobuyoshi Nakada
    55	YUKI Hiroshi
    49	Haruka Yoshihara
    40	HorimotoYasuhiro
    39	Yoji SHIDARA
    36	Hiroshi Hatake
    35	Yuto Hayamizu
    34	whombx
    30	yoshihara haruka
    26	Toshihisa
    22	takuya kodama
    19	khayashi
    18	Yutaro Shimamura
    18	wanabe
    12	Hiroyuki Sato
    12	IWAI, Masaharu
    10	dependabot[bot]
     6	Kenji Okimoto
     6	jacob16bit
     5	orangain
     4	Hiroshi Ohkubo
     4	Motoi Washida
     3	Daiki Ueno
     3	OBATA Akio
     3	Tetsuro IKEDA
     3	do-aki
     3	mori daijiro
     3	tamano
     3	yagisumi
     2	Jun Kuriyama
     2	Noritada Kobayashi
     2	Tetsuharu OHZEKI
     2	YUKI "Piro" Hiroshi
     2	brazil
     2	kou
     2	tashiro
     2	unknown
     2	wi24rd
     1	Akinori MUSHA
     1	Anthony M. Cook
     1	Ayumu
     1	Dylan Golow
     1	Genki Takiuchi
     1	HashidaTKS
     1	Jasper Siepkes
     1	NOKUBI Takatsugu
     1	Natanael Copa
     1	SATOH Fumiyasu
     1	SHIDARA Yoji
     1	SHIMODA Hiroshi
     1	Sebastian Wiedenroth
     1	Shimomura Tatsuya
     1	Sho Minagawa
     1	Tasuku SUENAGA
     1	Tim Gates
     1	Yosuke Sekikawa
     1	Yosuke Shiro
     1	Yu.Shimamura
     1	Yuya TAMANO
     1	cafedomancer
     1	mooz
     1	ryo-pinus
     1	tSU-RooT
     1	tSU_RooT
     1	vagrant
     1	yu
     1	yutaro
     1	zunda

Here are distinct authors (except trivial patch authors):

If you agree to this license change, could you add the following comment to this issue?

I agree to apply LGPL-2.1-or-later to my commits.

If you have any questions or object this license change, please let us know.

Trivial patch authors:

Patch authors who can't be contacted on GitHub:

Patch authors whose commits are replaced by other commits:

PRs by @whombx (all of them are moving document location)

How to reproduce it

No response
@kou kou added the Feature label May 7, 2024
@kou
Copy link
Member Author

kou commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

4 similar comments
@kuriyama
Copy link
Contributor

kuriyama commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@kenhys
Copy link
Member

kenhys commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@knu
Copy link
Contributor

knu commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@tetsuharuohzeki
Copy link
Contributor

I agree to apply LGPL-2.1-or-later to my commits.

@hiroyuki-sato
Copy link
Contributor

I agree to apply LGPL-2.1-or-later to my commits.

- [x] @hiroyuki-sato

@abetomo
Copy link
Contributor

abetomo commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

6 similar comments
@komainu8
Copy link
Member

komainu8 commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@cosmo0920
Copy link
Contributor

I agree to apply LGPL-2.1-or-later to my commits.

@otegami
Copy link
Contributor

otegami commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@siepkes
Copy link
Contributor

siepkes commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@darashi
Copy link
Member

darashi commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@noritada
Copy link
Contributor

noritada commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@wi24rd
Copy link
Contributor

wi24rd commented May 7, 2024 via email

@wiedi
Copy link
Contributor

wiedi commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@kou
Copy link
Member Author

kou commented May 7, 2024

I asked t-shm about this by e-mail and t-shm accepted this change.

@naoa
Copy link
Member

naoa commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

6 similar comments
@ueno
Copy link
Contributor

ueno commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@wanabe
Copy link
Contributor

wanabe commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@orangain
Copy link
Contributor

orangain commented May 7, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@ryo-pinus
Copy link

I agree to apply LGPL-2.1-or-later to my commits.

@obache
Copy link
Contributor

obache commented May 8, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@myokoym
Copy link
Member

myokoym commented May 9, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@myokoym myokoym closed this as completed May 9, 2024
@myokoym myokoym reopened this May 9, 2024
@knok
Copy link

knok commented May 9, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@piroor
Copy link
Member

piroor commented May 9, 2024

I agree to change the license about my contributions.

@HashidaTKS
Copy link
Contributor

I agree to apply LGPL-2.1-or-later to my commits.

1 similar comment
@ikdttr
Copy link
Member

ikdttr commented May 9, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@gunyarakun
Copy link
Member

I agree to apply LGPL-2.1-or-later to my commits.

1 similar comment
@yoshihara
Copy link
Member

I agree to apply LGPL-2.1-or-later to my commits.

@tamano
Copy link
Member

tamano commented May 10, 2024

I agree to apply LGPL-2.1-or-later to my commits.

Thanks,

@ryoqun
Copy link
Member

ryoqun commented May 12, 2024

I agree to apply LGPL-2.1-or-later to my commits.

7 similar comments
@do-aki
Copy link
Contributor

do-aki commented May 13, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@genki
Copy link
Contributor

genki commented May 13, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@nobu
Copy link
Member

nobu commented May 15, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@hayamiz
Copy link

hayamiz commented May 21, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@daijiro
Copy link
Member

daijiro commented May 22, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@iwaim
Copy link
Contributor

iwaim commented May 30, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@t2001
Copy link
Member

t2001 commented May 30, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@yu
Copy link
Member

yu commented May 30, 2024

I agree to relicense all my commits under LGPL-2.1-or-later.

@s-yata
Copy link
Contributor

s-yata commented Jun 10, 2024

I agree to apply LGPL-2.1-or-later to my commits.

1 similar comment
@wm3
Copy link
Contributor

wm3 commented Jul 11, 2024

I agree to apply LGPL-2.1-or-later to my commits.

@abetomo abetomo mentioned this issue Jul 11, 2024
Closed
@kou kou mentioned this issue Jul 12, 2024
Merged
abetomo added a commit to abetomo/groonga-nginx that referenced this issue Jul 13, 2024
@abetomo
Update the license header for LGPL-2.1-or-later (groonga#13)
8f46a91 
GitHub: fix groongaGH-12

Here are patch authors in groonga/groonga:

```console
$ git checkout 'ae00cf3e2b9c77d9d478161d691e322863e5b887^'
$ git shortlog -sn src/httpd
    99  Kouhei Sutou
    11  Kentaro Hayashi
     9  HAYASHI Kentaro
     5  Sutou Kouhei
     4  Motoi Washida
     1  Takashi Hashida
```

All of them agreed with this license change on
groonga/groonga#1774 .

Here are patch authors in groonga/groonga-nginx:

```console
$ git shortlog -sn | cat
    44	Sutou Kouhei
     5	dependabot[bot]
     2	Abe Tomoaki
     1	takuya kodama
```

All of them agreed with this license change on
groonga#12 .

So we can change our license to LGPL-2.1-or-later from LGPL-2.1-only.
@abetomo
Copy link
Contributor

abetomo commented Jul 19, 2024 •
edited
Loading

Listed commits for authors who have no comments at this time.

I have assigned (T) to what I judged to be a trivial patch.
We appreciate any comments you may have.

@kou
Copy link
Member Author

kou commented Jul 19, 2024 •
edited
Loading

We can mark this as a trivial patch too because it just remove unused codes.

@abetomo
Copy link
Contributor

abetomo commented Jul 23, 2024

Replaced with jQuery UI Progressbar Widget.
#1821

@abetomo abetomo mentioned this issue Aug 5, 2024
Merged
@abetomo
Copy link
Contributor

abetomo commented Aug 16, 2024

Since the following two commits are not creative, we consider them not copyrightable.

If there are any objections, please comment on this isssue within one month.

@abetomo
Copy link
Contributor

abetomo commented Dec 11, 2024

For the next commit on #1774 (comment) list:

This has been replaced by a change in 7371926.

@abetomo
Copy link
Contributor

abetomo commented Dec 11, 2024

@whombx commits in the description of this issue has been replaced by commits to move a C API reference to a header file.

Related task: #1817
Example of a commit moved a C API reference to a header file: #2150

@abetomo
Copy link
Contributor

abetomo commented Dec 11, 2024

The list of patch authors who have agreed to relicensing is in this issue.
We have checked all patches by authors whose agreement could not be verified. What we have checked is that it has already been replaced, or is a trivial patch, etc.

The relicensing is ready.

@kou
Copy link
Member Author

kou commented Dec 11, 2024

Finally!
Let's do it!

@abetomo abetomo mentioned this issue Dec 11, 2024
Merged
@kou kou closed this as completed in #2154 Dec 11, 2024
@kou kou closed this as completed in ff26d60 Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Relicensing to LGPL-2.1-or-later from LGPL-2.1-only abetomo/groonga