From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 77l9FqJWimeiTRIAWB0awg (envelope-from ) for ; Fri, 17 Jan 2025 08:09:54 -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=ACfOdGpD; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 428D81E100; Fri, 17 Jan 2025 08:09:54 -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=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 AE65E1E08E for ; Fri, 17 Jan 2025 08:09:53 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3F50A3847EC7 for ; Fri, 17 Jan 2025 13:09:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3F50A3847EC7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1737119393; bh=WERnkQ+4Fypx11q9lVqs2uLwy0ZCEUJbR8vo6FGe1Hg=; h=Date:To:Cc:In-Reply-To:Subject:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=ACfOdGpDndC7u/cCm9BXEoIFClxskV3jx1q54ChbwpV9mrulFs2l5BJUsp5XnZLbR TlXltaq4igGTjCDUaKT6h7C5bz5vYnYpa4lfSSmyWUqkOc744++9d85W6XtjTz/CqO BLzgP8p8uZEtkf6S7EfBbwzYHKDz6fuXIb7uUsfA= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 119B03858406 for ; Fri, 17 Jan 2025 13:09:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 119B03858406 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 119B03858406 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737119352; cv=none; b=Lm2DTdZ72zsjflF5jv5FZXovz1VpCQfe4HDH56adaWAJCMxecNzCooVpKS7lKr4uZGr4Z+NjnRuaJN5n9NPvqj3s8tEXhen4bWg9w+DYXGzwQSmGmUg9EpGJFADmdunyQIZvPBCyAWODUQ2HWvcEMkZLsbGmBVcmvZlQUiOtJuY= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737119352; c=relaxed/simple; bh=5qQ0DBifXkrf2HxhK8sOgeQsVIO8pQvMrgDD5W+pdZw=; h=DKIM-Signature:Date:Message-Id:From:To:Subject; b=SWhK4gZ9CtiNefY5VEZHSYRT3dbbNKrQ74d+PPRNdX82NxQbuUXOLfOtEgSO75Yr/tWaJqmdEHmLagP09YHe7PAK1Vk5Z/DBIe9Jja1s7shkx1G5rjF1DUy2jaqMMLz4CQO+VeqSNgFkIfUWzKYt1yyjIPnOTliC1xUjtz/EvOA= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 119B03858406 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tYm60-0004iU-Hc; Fri, 17 Jan 2025 08:09:08 -0500 Date: Fri, 17 Jan 2025 15:09:04 +0200 Message-Id: <86v7udegen.fsf@gnu.org> To: Florian Weimer Cc: mark@klomp.org, aburgess@redhat.com, luis.machado@arm.com, tom@tromey.com, blarsen@redhat.com, pinskia@gmail.com, gdb@sourceware.org, bkuhn@sfconservancy.org, zoe@fsf.org, ksiewicz@fsf.org In-Reply-To: <87jzatwwl0.fsf@oldenburg3.str.redhat.com> (message from Florian Weimer on Fri, 17 Jan 2025 11:42:19 +0100) Subject: Re: DCO: Was: Re: Contributing to gdb References: <86538dac-6c3a-4b9e-9de9-3906e645fa4d@redhat.com> <87y16vwbzl.fsf@tromey.com> <74c8b867-f5bb-48f7-9849-11d06e63a3d7@arm.com> <87tta2r5z2.fsf@redhat.com> <1fc456f48c4c6f8aa852c911c6234e219a356434.camel@klomp.org> <87jzatwwl0.fsf@oldenburg3.str.redhat.com> 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: Eli Zaretskii via Gdb Reply-To: Eli Zaretskii Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" > From: Florian Weimer > Cc: Andrew Burgess , Luis Machado > , Tom Tromey , Guinevere Larsen > , Andrew Pinski , GDB Development > , Eli Zaretskii , "Bradley M. Kuhn" > , zoe@fsf.org, ksiewicz@fsf.org > Date: Fri, 17 Jan 2025 11:42:19 +0100 > > * Mark Wielaard: > > > I kind of agree with Eli. The current contribution policy is pretty > > clear. But people seem to be constantly confused about the exact > > "rules" of using a DCO and Copyright "ownership". > > > > Specifically what it means for company disclaimers. With the current > > process it is clear the FSF will take care of that. With a DCO it > > suddenly becomes the responsibility of the individual employees to make > > sure the company agrees to them submitting to the project. > > But having a copyright assignment with the FSF does not change that at > all: an individual authorized by an organization to submit contributions > in principle still needs to determine if any particular change can be > contributed according to company rules. I think you are talking about the (relatively rare, AFAIU) situation with employees of companies, such as Google, which have blanket disclaimer for its employees to contribute code. But most contributors are not in that category: they are not "authorized" up front to submit contributions. They need to ask the employer to sign an explicit disclaimer for their contributions, usually for a relatively short period (like 5 or 10 years), after which, if the person still works for the same company, the disclaimer needs to be renewed. As for determining whether any change can be contributed according to company rules, see my other message: the assignment form explicitly asks that question, so the contributor should find out the answer and mention that in the form he/she submits. If they don't know what their employment contract says, they will have to find out when filling the form.