all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Licensing of NEWS files?
Date: Thu, 15 Oct 2015 18:34:58 +0200	[thread overview]
Message-ID: <87k2qoum31.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <878u74drzq.fsf@mbork.pl> (Marcin Borkowski's message of "Thu, 15 Oct 2015 18:19:21 +0200")

Marcin Borkowski <mbork@mbork.pl> writes:

> On 2015-10-15, at 18:13, Dmitry Gutov <dgutov@yandex.ru> wrote:
>
>> On 10/15/2015 06:58 PM, David Kastrup wrote:
>>
>> I don't disagree, but:
>>
>>> quoting from the NEWS
>>> file in some article they are doing about a new release.
>>
>> Isn't is Fair Use?
>
> Isn't Fair Use limited to US law?

Putting that aside: do we want it to be a problem to put up a reasonably
_complete_ NEWS file without appropriate license notices, modification
notices (the rest of Emacs is missing) and copy of GPL license?

Similarly to how we declare code examples in our Texinfo manuals as
"Public Domain" free for any use, I think that it would make sense to
similarly do so with the NEWS files.  The rationale most likely might be
that people cannot just rip them out without notice when distributing
Emacs, but the GPL pretty much allows that anyway when you leave an
appropriate notice of having done that.

Richard?  Any word on this?

-- 
David Kastrup



  parent reply	other threads:[~2015-10-15 16:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 15:58 Licensing of NEWS files? David Kastrup
2015-10-15 16:13 ` Dmitry Gutov
2015-10-15 16:19   ` Marcin Borkowski
2015-10-15 16:32     ` Dmitry Gutov
2015-10-16  1:16       ` Stephen J. Turnbull
2015-10-15 16:34     ` David Kastrup [this message]
2015-10-15 16:31 ` Eli Zaretskii
2015-10-15 16:43   ` David Kastrup
2015-10-15 22:05 ` Paul Eggert
2015-10-15 23:00   ` Xue Fuqiao
2016-02-01  0:56     ` Paul Eggert
2016-02-01  3:16       ` Xue Fuqiao
2015-10-16  8:58   ` Eli Zaretskii

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=87k2qoum31.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=mbork@mbork.pl \
    /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.