Seeking input from developers: glibc copyright assignment policy.

[Joseph Myers]

On Fri, 2 Jul 2021, Paul Eggert wrote:

> On 7/2/21 3:33 PM, Carlos O'Donell wrote:
> 
> > gnulib has been including non-FSF copyrighted material in various
> > modules (that include the files below) for a long time.
> 
> If gnulib-tool modifies any of those non-FSF copyright notices, then that's a
> bug that should be fixed. It doesn't modify the first one, so we should be OK
> there. (I didn't check the others.)
> 
> This raises another issue. What will be the glibc policy about putting
> copyright notices on files containing DCOed material? Will there be a separate
> copyright notice for each contributor? Linux doesn't do that - which is too
> sloppy for glibc, surely. I don't know what GCC plans to do.

I suggest using the same form as agreed by the GCC Steering Committee for 
use in GCC:

  Copyright The GNU Toolchain Authors.

with no date specified and not naming individual contributors, following 
the recommendations at 
<https://www.linuxfoundation.org/en/blog/copyright-notices-in-open-source-software-projects/>.

-- 
Joseph S. Myers
joseph@codesourcery.com