Seeking input from developers: glibc copyright assignment policy.

[Paul Eggert]

On 7/2/21 6:59 PM, Paul Eggert wrote:

> If gnulib-tool modifies any of those non-FSF copyright notices, then 
> that's a bug that should be fixed.

I've been reminded that gnulib-tool no longer modifies copyright 
notices, so there's no bug here.

> 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.

Following up on this, I propose that if DCO'ed contributions are 
accepted for a file, the file should contain a proper copyright notice 
listing the authors and the range of years that each contributed. E.g., 
the start of the file would look like this:

   /* Word-wrapping and line-truncating streams.
      Copyright (C) 1997-2022 Free Software Foundation, Inc.
      Copyright (C) 2021-2022 Alejandro Davis.
      Copyright (C) 2022 Sharon Carter, Debra Lindsey.
      This file is part of the GNU C Library.

      The GNU C Library is free software; you can redistribute it ...

This issue shouldn't arise for Glibc files shared with Gnulib, as 
they'll still follow the current policy.