Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: Luis Machado <luis.machado@arm.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 16:46:14 +0000	[thread overview]
Message-ID: <8734hlqr6x.fsf@redhat.com> (raw)
In-Reply-To: <00ba936a-6aa9-4d1d-8b1a-b5459b696289@arm.com>

Luis Machado <luis.machado@arm.com> writes:

> On 1/13/25 17:14, Andrew Burgess wrote:
>> Luis Machado via Gdb <gdb@sourceware.org> 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.
>> 
>> [2] https://sourceware.org/binutils/wiki/HowToContribute
>> 
>> Thanks,
>> Andrew
>> 
>
> I did some reading on DCO's and I have mixed feelings. I haven't followed
> discussions about DCO's on the other GNU tools projects, so it is not clear
> to me yet how/if they addressed the shortcomings of DCO's.
>
> 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.

I wonder how an attempt to switch licence for GDB would work given we
statically link against libbfd, which can already include DCO code?

Thanks,
Andrew


  parent reply	other threads:[~2025-01-14 16:47 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
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 [this message]
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=8734hlqr6x.fsf@redhat.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=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