public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>, libc-alpha@sourceware.org
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Fri, 2 Jul 2021 08:59:10 +0530	[thread overview]
Message-ID: <5f3dcd13-f367-47ba-9dc9-12852bba1c18@gotplt.org> (raw)
In-Reply-To: <87eechbzig.fsf@ebb.org>

On 7/2/21 1:03 AM, Bradley M. Kuhn wrote:
> Keep in mind that the copyright assignment/disclaimer arrangements have many
> forms and structures; IIUC, most can be revoked.  Furthermore, I note that
> the deadline day for input on this momentous change is nearing its end, and
> there are no statements on this thread from the well-known major employers
> involved in glibc about what their intended copyright policy if the FSF
> copyright assignment mandate is lifted.

For commercial distribution vendors**, I suspect it is not as easy a 
decision to withdraw copyright assignment since their contribution to 
GNU goes beyond gcc and glibc.  For hardware vendors (who form the other 
large contingent of contributors) maybe it's not as hard a decision, but 
it still involves getting legal to evaluate the change and initiate the 
process so I'm not entirely sure given that nobody has actually moved 
yet AFAICT.

> Absent assurances and more information, we must assume the worst case: that
> the all new copyrights are owned by the contributors' employers as soon as
> the copyright assignment mandate is lifted.

But for that their assignment has to be terminated, no?  If nobody has 
moved to do that, the worst case assumption ought to be a little more 
benign, i.e. companies start evaluating and withdrawing their 
assignments and the change happens more slowly over the coming months/years.

Regardless of that, I reckon the FSF will always have enough of a 
copyright stake to allow enforcing copyleft.  The glibc code base has 
legally significant artifacts at least from the early 90s that have 
survived to this date; that's 30 years.

> I suppose it's possible that companies who contribute to glibc have also
> faced frivolous copyright claims on FOSS.  (However, such incidents are
> extremely rare, though — and, I'm admittedly wondering if you're referencing
> the same widely exaggerated tale that I'm thinking of.)  Regardless, I think
> it's a moot point.  Such a situation doesn't imply those companies will
> later have the goal of defending the rights of users under copyleft.  If
> relevant at all, IMO, it cuts the other way: those companies may seek
> copyrights for escalation/counter-claims against any enforcement action
> (even a legitimate one brought to defend users' rights).  Note that, when

/me nods.  Based on my limited knowledge from asking around, it doesn't 
look like anybody has moved to terminate their assignments. 
Unfortunately I am not privy to the assignment file or the details of 
contracts with the FSF so I don't know for sure.

Siddhesh

** I am not speaking for my employer (Red Hat) and this is my personal 
impression based on my understanding of how distributions work.

  reply	other threads:[~2021-07-02  3:29 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
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
2021-06-25  8:23             ` Florian Weimer
2021-06-25 11:03               ` Eli Zaretskii
2021-06-25  6:30       ` Eli Zaretskii
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

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=5f3dcd13-f367-47ba-9dc9-12852bba1c18@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=bkuhn@sfconservancy.org \
    --cc=libc-alpha@sourceware.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).