Seeking input from developers: glibc copyright assignment policy.

Craig Topham craigt@fsf.org
Fri Jul 2 22:23:42 GMT 2021


>>>/From: Florian Weimer <fweimer@redhat.com <mailto:fweimer@redhat.com>> />>>/Cc: Siddhesh Poyarekar <siddhesh@gotplt.org
<mailto:siddhesh@gotplt.org>>, Eli Zaretskii <eliz@gnu.org
<mailto: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? /
> Ownership, that is, you don't control anymore who gets to use the code
> and under what terms.

The grant back in section 1 (d) of the FSF's copyright assignment
gives control to the developer who can then decide who gets to use the
code and under what terms, but the developer cannot limit how the FSF
distributes and uses the code, which is under a free license, most
likely the GPLv3 or later.

~Craig



More information about the Libc-alpha mailing list