From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
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
Subject: Re: DCO: Was: Re: Contributing to gdb
Date: Fri, 17 Jan 2025 15:09:04 +0200 [thread overview]
Message-ID: <86v7udegen.fsf@gnu.org> (raw)
In-Reply-To: <87jzatwwl0.fsf@oldenburg3.str.redhat.com> (message from Florian Weimer on Fri, 17 Jan 2025 11:42:19 +0100)
> From: Florian Weimer <fweimer@redhat.com>
> Cc: Andrew Burgess <aburgess@redhat.com>, Luis Machado
> <luis.machado@arm.com>, Tom Tromey <tom@tromey.com>, Guinevere Larsen
> <blarsen@redhat.com>, Andrew Pinski <pinskia@gmail.com>, GDB Development
> <gdb@sourceware.org>, Eli Zaretskii <eliz@gnu.org>, "Bradley M. Kuhn"
> <bkuhn@sfconservancy.org>, 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.
next prev parent reply other threads:[~2025-01-17 13:09 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
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 [this message]
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=86v7udegen.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=bkuhn@sfconservancy.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=fweimer@redhat.com \
--cc=ksiewicz@fsf.org \
--cc=luis.machado@arm.com \
--cc=mark@klomp.org \
--cc=pinskia@gmail.com \
--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