all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: feedmail.el in the public domain?
Date: Mon, 17 Sep 2018 11:12:02 -0400	[thread overview]
Message-ID: <jwv4leo2me1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83pnxcgqcw.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 17 Sep 2018 17:17:51 +0300")

> Does this mean we cannot/shouldn't have _any_ PD files in Emacs?

No, IIUC it just means that their header notices shouldn't say public
domain because, while the original version may have been PD, the current
version is inevitably covered by the copyright of the FSF because of all
the changes we've accumulated on them since they were incorporated
into Emacs.

And for that same reason, we need to distribute them under a license we
find acceptable: it could be CC0 (to try and mimick PD as much as
possible), or GPLv3+ (like all our other files).

> Because feedmail.el isn't the only one, we have a few more.

Indeed,


        Stefan



  reply	other threads:[~2018-09-17 15:12 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
2018-09-17 15:12                 ` Stefan Monnier [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv4leo2me1.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.