From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from authenticated.a-painless.mh.aa.net.uk (painless-a.thn.aa.net.uk [IPv6:2001:8b0:0:62::26]) by sourceware.org (Postfix) with ESMTPS id 20289385741E for ; Wed, 16 Jun 2021 14:08:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 20289385741E Received: from cartman.offog.org ([2001:8b0:83b:b53f::a]) by painless-a.thn.aa.net.uk with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ltWDm-0004pZ-Bs for libc-alpha@sourceware.org; Wed, 16 Jun 2021 15:08:46 +0100 Received: from ats by cartman.offog.org with local (Exim 4.94.2) (envelope-from ) id 1ltWDj-0005f1-5z for libc-alpha@sourceware.org; Wed, 16 Jun 2021 15:08:43 +0100 From: Adam Sampson To: Carlos O'Donell via Libc-alpha Subject: Re: Seeking input from developers: glibc copyright assignment policy. References: Date: Wed, 16 Jun 2021 15:08:43 +0100 In-Reply-To: (Carlos O'Donell via Libc-alpha's message of "Mon, 14 Jun 2021 14:52:03 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, TXREP, T_FILL_THIS_FORM_SHORT autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Wed, 16 Jun 2021 14:08:48 -0000 Carlos O'Donell via Libc-alpha writes: > The changes to accept patches with or without FSF copyright assignment > would be effective on August 2nd, and would apply to all open > branches. This sounds like a sensible approach. One suggestion I'd make here is to have some clear guidance on how you want to manage copyright notices in source files as part of the development process, since there's quite a bit of variation in practice here in other projects. For example, do you want DCO contributors to add copyright notices to individual files as part of their changes, or will the maintainers add them when merging, or will you collect them in a separate file? How do you prefer (international) names and email addresses to be formatted? (There is some guidance on copyright notices in the GNU Information for Maintainers, but it's mostly aimed at FSF-copyright projects at the moment: https://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices ) Thanks, -- Adam Sampson