From: Werner LEMBERG <wl@gnu.org>
To: kelly@prtime.org
Cc: 19479@debbugs.gnu.org, assign@gnu.org
Subject: bug#19479: Copyright issue
Date: Sun, 11 Jan 2015 07:33:00 +0100 (CET) [thread overview]
Message-ID: <20150111.073300.172574682.wl@gnu.org> (raw)
In-Reply-To: <uqK9s2EJ0lHC70uZbUunNN6qv171s49r3sesM5HhMaD@local>
>> No, the assignment document is just for the Emacs code you wrote
>> and whose copyright you own. It simply doesn't apply to the code
>> whose copyright you don't own (which normally only happens when the
>> copyright is owned by your employer).
>
> I don't have a copy of it handy, but if that's the way it's worded,
> then you're right, it wouldn't be illegal for me to sign it. It
> would only be immoral. It would be legally vacuous, and deceptive,
> leading to doubt about my intent.
Perhaps slightly off-topic, but quite relevant IMHO in a global
perspective:
It is *not* possible to create not-copyrighted code in some
jurisdictions like Germany. Whatever you write, it is by default
copyrighted by you (regardless whether there is a `public domain' line
or not), and you have to explicitly disclaim or reassign the
copyright.
For this reason, it is *much* better to use a license like CC0 instead
of a public domain notice, since this covers the `public domain' idea
in virtually all countries. Actually, this is what the FSF recommends
(https://www.gnu.org/licenses/license-list.en.html#CC0), and I guess
this works for emacs also, since it works already for GNU (according
to https://gcc.gnu.org/contribute.html#legal).
Werner
next prev parent reply other threads:[~2015-01-11 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zj9sm0q8.fsf@fencepost.gnu.org>
2015-01-09 21:00 ` bug#19479: Copyright issue Kelly Dean
2015-01-09 21:49 ` Kelly Dean
2015-01-09 23:47 ` Stefan Monnier
2015-01-10 1:18 ` Kelly Dean
2015-01-11 1:39 ` Stefan Monnier
2015-01-11 3:20 ` Kelly Dean
2015-01-11 6:33 ` Werner LEMBERG [this message]
2015-01-12 15:38 ` Richard Stallman
2015-01-10 19:29 ` Richard Stallman
2015-01-09 2:37 bug#19479: Package manager vulnerable Stefan Monnier
2015-01-08 21:06 ` Kelly Dean
2015-01-08 5:29 ` Kelly Dean
2015-01-09 6:59 ` bug#19479: Copyright issue (was: Re: bug#19479: Package manager vulnerable) Kelly Dean
2015-01-09 15:17 ` bug#19479: Copyright issue Stefan Monnier
2015-01-09 15:29 ` David Kastrup
2015-01-09 19:57 ` Kelly Dean
[not found] ` <EitH3yok1Itmynw5Ex1Vi3AuvkREurR1ccm1J5MQD4E@local>
2015-01-09 20:24 ` Glenn Morris
[not found] ` <0etwzzu2gd.fsf@fencepost.gnu.org>
2015-01-09 20:32 ` Glenn Morris
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150111.073300.172574682.wl@gnu.org \
--to=wl@gnu.org \
--cc=19479@debbugs.gnu.org \
--cc=assign@gnu.org \
--cc=kelly@prtime.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).