From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org
Subject: Re: feedmail.el in the public domain?
Date: Mon, 17 Sep 2018 17:17:51 +0300 [thread overview]
Message-ID: <83pnxcgqcw.fsf@gnu.org> (raw)
In-Reply-To: <60200ba3-7f9c-3e65-3620-031b05ff3d4f@cs.ucla.edu> (message from Paul Eggert on Sun, 16 Sep 2018 21:12:57 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 16 Sep 2018 21:12:57 -0700
> Cc: eliz@gnu.org, emacs-devel@gnu.org
>
> Stefan Monnier wrote:
> > 1- Take a file from public domain.
> > 2- Make many small changes to it over the course of several years (all
> > after the Berne convention).
> > 3- Assume the sum of those changes is significantly higher than the
> > "20-lines triviality threshold".
> > 4- Is the result still public domain?
>
> No, the result is public domain only if the contributors deliberately place it
> into the public domain, in a process known as dedication. And that process is
> legally controversial for works created after 1976 in the US - though I'm
> perhaps giving you more detail than you want to know, Creative Commons
> recommends against relying on such dedications
> <https://creativecommons.org/licenses/publicdomain/>.
Does this mean we cannot/shouldn't have _any_ PD files in Emacs?
Because feedmail.el isn't the only one, we have a few more.
next prev parent reply other threads:[~2018-09-17 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:44 feedmail.el in the public domain? Stefan Monnier
2018-09-14 18:36 ` Eli Zaretskii
2018-09-15 22:13 ` Paul Eggert
2018-09-16 17:49 ` Eli Zaretskii
2018-09-16 19:59 ` Paul Eggert
2018-09-17 2:25 ` Richard Stallman
2018-09-17 3:00 ` Stefan Monnier
2018-09-17 4:12 ` Paul Eggert
2018-09-17 14:17 ` Eli Zaretskii [this message]
2018-09-17 15:12 ` Stefan Monnier
2018-09-17 22:53 ` Richard Stallman
2018-09-18 2:53 ` Stefan Monnier
2018-09-18 3:12 ` Glenn Morris
2018-09-17 22:52 ` Richard Stallman
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=83pnxcgqcw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.
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).