From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, psmith@gnu.org
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Tue, 15 Jun 2021 19:14:10 +0200 [thread overview]
Message-ID: <5190941.cROn723324@omega> (raw)
In-Reply-To: <5ac569a3c976caf3658e652fea843dc9dc69f76a.camel@gnu.org>
Paul Smith wrote:
> I worry that people think that a DCO is a hassle-free
> replacement for an employer's copyright assignment. Maybe, in some
> jurisdictions, it even can be.
>
> But as far as I'm aware in the U.S. (and other countries) you can't
> just declare that your employer doesn't have any copyright to work you
> do, even on your own time.
Yes, it depends on the jurisdiction. In Germany, the law gives the
employee the copyright on works created on his own time (§ 15 UrhG,
§ 69b UrhG, § 2.1 GG); the employment contract can influence further
details. The situation appears to be very different in the U.S.
Bruno
next prev parent reply other threads:[~2021-06-15 17:14 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 [this message]
2021-06-16 11:31 ` Eli Zaretskii
2021-06-15 21:08 ` Pádraig Brady
2021-06-16 13:10 ` Paul Smith
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=5190941.cROn723324@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=psmith@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).