From: Luis Machado via Gdb <gdb@sourceware.org>
To: Simon Marchi <simark@simark.ca>,
Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
Guinevere Larsen <blarsen@redhat.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
GDB Development <gdb@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>, Pedro Alves <pedro@palves.net>,
Nick Clifton <nickc@redhat.com>
Subject: Re: DCO: Was: Re: Contributing to gdb
Date: Tue, 14 Jan 2025 15:28:41 +0000 [thread overview]
Message-ID: <4ec99ea7-fc48-49ed-a75a-a5a06370d6ad@arm.com> (raw)
In-Reply-To: <7ac6e62d-1969-41b9-be3f-a2f70344a3eb@simark.ca>
On 1/14/25 15:10, Simon Marchi wrote:
>
>
> On 2025-01-14 04:49, Luis Machado via Gdb wrote:
>> While I agree having gdb be the sole bureaucratic entity not accepting DCO
>> with the other GNU tools projects accepting it (in particular because we
>> share code with binutils, so technically we'd have to make a joint decision),
>> DCO's don't seem to come for free, as we need to track each and every one of
>> those contributions so we can refer back to them when/if we ever decide to
>> update/switch licenses or if a legal problem arises.
>>
>> The contributions are not gdb's, they are still owned by their contributors,
>> but those are granted the right to be distributed by gdb under the GPL, if I
>> understand it correctly.
>>
>> That is potentially a lot of work, and really needs to be taken seriously if
>> we really want to do things by the book. Makes me wonder how we're supposed
>> to track this.
>
> My understanding is that the tracking is done using the "Signed-off-by"
> git trailer. I don't know of any project tracking contributions more
> extensively than that.
>
> Simon
That's what I see as well. But my understanding is that the identifier used
in the Signed-off-by needs to translate to a reachable entity/person. If ever
there is a problem with a particular contribution, whether it needs to be
reverted or the code ownership is being challenged, that person needs to
be reachable so appropriate action could be taken to rectify the situation.
Also, if the project ever wants to do a change/move to new licensing terms,
the project will need the approval of these contributors. Hence my observation
that this seems like a significant amount of work (for the project) that needs to
be done to ensure these contributors are always known and reachable.
From reading things about DCO, it seems to rely on country-specific
interpretations and legal systems. The Signed-off-by git tag may or
may not be enough guarantee compared to CLA's.
Obvious disclaimer, this is from doing some research on the topic. I don't
have a background in legal. But it doesn't seem to me like DCO's are as simple
as just adding tags to git commits as some seem to assume.
next prev parent reply other threads:[~2025-01-14 15:29 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 21:52 shaunak saha via Gdb
2024-06-17 12:21 ` Guinevere Larsen via Gdb
2024-06-17 15:00 ` DCO: Was: " Andrew Pinski via Gdb
2024-06-17 15:57 ` Guinevere Larsen via Gdb
2024-06-17 16:07 ` Jan Beulich via Gdb
2024-06-17 16:32 ` Eli Zaretskii via Gdb
2024-06-17 16:37 ` Guinevere Larsen via Gdb
2024-06-17 16:45 ` Eli Zaretskii via Gdb
2024-06-17 18:18 ` Guinevere Larsen via Gdb
2024-06-17 18:24 ` Andrew Pinski via Gdb
2024-06-17 19:57 ` Eli Zaretskii via Gdb
2024-06-17 19:37 ` Eli Zaretskii via Gdb
2024-06-17 19:48 ` Guinevere Larsen via Gdb
2024-06-18 12:25 ` Eli Zaretskii via Gdb
2024-06-27 17:48 ` Thiago Jung Bauermann via Gdb
2024-06-27 19:03 ` Eli Zaretskii via Gdb
2024-06-29 3:27 ` Thiago Jung Bauermann via Gdb
2024-06-17 19:15 ` Arsen Arsenović via Gdb
2024-06-18 11:54 ` Eli Zaretskii via Gdb
2024-06-28 0:43 ` NightStrike via Gdb
2024-06-28 6:08 ` Eli Zaretskii via Gdb
2024-06-21 13:20 ` Nick Clifton via Gdb
2024-06-23 22:06 ` Tom Tromey
2024-12-02 8:56 ` Luis Machado via Gdb
2025-01-13 17:14 ` Andrew Burgess via Gdb
2025-01-13 17:32 ` Eli Zaretskii via Gdb
2025-01-17 10:37 ` Florian Weimer via Gdb
2025-01-17 10:44 ` Luis Machado via Gdb
2025-01-17 13:01 ` Eli Zaretskii via Gdb
2025-01-21 19:10 ` Guinevere Larsen via Gdb
2025-01-13 17:42 ` Simon Marchi via Gdb
2025-01-14 15:17 ` automated coding style tool (was: RE: DCO: Was: Re: Contributing to gdb) Aktemur, Tankut Baris via Gdb
2025-01-14 17:11 ` automated coding style tool Tom Tromey
2025-01-14 17:14 ` Luis Machado via Gdb
2025-01-14 17:23 ` Simon Marchi via Gdb
2025-01-14 23:04 ` Tom Tromey
2025-01-15 6:03 ` Maciej W. Rozycki
2025-01-18 18:39 ` Tom Tromey
2025-01-22 22:36 ` Maciej W. Rozycki
2025-01-15 10:20 ` Luis Machado via Gdb
2025-01-15 12:24 ` Aktemur, Tankut Baris via Gdb
2025-01-17 13:42 ` Andrew Burgess via Gdb
2025-01-17 15:13 ` Joel Brobecker via Gdb
2025-01-17 15:55 ` Simon Marchi via Gdb
2025-01-17 17:36 ` Phi via Gdb
2025-01-17 19:27 ` Simon Marchi via Gdb
2025-01-18 18:56 ` Tom Tromey
2025-01-20 11:30 ` Luis Machado via Gdb
2025-01-14 17:15 ` Simon Marchi via Gdb
2025-01-14 9:49 ` DCO: Was: Re: Contributing to gdb Luis Machado via Gdb
2025-01-14 13:56 ` Eli Zaretskii via Gdb
2025-01-14 15:10 ` Simon Marchi via Gdb
2025-01-14 15:28 ` Luis Machado via Gdb [this message]
2025-01-14 15:47 ` Simon Marchi via Gdb
2025-01-14 16:33 ` Luis Machado via Gdb
2025-01-14 16:42 ` Eli Zaretskii via Gdb
2025-01-15 11:49 ` Mark Wielaard
2025-01-14 16:46 ` Andrew Burgess via Gdb
2025-01-15 11:25 ` Mark Wielaard
2025-01-15 6:20 ` Maciej W. Rozycki
2025-01-15 11:05 ` Mark Wielaard
2025-01-14 15:28 ` Mark Wielaard
2025-01-17 10:42 ` Florian Weimer via Gdb
2025-01-17 13:09 ` Eli Zaretskii via Gdb
2025-01-19 16:37 ` Mark Wielaard
2025-01-27 15:55 ` DCO Bradley M. Kuhn via Gdb
2025-01-27 16:36 ` DCO Krzysztof Siewicz via Gdb
2025-01-27 17:22 ` DCO Guinevere Larsen via Gdb
2025-01-31 19:36 ` DCO Mark Wielaard
2024-06-18 13:32 ` DCO: Was: Re: Contributing to gdb Michael Matz via Gdb
2024-06-19 7:38 ` shaunak saha via Gdb
2024-06-19 12:07 ` Guinevere Larsen via Gdb
2024-06-25 22:27 ` shaunak saha via Gdb
2024-06-26 17:38 ` Tom Tromey
2024-06-28 7:23 ` shaunak saha via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ec99ea7-fc48-49ed-a75a-a5a06370d6ad@arm.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=luis.machado@arm.com \
--cc=nickc@redhat.com \
--cc=pedro@palves.net \
--cc=pinskia@gmail.com \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox