Re: Seeking input from developers: glibc copyright assignment policy.

[Florian Weimer <fweimer@redhat.com>]

* Carlos O'Donell:

> On 7/4/21 7:55 AM, Florian Weimer wrote:
>> * Paul Eggert:
>> 
>>> 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.
>> 
>> I would prefer something along the lines “Copyright The glibc
>> Contributors”.  No year or year range, no individual names.  Listing
>> years is apparently not legally required, and naming individual authors
>> is also optional.  See:
>> 
>>   Copyright Notices in Open Source Software Projects 
>>   <https://www.linuxfoundation.org/en/blog/copyright-notices-in-open-source-software-projects/>
>
> The GCC SC suggestion is as follows:
>
> "The GNU Toolchain Authors"
> https://gcc.gnu.org/pipermail/gcc/2021-June/236217.html
>
> All files that receive DCO'd material for the first time
> would add the following line:
>
> "Copyright The GNU Toolchain Authors"
>
> in the header comment.

I had missed that.  It works for me, both the string and the rule about
adding it to files (that is, only for files with DCO contributions).

Thanks,
Florian