All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Fontana <rfontana@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-spdx@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
	Jonathan Brassow <jbrassow@redhat.com>
Subject: Re: treewide: License cleanup - RedHat originated
Date: Sun, 22 May 2022 13:33:54 -0400	[thread overview]
Message-ID: <CAC1cPGz4CVCqb7P72sWjJ5S6s6HcxzqiwuykwGFswkovOuALHA@mail.gmail.com> (raw)
In-Reply-To: <165322121770.3770149.18166071018834854082.tglx@xen13>

On Sun, May 22, 2022 at 10:55 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> Richard!
>
> Sorry for pestering you, but the amount of files is just too much to split
> it up and targetting the authors is difficult because quite some of them
> are not longer at RHT. The files are all (c) RedHat or Sistina Software,
> which is part of RedHat since 2003.
>
> This is part of the effort to clean up the licensing mess in the kernel and
> convert it to SPDX license identifiers as the only source of license
> information.
>
> Archaeology found the following unspecific GPL license references, which
> have been authored by RedHat/Sistina.
>
> To clean this up, can you please either advise the RHT kernel team or let
> me know which GPLv2 variant to use for the files and I run it through my
> cleanup machinery.

Hi Thomas,

I assume you're selecting files that have some sort of Red Hat or
Sistina copyright notice. Just as a disclaimer, I can't speak to
copyrights in these files that may be held by other organizations or
individuals (and I can't say definitively whether any file bearing a
Red Hat or Sistina copyright notice has or retains any copyright owned
by Red Hat). With that said:

> 1) this file is released under the gpl

I am fine with saying that any Red Hat copyrights (including any
Sistina copyrights acquired by Red Hat) in these can be represented
with SPDX-License-Identifier: GPL-2.0.

I would note that the following files did not seem to have any Red Hat
or Sistina copyright notices:

>    drivers/md/dm-log-writes.c
>    drivers/md/dm-ps-queue-length.c
>    drivers/md/dm-ps-service-time.c
>    drivers/md/dm-unstripe.c
>    drivers/md/dm-zero.c

Skipping category 2 for the moment:

> 3) (c) 2000 red hat gpl d

> 4) this code is covered by the gpl

> 5) this software may be freely redistributed under the terms of the gnu
>    general public license you should have received a copy of the gnu general
>    public license along with this program if not write to the free software
>    foundation inc 675 mass ave cambridge ma 02139 usa

> 6) released under the general public license (gpl)

I am fine with saying that any Red Hat copyrights (including any
Sistina copyrights acquired by Red Hat) in these can be represented
with SPDX-License-Identifier: GPL-2.0.

> 2) this file is released under the lgpl
>
>    drivers/md/dm-core.h
>    drivers/md/dm-log-userspace-base.c
>    drivers/md/dm-log-userspace-transfer.c
>    drivers/md/dm-log-userspace-transfer.h
>    drivers/md/dm-log.c
>    drivers/md/dm-rq.h
>    drivers/md/dm.h
>    include/linux/device-mapper.h
>    include/linux/dm-dirty-log.h

For these, if the question is just about what version of the LGPL we
should treat these as, I'd be fine with representing them as
SDPX-License-Identifier: LGPL-2.1.

However, and I realize this may go beyond my 'remit' as someone
consulted for linux-spdx stuff or open some additional bag of worms,
I'm wondering if these would be better off just relicensed under
GPLv2, and thus represented as SPDX-License-Identifier: GPL-2.0. Even
treating this code as having been LGPLv2.x-licensed, this would be
authorized or at any rate contemplated by the largely-overlooked
LGPLv2.0/LGPLv2.1 section 3. Suggesting this because it would seem to
help marginally with some of the goals of this initiative and also
because it's not obvious to me why LGPL would have been preferred over
GPLv2 for these files to begin with, assuming they weren't copied from
some unrelated LGPL-licensed project. I've cc'd Jonathan Brassow and
Mike Snitzer in case they have any thoughts on this.

Richard


  reply	other threads:[~2022-05-22 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 14:54 treewide: License cleanup - RedHat originated Thomas Gleixner
2022-05-22 17:33 ` Richard Fontana [this message]
2022-05-22 18:12   ` Thomas Gleixner
2022-05-25 14:58     ` Mike Snitzer
2022-05-25 14:58       ` [dm-devel] " Mike Snitzer
2022-05-25 14:56   ` Mike Snitzer
2022-05-25 14:56     ` [dm-devel] " Mike Snitzer

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=CAC1cPGz4CVCqb7P72sWjJ5S6s6HcxzqiwuykwGFswkovOuALHA@mail.gmail.com \
    --to=rfontana@redhat.com \
    --cc=jbrassow@redhat.com \
    --cc=linux-spdx@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=tglx@linutronix.de \
    /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.