From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id euuGJKxQhWei0A0AWB0awg (envelope-from ) for ; Mon, 13 Jan 2025 12:43:08 -0500 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=GD/HGo00; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 81B2C1E100; Mon, 13 Jan 2025 12:43:08 -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.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=unavailable 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 DB8C01E05C for ; Mon, 13 Jan 2025 12:43:07 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 7B6E33857710 for ; Mon, 13 Jan 2025 17:43:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7B6E33857710 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1736790187; bh=9KKA69RLf7ynwEKvMNdeSYXBwlercCWdrFKp+iFPaTE=; h=Date:Subject:To:Cc:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=GD/HGo00wzFJRhXCYO8KN30YHS2/2UFoOOH52ZtBQ0FatSpxpKiuyAXVxUZlS90ZK EVkiZ8tURUnOMnyHBmw/ZW3jqoZWi6sSmGLT4EYF+Szf/exRiFxEUVuu/hmNaizfYW gTjnMn0RvT86GExN+UKAxwv/1FpCUtTKkR4BLV0A= Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 015193858CDB for ; Mon, 13 Jan 2025 17:42:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 015193858CDB ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 015193858CDB ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1736790142; cv=none; b=qbByw0xdMQxWMCWriZ5dnkj2DnYEHdUt2fYFpUYPl4YZY9RrXXpHcXjHAWh1GdpLsXxqtUM3N4UpzhCaK+5FwrQDjRN3d7QnxVuxdaZIjOowLf9tvA+HnKHlIoi6kvbEPa9ebpLgTXOu0gjc4tTNrq1zsU6iV2AZnaUT9zToE/k= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1736790142; c=relaxed/simple; bh=FfvWJrOGQRS0Bw38UjFGVQojVVsz46bAcnOBt8/Cd+0=; h=DKIM-Signature:DKIM-Signature:Message-ID:Date:MIME-Version: Subject:To:From; b=DEMoy4ZofSrmihSfkotWphlmXb60CaiOEv4NuGcawofqxXHlYGiVBkzlKhbxS/noBC/BWgIXHYYVOen61JtALW5u6BgCfLT32L60mX+xJWL0J3jxYkm/Mz6VvTg+tvbBzjo+orbXYwK+ObJ5O/mgVuUtWl/z5ZDZsR7JGt3WM/Y= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 015193858CDB Received: by simark.ca (Postfix, from userid 112) id 948131E0FE; Mon, 13 Jan 2025 12:42:21 -0500 (EST) Received: from [10.0.0.11] (modemcable238.237-201-24.mc.videotron.ca [24.201.237.238]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 7775B1E05C; Mon, 13 Jan 2025 12:42:18 -0500 (EST) Message-ID: Date: Mon, 13 Jan 2025 12:42:18 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: DCO: Was: Re: Contributing to gdb To: Andrew Burgess , Luis Machado , Tom Tromey , Guinevere Larsen Cc: Andrew Pinski , GDB Development , Eli Zaretskii References: <86538dac-6c3a-4b9e-9de9-3906e645fa4d@redhat.com> <87y16vwbzl.fsf@tromey.com> <74c8b867-f5bb-48f7-9849-11d06e63a3d7@arm.com> <87tta2r5z2.fsf@redhat.com> Content-Language: en-US In-Reply-To: <87tta2r5z2.fsf@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: , From: Simon Marchi via Gdb Reply-To: Simon Marchi Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On 2025-01-13 12:14, Andrew Burgess via Gdb wrote: > Luis Machado via Gdb writes: > >> Hi, >> >> On 6/23/24 23:06, Tom Tromey wrote: >>>>> I just noticed that GDB (and binutils) are currently not accepting >>>>> DCO's like both glibc >>>>> (https://sourceware.org/glibc/wiki/Contribution%20checklist#Copyright_and_license) >>>>> and GCC (https://gcc.gnu.org/contribute.html#legal) are now accepting. >>>>> Has there been any talk about accepting DCOs for gdb and binutils? Or >>>>> has this not been brought up yet? >>> >>> If gcc, glibc, and binutils accept it, then IMO gdb should as well. >>> >>> Tom >> >> Bumping this thread. I noticed there was a mention of aligning gcc/glibc/binutils in terms >> of DCO text. That made me wonder where we stand regarding DCO for gdb [1], and if we really >> want to stray from the other toolchain projects by not making a decision on whether we accept >> it or not. >> >> [1] https://inbox.sourceware.org/binutils/24b26a75-3b3d-4a00-af92-0b7c331e2db7@redhat.com/ > > Based on nothing more than remaining consistent with gcc, binutils, and > glibc, I think we should make the switch to accepting DCO contributions > under the same terms that binutils uses[2] (as well as accepting FSF > assigned contributions). > > I'm volunteering myself to add suitable words to the GDB wiki (based off > the binutils wording), unless anyone objects. Ideally I'd like a +1 > from a couple of other global maintainers with no serious objections, > and I'll go ahead and make the change. > > I think that Eli believes the concerns with FSF assignment are > overblown, and given the information provided, I'm inclined to agree. > But at this point, with other components accepting DCO, I'm not sure > that's really relevant. Unless there's a super compelling reason why > GDB should diverge ... I think we should fall into line with the other > components. I would be happy if we accepted DCO contributions. Having to go through some copyright assignment paperwork is not the end of the world, but it is one of many annoyances that add friction for new contributors (others I think of right now are the use of mailing lists for reviews and our specific coding style that we are unable to enforce with an automated tool). Simon