From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id C6E7A38515FD for ; Mon, 5 Jul 2021 05:28:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C6E7A38515FD Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-235-SGs_KPg3OMKbNTA61Vghsg-1; Mon, 05 Jul 2021 01:28:29 -0400 X-MC-Unique: SGs_KPg3OMKbNTA61Vghsg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D580FA40C1; Mon, 5 Jul 2021 05:28:27 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-115-5.ams2.redhat.com [10.36.115.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B3EF260C0F; Mon, 5 Jul 2021 05:28:22 +0000 (UTC) From: Florian Weimer To: Carlos O'Donell Cc: Paul Eggert , DJ Delorie , "Dmitry V. Levin" , Bruno Haible , libc-alpha@sourceware.org Subject: Re: Seeking input from developers: glibc copyright assignment policy. References: <1b2ac4c8-0bbf-b7a7-8b05-03d5a71d46f4@cs.ucla.edu> <87eeceqomw.fsf@oldenburg.str.redhat.com> <5adcc865-a2b4-3162-df29-2fb6f30cb4cc@redhat.com> Date: Mon, 05 Jul 2021 07:28:20 +0200 In-Reply-To: <5adcc865-a2b4-3162-df29-2fb6f30cb4cc@redhat.com> (Carlos O'Donell's message of "Mon, 5 Jul 2021 01:00:42 -0400") Message-ID: <8735stqqh7.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2021 05:28:32 -0000 * Carlos O'Donell: > On 7/4/21 7:55 AM, Florian Weimer wrote: >> * Paul Eggert: >>=20 >>> Following up on this, I propose that if DCO'ed contributions are >>> accepted for a file, the file should contain a proper copyright notice= =20 >>> 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. >>=20 >> I would prefer something along the lines =E2=80=9CCopyright The glibc >> Contributors=E2=80=9D. No year or year range, no individual names. Lis= ting >> years is apparently not legally required, and naming individual authors >> is also optional. See: >>=20 >> Copyright Notices in Open Source Software Projects=20 >> > > 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