All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
Date: Mon, 09 Apr 2018 21:08:10 +0200	[thread overview]
Message-ID: <1523300890.3525.55.camel@suse.com> (raw)
In-Reply-To: <9ad33b55-17fc-9ed9-ca11-2be0e11a7b1f@gmail.com>

On Mon, 2018-04-09 at 19:29 +0200, Xose Vazquez Perez wrote:
> On 04/09/2018 05:57 PM, Martin Wilck wrote:
> 
> > 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.
> 
> They are under their _original_ licence. Nothing was changed inside
> the files.

Would you care to enlighten me what this "original license" might be?
The files themselves contain no information about it.

> > By changing COPYING to
> > GPLv2.0, you effectively changed the license of all these files
> > from
> > LPGLv2.0 to GPLv2.0
> 
> There is no evidence of that in any place. All references to the
> COPYING file are
> external files/code, with GPL licence.

This is not about the files you refer to. The reference in those files
was obiously wrong until your patch was merged. (I admit that's a +1
for your patch).

This is about the files that have *no license header*. We *must* assume
that they are covered by a central license file in the top directory.
If we don't do that, it'd be questionable if said files are
distributable at all. Legally, they'd probably not be considered FLOSS.
Files without explicit copyright are be covered by regular copyright
law, meaning that copying and redistribution are _not_ allowed under
most legislations.

I hope that makes it clear why we need to be firm that these files are
covered by the top license file. That central license file used to be
COPYING. The point of my post was that we have *two* such files now,
and without resorting to history it's impossible to tell which file is
covered by which license (and even with history it's hard, but that's
another posting).

Historically, these files were added to the tree by Christophe, and
he'd copied the LGPLv2.0 text into COPYING, thus it seems likely that
he meant them to be under LGPLv2.0.

Martin

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

  reply	other threads:[~2018-04-09 19:08 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
2018-04-09 17:29   ` Xose Vazquez Perez
2018-04-09 19:08     ` Martin Wilck [this message]
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=1523300890.3525.55.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.