From: Mark Wielaard <mark@klomp.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Marchi <simark@simark.ca>,
luis.machado@arm.com, aburgess@redhat.com, tom@tromey.com,
blarsen@redhat.com, pinskia@gmail.com, gdb@sourceware.org,
pedro@palves.net, nickc@redhat.com,
"Bradley M. Kuhn" <bkuhn@sfconservancy.org>,
zoe@fsf.org, ksiewicz@fsf.org
Subject: Re: DCO: Was: Re: Contributing to gdb
Date: Wed, 15 Jan 2025 12:49:37 +0100 [thread overview]
Message-ID: <20250115114937.GC25056@gnu.wildebeest.org> (raw)
In-Reply-To: <86a5bttkh8.fsf@gnu.org>
Hi Eli,
On Tue, Jan 14, 2025 at 06:42:59PM +0200, Eli Zaretskii via Gdb wrote:
> As long as we are only considering good-faith mistakes, not deliberate
> lies about the authorship and copyright rights, the difference between
> CA and DCO is that with the former, one is _required_ to provide a
> disclaimer from the employer (if that is relevant; it isn't always),
> so this aspect is pretty much in the face of the contributor. By
> contrast, with DCOs one is just asked to declare that he/she has the
> rights to contribute the code. So people might, by omission, make the
> mistake of not obtaining the employer's agreement, perhaps because
> they are not aware of these aspects, or forget, or...
One thing we could do to make it easier for people contributing work
for their employer is follow what the Samba does for their DCO [1].
Someone wishing to contribute work under the DCO simply first sends a
copy of the whole DCO from their corporate email address declaring
they have permission to contribute to Samba from their employer under
the indicated licenses to a special "contributing" email address. The
Samba project then keeps a copy of that email as a record that the
submitter has the rights to contribute code.
We could ask the FSF copyright-clerk to do that for us. After the
copyright-clerk receives that declaration people are then fine to
submit Signed-off-by patches from their employers email address.
It doesn't prevent all mistakes, but at least makes clear that if you
contribute on behave of your company you have to check you have the
rights. And the explicit email has the added benefit that we can show
we had a company disclaimer on file.
Cheers,
Mark
[1] https://www.samba.org/samba/devel/copyright-policy.html
next prev parent reply other threads:[~2025-01-15 11:50 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 [this message]
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=20250115114937.GC25056@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=aburgess@redhat.com \
--cc=bkuhn@sfconservancy.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=ksiewicz@fsf.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 \
--cc=zoe@fsf.org \
/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