all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Pittman <slippycheeze@google.com>
To: emacs-devel@gnu.org, licensing@fsf.org
Subject: Licensing for source code contained in Emacs manuals
Date: Mon, 12 Nov 2018 13:24:06 -0500	[thread overview]
Message-ID: <CAC45yQs5C9=Zonsu03on=9C5ne2vmgRtEu33WV1=ascz_WQKwg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]

G'day.  The question of licensing for code derived from a sample contained
in the flymake manual came up, and I wanted to follow up to ensure
appropriate compliance with the license terms.

This is copied to the FSF licensing team, as I strongly suspect they are
appropriate to correct any misapprehensions that I have about the licenses,
their application, or the other questions at hand.

The source in question is here:

https://www.gnu.org/software/emacs/manual/html_node/flymake/An-annotated-example-backend.html

That manual is licensed under the GFDL, appropriately.  The code, I think,
is sufficiently large and involved that it can't be reused arbitrarily as
"fair use", or any other general licensing exception.

Now, I'm pretty certain the intent was that this code could be reused for
the purpose of developing flymake backends, and it is a copy of code that
was under the GPL prior to inclusion – although it is not directly
including that code, and has extended the commentary.

The manual in question, the GFDL itself, and the GNU/FSF FAQ about
licensing provide no exceptions for the case of relicensing the sample code
that I am able to find.

As far as I can tell, this means that anything derived from that sample
code would also be covered by the GFDL, including the provisions for
invariant sections, which do not really make sense in the context of "I
wrote a flymake backend."


On checking, none of the other Emacs manuals seem to have any documented
exception to the GFDL for sample code either; the Emacs manual mentions the
GPL, but only in the context of Emacs itself, noting the manual is undir
the GFDL.


Would it be appropriate to extend the documentation to explicitly permit
reuse of the sample code in the Emacs flymake manual, or all Emacs manuals,
under the same license as Emacs itself?  That is, sample code could be used
under the GFDL *or* the GPLv3 (at this time).


If I have missed something, and I am definitely not an IP licensing lawyer,
please let me know, and I'll be very happy to be corrected. :)

Thanks for your time.

[-- Attachment #2: Type: text/html, Size: 2631 bytes --]

             reply	other threads:[~2018-11-12 18:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 18:24 Daniel Pittman [this message]
2018-11-12 20:01 ` Licensing for source code contained in Emacs manuals Paul Eggert
2018-11-12 21:35   ` Daniel Pittman
2018-11-13 18:31     ` Glenn Morris
2018-11-14 23:13       ` Richard Stallman
2018-11-19 14:18         ` Daniel Pittman
2018-11-20  0:49           ` Richard Stallman
2018-12-24  2:26 ` Richard Stallman
2019-01-07 21:06   ` Daniel Pittman
2019-01-08  1:06     ` Paul Eggert
2019-01-08 18:57     ` Richard Stallman
2019-06-30  5:05     ` FIXME: When the reader is called in the minibuffer Spenser Truex
2019-06-30 13:50       ` Stefan Monnier

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='CAC45yQs5C9=Zonsu03on=9C5ne2vmgRtEu33WV1=ascz_WQKwg@mail.gmail.com' \
    --to=slippycheeze@google.com \
    --cc=emacs-devel@gnu.org \
    --cc=licensing@fsf.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.