Seeking input from developers: glibc copyright assignment policy.

[Paul Eggert]

A proposal to change the glibc copyright assignment policy is being 
circulated on libc-alpha. The email thread starts at 
<https://sourceware.org/pipermail/libc-alpha/2021-June/127581.html>, and 
the text of the email seeking input is at the end of this message.

I'm sending this to bug-gnulib because we copy some files directly from 
glibc and eventually I expect these files to be affected. The simplest 
approach I see for Gnulib is to adopt glibc's policy, at least for files 
or code copied from glibc.

Here's a copy of the email seeking input from developers on libc-alpha.

-----

Community,

glibc was created as part of the GNU Project but has grown to operate as
an autonomous project. As part of the GNU Toolchain the glibc stewards
support the gcc project policy changes presented here:
https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html

The glibc stewards are seeking input from developers to decide if the 
project
should relax the requirement to assign copyright for all changes to the
Free Software Foundation as follows:

Contributors who have an FSF Copyright Assignment wouldn't need to
change anything.  Contributors who wish to utilize the Developer Certificate
of Origin[1] would add a Signed-off-by message to their commit messages.

The changes to accept patches with or without FSF copyright assignment
would be effective on August 2nd, and would apply to all open branches.

The glibc stewards, like the GCC SC, continue to affirm the principles of
Free Software, and that will never change.

glibc will continue to be developed, distributed, and licensed under the
GNU Lesser General Public License v2.1 or any later version as
published by the Free Software Foundation.

Input on this issue is accepted until July 1st 2021.

Signed,
Ryan Arnold
Paul Eggert
Jakub Jelinek
Maxim Kuvyrkov
Joseph Myers
Carlos O'Donell

[1] https://developercertificate.org/