Seeking input from developers: glibc copyright assignment policy.

[DJ Delorie]

Paul Eggert <eggert@cs.ucla.edu> writes:
> In contrast, the Glibc library code is explicitly LGPL2.1+ (with 
> emphasis on the "+"). DCO'd contributions to GLibc would be under 
> Glibc's terms, not Linux's. Since Glibc's terms explicitly allow it to 
> be redistributed under later versions of the LGPL,

So far so good.

> a future Glibc release could use LGPL4 (should a version 4 ever come
> out).

Sorta.  A future glibc could distribute under the terms of LGPL4+, but a
future glibc could NOT change the license to "LGPL4+".  I.e. if LGPL2.1
had a problem, we could not fix the problem by preventing LGPL2.1 from
being used.  *We* could use LGPL4, but we can't take away someone else's
right to use LGPL2.1.  Only the copyright owner(s) can do that.