From: Kelly Dean <kelly@prtime.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: assign@gnu.org, 19479@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: Copyright issue
Date: Fri, 09 Jan 2015 19:57:35 +0000 [thread overview]
Message-ID: <EitH3yok1Itmynw5Ex1Vi3AuvkREurR1ccm1J5MQD4E@local> (raw)
In-Reply-To: <jwvmw5s0yu5.fsf-monnier+emacsbugs@gnu.org>
Stefan Monnier wrote:
>> 1. My code is PD. (In case the FSF disputes this fact, I'm attaching
>> a signed document to establish it.)
>
> It can't be PD. You're simply confused about it. It will only be PD 75
> years after your death (or something like that). Until then, all you
> can do is sign paperworks, and currently for Emacs contributions we
> require this paperwork to be a copyright assignment rather than
> a disclaimer.
GNU's own website says it can be PD. The documents at the three links I sent you start with:
⌜I'd like to ask you to sign a disclaimer for the manual, thus putting it in the public domain.⌝
⌜I'd like to ask you to sign a disclaimer for the program, thus putting it in the public domain.⌝
⌜I'd like to ask you to sign a disclaimer for your changes, thus putting them in the public domain.⌝
Notice the ⌜thus putting them in the public domain⌝.
Also, do you claim that SQLite is not PD? The author, Richard Hipp, says it's PD, and the many millions of users of SQLite, including many major companies with lots of copyright lawyers, accept the legal fact that it's PD. And Richard Hipp is not dead.
Also, do you claim that feedmail.el is not PD? The first lines of it are:
;;; feedmail.el --- assist other email packages to massage outgoing messages
;;; This file is in the public domain.
;; This file is part of GNU Emacs.
next prev parent reply other threads:[~2015-01-09 19:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwv4ms03cj3.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <quFzgVhBDz7zhUp0lS56OK32kQQjWsi4jSGZeullV6K@local>
[not found] ` <iKceXlDJbawOYczzAAZidbwV0Sq68CGaBNzyymlTMR2@local>
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 [this message]
2015-01-09 20:24 ` Glenn Morris
2015-01-09 20:32 ` Glenn Morris
[not found] ` <rt-3.4.5-910-1421783402-547.973211-5-0@rt.gnu.org>
[not found] ` <sXpSIlT9bkMLz7zWFLWTjm38mvYqlezH8vXlii5uxqC@local>
2015-02-24 18:11 ` bug#19479: Disclaimer is now on file at FSF Glenn Morris
2015-02-24 23:02 ` Kelly Dean
2015-02-25 21:09 ` Glenn Morris
2017-09-02 12:24 ` Eli Zaretskii
2015-02-25 4:41 ` Vibhav Pant
2015-02-25 5:32 ` Stephen J. Turnbull
2014-12-30 10:42 Emacs package manager vulnerable to replay attacks Kelly Dean
2014-12-30 11:45 ` Ivan Shmakov
[not found] ` <F8kXGdneKQWh6B82cOwdrCdBAdO1h3o9WXOqLmHuB8T@local>
[not found] ` <iHwGTo6KPGu52f1tOLq6Ek7KcZ7r2tufrT1z4GnPndF@local>
2015-02-24 8:47 ` Kelly Dean
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=EitH3yok1Itmynw5Ex1Vi3AuvkREurR1ccm1J5MQD4E@local \
--to=kelly@prtime.org \
--cc=19479@debbugs.gnu.org \
--cc=assign@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).