From: Paul Smith <psmith@gnu.org>
To: Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Wed, 16 Jun 2021 09:10:20 -0400 [thread overview]
Message-ID: <fea1faed5373eaadf33d5acc2621c8ff9e6fe447.camel@gnu.org> (raw)
In-Reply-To: <d142fc38-8398-ebf6-04a7-899b25250601@draigBrady.com>
On Tue, 2021-06-15 at 22:08 +0100, Pádraig Brady wrote:
> Yes the fact that one needs to repeat this process as one changes
> employers is very awkward.
This is exactly what I was worried about with my previous message:
people saying "it's awkward to get my employer to assign copyright so
I'd rather use a DCO" when they are not legally allowed to do that.
A DCO is not a magic bullet. If your employer has copyright to the
changes you made then the DCO is useless to you because the ownership
is not yours to certify; you'll STILL have to get your employer to
agree to it. If you have the copyright yourself then you don't need
your employer to sign anything in the first place!
Allowing contributors to follow a simpler process doesn't make the
situation less complicated, it just makes it easier to ignore. But
ignoring it doesn't make it go away.
The assignment is awkward, and it is extra effort, but that effort is
not useless or wasted. IMO it's important for the project that people
pay attention to this and handle it BEFORE their code is accepted.
next prev parent reply other threads:[~2021-06-16 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 20:39 Seeking input from developers: glibc copyright assignment policy Paul Eggert
2021-06-14 22:46 ` Bruno Haible
2021-06-15 12:03 ` Eric Blake
2021-06-15 16:32 ` Paul Smith
2021-06-15 17:14 ` Bruno Haible
2021-06-16 11:31 ` Eli Zaretskii
2021-06-15 21:08 ` Pádraig Brady
2021-06-16 13:10 ` Paul Smith [this message]
2021-06-16 11:47 ` Dmitry V. Levin
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fea1faed5373eaadf33d5acc2621c8ff9e6fe447.camel@gnu.org \
--to=psmith@gnu.org \
--cc=bug-gnulib@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).