public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, siddhesh@gotplt.org
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Fri, 25 Jun 2021 10:52:39 +0300	[thread overview]
Message-ID: <83eecqs7nc.fsf@gnu.org> (raw)
In-Reply-To: <87pmwaieyk.fsf@oldenburg.str.redhat.com> (message from Florian Weimer on Fri, 25 Jun 2021 09:24:51 +0200)

> From: Florian Weimer <fweimer@redhat.com>
> Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,  Eli Zaretskii <eliz@gnu.org>
> Date: Fri, 25 Jun 2021 09:24:51 +0200
> 
> * Eli Zaretskii via Libc-alpha:
> 
> > I'm showing text from the assignment agreement that IMO clearly says
> > the developer retains all the rights.
> 
> No, the developer gives up copyright ownership.

I don't understand what that means, sorry.  The text says I can do
anything and everything I want with the code, except interfering with
the FSF's use of that code.  So what exactly did I give up?

> This has real legal consequences, and it is quite different from a
> broad-ranging license to use the contributions.  If the FSF wanted
> the latter, it could ask for precisely that, but instead it asks for
> full ownership.

I looked up all the instances of "owner" and "ownership" in the CLA
text, and couldn't find where they ask for "full ownership".  What did
I miss?

> Apart from the recent actions of the FSF that are so difficult to
> understand, there is also a glibc-specific aspect here: The FSF is
> ignoring large-scale LGPL infringement that comes with incorrect use of
> container technology.  (At the very least, publishing a container image
> with glibc in it requires certain legal notices according to the LGPL
> terms, and all binaries linked against glibc must be re-linkable against
> a changed glibc.)  This has reached such a degree that distributors of
> container images might legally assume that the FSF has waived any and
> all LGPL requirements, which the FSF can do as the copyright owner.

I don't know about this specific case, but it sounds like something to
raise up with the FSF, and urgently.

> If true, only an influx of additional copyright owners for glibc can
> preserve the (limited) copyleft nature of glibc.

How will it do that?  If you have 100 or 500 or 1000 copyright owners,
how would glibc do better in case of such infringements?

  reply	other threads:[~2021-06-25  7:52 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  1:04 Bruno Haible
2021-06-23  3:19 ` Siddhesh Poyarekar
2021-06-24 19:30   ` Eli Zaretskii
2021-06-25  2:23     ` Siddhesh Poyarekar
2021-06-25  6:26       ` Eli Zaretskii
2021-06-25  6:47         ` Siddhesh Poyarekar
2021-06-25  7:06           ` Eli Zaretskii
2021-06-25  8:57             ` Siddhesh Poyarekar
2021-06-25  9:43               ` Siddhesh Poyarekar
2021-06-25 11:32                 ` Eli Zaretskii
2021-06-25 12:07                   ` Florian Weimer
2021-06-25 12:11                   ` Siddhesh Poyarekar
2021-06-25 12:14                     ` Florian Weimer
2021-06-25 12:25                       ` Siddhesh Poyarekar
2021-06-25 12:33                         ` Florian Weimer
2021-06-25 12:48                           ` Siddhesh Poyarekar
2021-06-25 13:44                             ` Eli Zaretskii
2021-06-25 14:06                               ` Siddhesh Poyarekar
2021-06-26  6:31                                 ` Eli Zaretskii
2021-06-28  4:11                                   ` Siddhesh Poyarekar
2021-06-28 12:01                                     ` Eli Zaretskii
2021-06-28 13:06                                       ` Siddhesh Poyarekar
2021-06-28 14:04                                         ` Phil Blundell
2021-06-28 14:57                                         ` Eli Zaretskii
2021-06-25 11:30               ` Eli Zaretskii
2021-06-25 12:24                 ` Siddhesh Poyarekar
2021-06-25  7:24         ` Florian Weimer
2021-06-25  7:52           ` Eli Zaretskii [this message]
2021-06-25  8:23             ` Florian Weimer
2021-06-25 11:03               ` Eli Zaretskii
2021-06-25  6:30       ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2021-07-02 22:23 Craig Topham
2021-07-05 14:59 ` Szabolcs Nagy
2021-07-05 16:48   ` Eli Zaretskii
2021-07-05 18:52     ` Paul Eggert
2021-06-14 18:52 Carlos O'Donell
2021-06-14 19:08 ` Rich Felker
2021-06-14 19:25   ` Khem Raj
2021-06-14 20:05 ` Florian Weimer
2021-06-14 20:22   ` Matt Turner
2021-06-15 20:28     ` Carlos O'Donell
2021-06-14 21:16   ` Paul Eggert
2021-06-14 20:18 ` Matt Turner
2021-06-14 20:22 ` Adhemerval Zanella
2021-06-15  2:48 ` Siddhesh Poyarekar
2021-06-15  3:18 ` DJ Delorie
2021-06-15 17:41   ` Paul Eggert
2021-06-15 18:43     ` DJ Delorie
2021-06-15 19:05       ` Paul Eggert
2021-06-15 19:12         ` DJ Delorie
2021-06-15 19:35           ` Paul Eggert
2021-06-15 19:42             ` DJ Delorie
2021-06-15 20:08             ` Carlos O'Donell
2021-07-02 22:33             ` Carlos O'Donell
2021-07-03  1:59               ` Paul Eggert
2021-07-04  0:40                 ` Paul Eggert
2021-07-04 11:55                   ` Florian Weimer
2021-07-04 18:32                     ` Paul Eggert
2021-07-04 23:25                       ` Bradley M. Kuhn
2021-07-05 15:26                         ` Christoph Hellwig
2021-07-06 18:02                           ` Bradley M. Kuhn
2021-07-05  5:28                       ` Carlos O'Donell
2021-07-05 20:21                         ` Paul Eggert
2021-07-06 18:05                           ` Bradley M. Kuhn
2021-07-06 19:42                             ` Paul Eggert
     [not found]                               ` <YOTTfm12jac/NYe5@ebb.org>
2021-07-07  8:51                                 ` Florian Weimer
2021-07-07 15:01                                   ` Joseph Myers
2021-07-05  5:00                     ` Carlos O'Donell
2021-07-05  5:28                       ` Florian Weimer
2021-07-05 20:37                 ` Joseph Myers
2021-07-03  3:24               ` Bruno Haible
2021-07-05  5:53                 ` Carlos O'Donell
2021-06-15  3:39 ` Daniel Black
2021-06-15 16:09 ` Josh Triplett
2021-06-16 13:01 ` Alyssa Ross
2021-06-16 14:08 ` Adam Sampson
2021-06-16 19:33   ` Joseph Myers
2021-06-16 19:45 ` Phil Blundell
2021-06-30 21:54 ` Bradley M. Kuhn
2021-07-01  5:24   ` Siddhesh Poyarekar
2021-07-01 19:33     ` Bradley M. Kuhn
2021-07-02  3:29       ` Siddhesh Poyarekar
2021-07-03  6:03         ` Eli Zaretskii
2021-07-01  8:19   ` Alexandre Oliva
2021-07-02  8:59   ` Florian Weimer
2021-06-30 22:21 ` Mark Wielaard

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=83eecqs7nc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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.
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).