From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id yzqpF1Xxj2e9mRYAWB0awg (envelope-from ) for ; Tue, 21 Jan 2025 14:11:17 -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=H1mWTsrm; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 515FE1E100; Tue, 21 Jan 2025 14:11:17 -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 CBBEE1E05C for ; Tue, 21 Jan 2025 14:11:15 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5863A3857C7B for ; Tue, 21 Jan 2025 19:11:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5863A3857C7B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1737486675; bh=YDXCGYVDj7++Qjo8O8zhFrEYwLNR1LkeShZf4GSmwvQ=; 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=H1mWTsrmtx88da1EmOdmf0NL/wKFtDAqUWtQPdl1UXoo3jUVPYivPbzfRK10vcNFA DME1Ry/IoBm9NPRTSN0X9NnYIX7BtC1o1qIG1o/lo2U6c54gQHDu66E+TaRfS3Pi6q RzaIS08tWSDQbSvu6YwxGNIkbgJU72ZWeZkhf/DU= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTP id 4C05E3858CD1 for ; Tue, 21 Jan 2025 19:10:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4C05E3858CD1 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 4C05E3858CD1 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737486629; cv=none; b=ResvsN1WS9/Kmf3zZz6E2CiRJQraSyAKs06kZ3nSEUmIlujaQDNN8PtVWJwO4cQ2GKZi8IWEucXNkNGxhML4Y0a/hks9iaoNKTt3CvMe1OOsP9/QOzPv4DhkbF44Sa9Q0UsHY4DthRb0OeqT/tQZRFmn9mgcHrxi02zv4DuMHEE= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737486629; c=relaxed/simple; bh=ecxjygVwNX2huiaW8jBdu0iW89wIqsJT+aIquqKCen4=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=noub/ifqUm+cBnTs9Qfc50qjKrEfu70BK2nlubUX+H/wdf/ihBlRtt/MOXUV94WXHJ7i/yJlfZCGi0JejXXeHO3vVxpqLM55gS0aeagL4iLS0MJzQfh521wYy/pIh66f8NGR4Lebc3uxWHclRwdLaJZ460TW0uLP+RhytWaJZ9Y= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4C05E3858CD1 Received: from mail-pl1-f197.google.com (mail-pl1-f197.google.com [209.85.214.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-339-pqQG834fN6ub2SPa9kHZ7w-1; Tue, 21 Jan 2025 14:10:25 -0500 X-MC-Unique: pqQG834fN6ub2SPa9kHZ7w-1 X-Mimecast-MFC-AGG-ID: pqQG834fN6ub2SPa9kHZ7w Received: by mail-pl1-f197.google.com with SMTP id d9443c01a7336-21631cbf87dso113969925ad.3 for ; Tue, 21 Jan 2025 11:10:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737486625; x=1738091425; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YDXCGYVDj7++Qjo8O8zhFrEYwLNR1LkeShZf4GSmwvQ=; b=Yne39LdtSKEX/mIk8RJhWp+vGfz3u/HmjpydrBbfUnib8SRLIy+qyq47kqtjAxlF1M 7QuS1nE9yfVgIVVYtwUKyT170N3d1JRXfaKI5MukTkEgVlorX4R9qFeX35nGdkQGcMkD pOcRW/YjfGtPQIlJ0sWemkbSbyz9/6uf4QTi3ALXdWDavt7WvsF2Lly+mJoA18iRvO5a RvNQo/M9ybVVECOtFHQN4iEoAO9F+udFqVhzovfdb1uGcT3adv8QSfTr7Bsn4B/qgfkJ Cls6B6/wpxBKH92vpjNm/95SHTBQS8jO2bsJ3uspGwceq7SdGPm30ny7Z84MDvlNJ76F lm6w== X-Gm-Message-State: AOJu0Yz3Tsroh9dbY1X2g0EsE730KrCQiXqcSbsV2Q9kLRb7m7w890Rn u553RPRJqaZdU9xDMSNVFH8pGqK+DmZjNnLDL7h0zsCUoKWhrlbTFNd7Y4D/pIMRJCaeXEtlHLE Py8nQgz16OPFjFPSexFJCCDJFiPUmzs455t6Oc53/exk+0UrR X-Gm-Gg: ASbGncvoFZ0C92VymHdvHS6QZoWqQ/N1JoY5eF/cTt43FfD7/9xo/EY1gL4jKuLcLV9 EqvkcqNKfY2R0HcFeO6i14jQv7DnaUX04A9sLO1pmk0mqSLMfC6Up/4yjEtKxJPmyYR8dvQGAvB FHdwPyPbnrKJZuGHRC59JX9eP9SJ1sDoXoJ6nRuOs1d7O+XBOmulntA2KliIc9OpB3nXxvo1AiR L2J0CZOrQ8ByBhIjjpw7iKV7MrfzX1vlJ7110U0i0stTMnkyGThuoF1qs+TxLXh9PoFyF09FEWx FApq2A== X-Received: by 2002:a17:903:1d2:b0:216:393b:23d4 with SMTP id d9443c01a7336-21c352ddf89mr288127335ad.11.1737486624719; Tue, 21 Jan 2025 11:10:24 -0800 (PST) X-Google-Smtp-Source: AGHT+IEowuE9CS1bQSpI81F9PEaQeCcCt9KvgUrGaSTVNB1TXHuphMM8QFsdw2cq1LOoFEOgZqz5/A== X-Received: by 2002:a17:903:1d2:b0:216:393b:23d4 with SMTP id d9443c01a7336-21c352ddf89mr288126875ad.11.1737486624355; Tue, 21 Jan 2025 11:10:24 -0800 (PST) Received: from ?IPV6:2804:14d:8084:9a69::1000? ([2804:14d:8084:9a69::1000]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-21c2ceb73ccsm82791345ad.58.2025.01.21.11.10.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Jan 2025 11:10:23 -0800 (PST) Message-ID: Date: Tue, 21 Jan 2025 16:10:19 -0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: DCO: Was: Re: Contributing to gdb To: Eli Zaretskii , Florian Weimer Cc: gdb@sourceware.org, aburgess@redhat.com, luis.machado@arm.com, tom@tromey.com, blarsen@redhat.com, pinskia@gmail.com References: <86538dac-6c3a-4b9e-9de9-3906e645fa4d@redhat.com> <87y16vwbzl.fsf@tromey.com> <74c8b867-f5bb-48f7-9849-11d06e63a3d7@arm.com> <87tta2r5z2.fsf@redhat.com> <86bjwavcux.fsf@gnu.org> <87o705wwsd.fsf@oldenburg3.str.redhat.com> <86y0z9egqu.fsf@gnu.org> In-Reply-To: <86y0z9egqu.fsf@gnu.org> X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: xgfz25tFAl4hAoDRnhi7KPTO21Eom8Ud80gBR2WaK38_1737486625 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed 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: Guinevere Larsen via Gdb Reply-To: Guinevere Larsen Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On 1/17/25 10:01 AM, Eli Zaretskii wrote: >> From: Florian Weimer >> Cc: Andrew Burgess , Eli Zaretskii , >> luis.machado@arm.com, tom@tromey.com, blarsen@redhat.com, >> pinskia@gmail.com >> Date: Fri, 17 Jan 2025 11:37:54 +0100 >> >> * Eli Zaretskii via Gdb: >> >>> I mostly fear that by accepting DCOs we will open ourselves to >>> contributions from people who are not authorized to contribute their >>> code (e.g., it was copied from somewhere, or their employment contract >>> makes all their code the property of their employer, or something of >>> that nature). DCO makes it much easier to submit code based on >>> incorrect understanding of what the DCO text says, so the probability >>> for honest mistakes is higher than with CA. >> It is possible that someone signs a copyright assignment without being >> authorized to do so, which is exactly the same problem. As far as I >> know, the FSF doesn't verify that the signer has been authorized by the >> organization that owns the rights. > verification is not the issue here, the issue is whether the > contributor is at all aware of this aspect. > > The copyright assignment process includes the contributor filling a > form, where he/she is asked whether they have an employer that should > be included in the process: > > [Do you have an employer who might have a basis to claim to own > your changes? Do you attend a school which might make such a claim?] > > I think reasonable people will always know to answer those questions, > or at least ask the FSF copyright clerk what is the meaning of "an > employer who might have a basis to claim to own your changes" (and > similarly the meaning of the question about the school). > > By contrast, AFAIK there's no such process in sending the DCO. > We could have a similar process. A way to ensure that a contributor has seen the DCO could be setting up a bot, and whenever an email with an SOB with a never before seen email, the bot sends a boilerplate "Welcome to the project. Before we can accept, please be sure to review the following, and reply in line that you meet the conditions." And after the reply, we can be reasonably sure the contributor knows what a DCO entails. When I mentioned this to Andrew, he had a simpler idea, just to setup some "gdb-dco" list, where contributors who want to contribute with DCO would send the DCO wording with an "OK" or the name or pseudonym they'll be using to contribute. There's less automation and a little more annoyances to end contributors, but it is easier than signing a contract - especially for contributors whose mother tongue isn't english - and has a result immediately, as opposed to waiting for over a month at times. -- Cheers, Guinevere Larsen She/Her/Hers