From: Martin Wilck <mwilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
Hannes
Subject: Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
Date: Mon, 09 Apr 2018 17:57:20 +0200 [thread overview]
Message-ID: <1523289440.3525.27.camel@suse.com> (raw)
In-Reply-To: <20180327182819.20163-1-xose.vazquez@gmail.com>
Hello Christophe,
You've merged the GPL/LGPL patch set from Xose. I'd like to understand
your intentions.
There are >130 files in the multipath-tools source code which don't
have a license header. So far my assumption was that these files were
covered by COPYING, which used to be LGPLv2.0. By changing COPYING to
GPLv2.0, you effectively changed the license of all these files from
LPGLv2.0 to GPLv2.0. *Did you mean that*? Or was it your intention that
these files are now covered by COPYING.LESSER?
If we ship several COPYING files, we need to tell which source files
are covered by which one. Without that, the license situation is now
even less clear than before. Users might even think that they can
freely choose between the two, which isn't the case AFAICT.
I was preparing a README document describing the current state of
affairs regarding the licensing (along the lines of my "multipath-tools
licenses" posting from Mar 23), but this late move of yours leaves me
confused.
IMHO changing the license would need the consent of the copyright
holders, at least those mentioned in the file headers. I'm currently
assuming that my previous assessment still holds and source files that
have no license header, and for which no other evidence exists, are
covered by LGPLv2.0 aka COPYING.LESSER. Please correct me if I'm wrong.
Regards,
Martin
PS: we also need to include the GPLv3.0 text because of the GPLv3.0
license of libdmmp.
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-04-09 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 18:28 [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER Xose Vazquez Perez
2018-03-27 18:28 ` [PATCH 2/2] multipath-tools: add GPLv2 as COPYING Xose Vazquez Perez
2018-03-27 22:04 ` Martin Wilck
2018-03-28 19:31 ` Xose Vazquez Perez
2018-03-27 22:03 ` [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER Martin Wilck
2018-03-28 19:40 ` Xose Vazquez Perez
2018-03-28 19:54 ` Martin Wilck
2018-03-28 20:05 ` Xose Vazquez Perez
2018-03-28 20:14 ` Martin Wilck
2018-04-09 15:57 ` Martin Wilck [this message]
2018-04-09 17:29 ` Xose Vazquez Perez
2018-04-09 19:08 ` Martin Wilck
2018-04-09 20:38 ` Christophe Varoqui
2018-04-09 21:25 ` Martin Wilck
2018-04-09 22:37 ` multipath-tools 0.7.6 fossology license assessment Martin Wilck
2018-04-10 14:54 ` [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER Xose Vazquez Perez
2018-04-10 15:45 ` Christophe Varoqui
2018-04-10 21:38 ` Xose Vazquez Perez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1523289440.3525.27.camel@suse.com \
--to=mwilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=xose.vazquez@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.