unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: feedmail.el in the public domain?
Date: Sun, 16 Sep 2018 12:59:38 -0700	[thread overview]
Message-ID: <b4451040-8414-f070-02b0-df33036bed1b@cs.ucla.edu> (raw)
In-Reply-To: <83worlgwmw.fsf@gnu.org>

Eli Zaretskii wrote:

> why would we want or need to waste our energy on
> this?  This file has been in Emacs since about forever, and it never
> bothered us that it was in PD.  Why now?

Because it's come to our attention now, it's an easy fix, and getting licenses 
right is an important part of the GNU project's work.

>> If a file is in the public domain then there is no legal obstacle to placing 
>> whatever copyright license you like on a copy that you redistribute....
> 
> Maybe so (IANAL)

I'm not a lawyer either, but this is a well-understood part of copyright law 
there's no real controversy about it. We've used public-domain code in the GNU 
project before, with no problems.



  reply	other threads:[~2018-09-16 19:59 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 [this message]
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
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=b4451040-8414-f070-02b0-df33036bed1b@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@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).