unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: pengmeiyu@riseup.net
To: 43975@debbugs.gnu.org
Cc: Peng Mei Yu <pengmeiyu@riseup.net>
Subject: [bug#43975] [PATCH 0/1] gnu: Add ccal [And asking for help on license issue].
Date: Tue, 13 Oct 2020 16:09:15 +0800	[thread overview]
Message-ID: <20201013080915.23344-1-pengmeiyu@riseup.net> (raw)

From: Peng Mei Yu <pengmeiyu@riseup.net>

Hi everyone,

This patch adds ccal, a program for Chinese calendar.  This program has a
weird license issue.

The program's original license was GPL v2+, then the author changed part of
the source code to LGPL under the request of third-party users.  You can find
the email discussion here:
https://github.com/liangqi/kcalendar/blob/c77098a1f3133878743632cdd5788377161610a1/README#L57

The problem is within the LGPL license notice in source code.  The LGPL
license published by FSF can be one of three choices:

- GNU Library General Public License, version 2.0
- GNU Lesser General Public License, version 2.1
- GNU Lesser General Public License, version 3.0

1. In the license notice sections of source code, the author wrote:

mphases.cpp:
--8<---------------cut here---------------start------------->8---
   Distributed under the terms of the GNU Lesser General Public License as
   published by the Free Software Foundation; either version 2 of the
   License, or (at your option) any later version.
--8<---------------cut here---------------end--------------->8---

"GNU Lesser General Public License" and "version 2" is not a valid
combination. "GNU Lesser General Public License" can be either version 2.1 or
version 3.0.

2. In the README file, the author also missspelled "GNU Lesser General Public
License".  "GNU Less General Public License" is not a valid license name.

README:
--8<---------------cut here---------------start------------->8---
Distributed under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version. Portions related to
computing of Chinese dates are distributed under the terms of the GNU
Less General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option)
any later version.
--8<---------------cut here---------------end--------------->8---

3. The COPYING.LESSER file bundled with source code is a copy of LGPL v3.

This is a total mess.

I think the author's intention was to release the code with "GNU Library
General Public License, version 2.0 or any later version".  However what he
wrote in the code is "GNU Lesser General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your option)
any later version."  I think LGPL v2.1 and v3.0 is compatible with this
sentence.  But I am not sure if "GNU Library General Public License, version
2.0" can be considered compatible.  I am in no way familiar with the western
legal system, so this is only my personal opinion.

The GNU.org webset lists "GNU Library General Public License, version 2.0" as
an old version of "GNU Lesser General Public License":
https://www.gnu.org/licenses/old-licenses/old-licenses.html
Does that mean the FSF thinks "GNU Library General Public License, version
2.0" is equal to "GNU Lesser General Public License, version 2.0"?  Will this
hold in a court?

What's your opinion?

Thanks in advance.




             reply	other threads:[~2020-10-13  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  8:09 pengmeiyu [this message]
2020-10-13  8:22 ` [bug#43975] [PATCH 1/1] gnu: Add ccal Peng Mei Yu
2020-10-18 21:51   ` bug#43975: " Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201013080915.23344-1-pengmeiyu@riseup.net \
    --to=pengmeiyu@riseup.net \
    --cc=43975@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).