Update to glibc copyright assignment policy

[Florian Weimer]

* Carlos O'Donell via Libc-alpha:

> On 7/29/21 6:25 AM, Siddhesh Poyarekar wrote:
>> On 7/29/21 1:20 AM, Carlos O'Donell via Libc-alpha wrote:
>>> branches. Code shared with other GNU packages via Gnulib will
>>> continue to require assignment to the FSF.
>> 
>> Does that mean we cannot touch the code shared with gnulib if we do
>> not assign copyright to the FSF?  Or does it mean that if/when that
>> happens, we will stop syncing those bits with gnulib?
>
> The code shared with gnulib carries with it an existing obligation
> to the gnulib community that we maintain the existing copyright
> protocol for those files to honour that obligation.
>
> My suggestion is that we as a community in glibc need to decide,
> on a file-by-file basis what we are going to do. I'm open to other
> alternatives too, the following 2 steps are just my suggestion.

I'm worried that this obligation means that we cannot use glibc-specific
facilities in code shared with gnulib.  For example, look at how the
scratch buffer mechanism landed in gnulib.  If we had DCO contributions
for that mechanism, that wouldn't be possible—and that facility started
out with the firm idea that it would never end up in gnulib.

Thanks,
Florian