From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>,
"Tim Rühsen" <tim.ruehsen@gmx.de>
Subject: Re: copyright in Germany
Date: Wed, 20 May 2020 00:15:31 +0200 [thread overview]
Message-ID: <122305602.73dpF6A0ll@omega> (raw)
In-Reply-To: <CAEYrNrQ2EAjDdAq_bWia2AYDOW1MrXxXusyS7W0nNZN4FGWJeQ@mail.gmail.com>
Marc Nieper-Wißkirchen wrote:
> > "copyright" here means more "Nutzungsrecht" which you can transfer also
> > in Germany. You still stay the "Urheber".
>
> If transferring the "Nutzungsrecht" is enough, everything should be fine.
You need to verify, though, that no employer of yours has a legal basis
for claiming the "Nutzungsrechte" on the code that you want to contribute.
If the code you write is not related to your job, that is, if you are not
being paid to write it, then the "Nutzungsrechte" belong to you - regardless
whether your employment contract says otherwise. This is guaranteed by
Art. 2.(1) Grundgesetz. (*)
Often it is clear whether something is related to your job. For example,
if you have a manager that tells you what to develop. (*)
If your employer is a university [1], things are less clear. In the past,
some universities have been strict and claimed that the works of their
professors and researchers belong to them. This has changed somewhat around
2000-2005: The slogan "public money - public code" has convinced at least
some universities to allow the code that came out of research projects to
be released under Open Source licenses. In any case, this topic is subject
to negotiation between the professors/researchers and the university.
(*) Disclaimer: I got this infos from a lawyer. But I am not a lawyer. Consult
your own lawyer.
Bruno
[1] https://www.uni-augsburg.de/de/fakultaet/mntf/math/prof/alg/arbeitsgruppe/nieper-wisskirchen/
next prev parent reply other threads:[~2020-05-19 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 7:44 Easy Accurate Reading and Writing of Floating-Point Numbers Marc Nieper-Wißkirchen
2020-05-19 15:10 ` Marc Nieper-Wißkirchen
2020-05-19 15:35 ` Marc Nieper-Wißkirchen
2020-05-19 15:51 ` Paul Eggert
2020-05-19 16:11 ` Marc Nieper-Wißkirchen
2020-05-19 17:23 ` Tim Rühsen
2020-05-19 19:10 ` Marc Nieper-Wißkirchen
2020-05-19 21:25 ` Tim Rühsen
2020-05-19 22:15 ` Bruno Haible [this message]
2020-05-20 9:52 ` copyright in Germany Marc Nieper-Wißkirchen
2020-05-20 13:41 ` Bruno Haible
2020-05-20 12:39 ` Easy Accurate Reading and Writing of Floating-Point Numbers Marc Nieper-Wißkirchen
2020-05-23 12:02 ` Bruno Haible
2020-05-23 12:26 ` Marc Nieper-Wißkirchen
2020-05-23 14:52 ` Bruno Haible
2020-05-23 15:50 ` Marc Nieper-Wißkirchen
2020-05-23 15:33 ` Paul Eggert
2020-06-25 19:19 ` Bruno Haible
2020-06-25 19:33 ` Marc Nieper-Wißkirchen
2020-05-19 22:37 ` Bruno Haible
2020-05-20 10:04 ` Marc Nieper-Wißkirchen
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=122305602.73dpF6A0ll@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=marc.nieper+gnu@gmail.com \
--cc=tim.ruehsen@gmx.de \
/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).