From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id fGigEpiWh2do3g8AWB0awg (envelope-from ) for ; Wed, 15 Jan 2025 06:06:00 -0500 Received: by simark.ca (Postfix, from userid 112) id 3DA151E100; Wed, 15 Jan 2025 06:06:00 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.0 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 9BF5A1E08E for ; Wed, 15 Jan 2025 06:05:59 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3982B385DDDA for ; Wed, 15 Jan 2025 11:05:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3982B385DDDA Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id CEF8B385DDCD for ; Wed, 15 Jan 2025 11:05:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CEF8B385DDCD Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org CEF8B385DDCD Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=45.83.234.184 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1736939106; cv=none; b=byRUKWfc73x/yed363+J929eiy4ujYZDVzv6DqE/sE27wB2CtuwWqb9UJf0Tr4cci7uAzyhzjJAVIDnthYqM0SZ8q6xlrdjiHRqWxBK5ymXcg2nDPBsJA6lw0+r/Ha9OtDr/FjyCTQxx5rySgIKtSSbtoQq/lsiElCoRix4WsrA= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1736939106; c=relaxed/simple; bh=c9FGsi5Wd2sL8SJWupK/cAtsTH3M1zIZffZJ+l1XsPo=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=Ppxlkpl7OzBQtRmYWE/yO1k0QPECdzP5NG2iG7QEn1RbSzqXtKc9J02jzT7Wd/AxjtWdJdq5NsMq5gjP9luk92lYCRtOtm6M8Z8fMnItvi4YicsHSiZ5DAZMCfuXs+/Mbhxrcew+9e8PPFSKXmA0jPNmO4TWYUGbMgPADWOgong= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CEF8B385DDCD Received: by gnu.wildebeest.org (Postfix, from userid 1000) id F0EC53021E82; Wed, 15 Jan 2025 12:05:03 +0100 (CET) Date: Wed, 15 Jan 2025 12:05:03 +0100 From: Mark Wielaard To: Luis Machado Cc: Andrew Burgess , Tom Tromey , Guinevere Larsen , Andrew Pinski , GDB Development , Eli Zaretskii , Pedro Alves , Nick Clifton , "Bradley M. Kuhn" , zoe@fsf.org, ksiewicz@fsf.org Subject: Re: DCO: Was: Re: Contributing to gdb Message-ID: <20250115110503.GA25056@gnu.wildebeest.org> References: <86538dac-6c3a-4b9e-9de9-3906e645fa4d@redhat.com> <87y16vwbzl.fsf@tromey.com> <74c8b867-f5bb-48f7-9849-11d06e63a3d7@arm.com> <87tta2r5z2.fsf@redhat.com> <00ba936a-6aa9-4d1d-8b1a-b5459b696289@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ba936a-6aa9-4d1d-8b1a-b5459b696289@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hi Luis, On Tue, Jan 14, 2025 at 09:49:34AM +0000, Luis Machado via Gdb wrote: > Also, I've seen DCO's being sold partially as a mechanism that > doesn't require contributors to share personal information, due to > privacy concerns. I don't think that is true from my reading of it, > given we absolutely need to know how to reach out to the > contributor/employer of the contributor in case the need arises. And > that is not even considering things like the contributor passing > away, disappearing etc. There is indeed some confusion about anonymous and/or pseudonomous contributions. Where the main issue really is that there is a difference between someones "real" (legal) name and how they identify themselves. Various projects have handled that in different ways. The current proposed clarification [1] for the GCC project reads: The name you use as your identity should not be an anonymous id or false name that misrepresents who you are. A known identity can be the committer's real, birth or legal name, but can also be an established (online) identity. It is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution. You should not deliberately use a name or email address that hides your identity. When you wish to only contribute under an (anonymous) pseudonym, or when you require an explicit employer disclaimer, then following the FSF assignment process is more appropriate. Cheers, Mark [1] https://inbox.sourceware.org/gcc-patches/8faf15ae-1009-8da9-12c8-c0cd6a0ec9e4@pfeifer.com/