unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: belanger@truman.edu
Cc: belanger@truman.edu, emacs-devel@gnu.org
Subject: Re: Manual licenses
Date: Sun, 15 Apr 2007 15:01:09 -0400	[thread overview]
Message-ID: <E1Hd9yH-0006ag-DO@fencepost.gnu.org> (raw)
In-Reply-To: <873b32jlkx.fsf@truman.edu> (message from Jay Belanger on Sat, 14 Apr 2007 23:41:34 -0500)

Each manual should contain a copy of the GFDL, because we want them
to be separately distributable.

Can people please work on that, and the other points below?

But not this one:

      But now I wonder if the
    GPL should be part of the individual manuals? 

Including the GPL in any given manual is entirely optional.

    A few other things I noticed, which may or may not be worth noting.
    Several manuals have old dates on the cover page.  (Calc does, but I'm
    going to remove that.)
    The ERC manual is under the GFDL, but doesn't give a pointer to
    a copy if it in the copyright notice.
    A couple of manuals (dired-x, the faq) aren't under the GFDL.
    A couple of manuals (flymake, newsticker) don't have an "@insertcopying"
    line in the title page, so the copyright doesn't appear when they're 
    processed.  (I'd say the same about widget, but that doesn't have a
    title page.)
    A couple of manuals (pgg, url) have copyright notices which mention
    that the GFDL is included as a section, but it isn't.

Thank you for noticing these points.  We need to fix them all
before the release.

  reply	other threads:[~2007-04-15 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15  4:41 Manual licenses Jay Belanger
2007-04-15 19:01 ` Richard Stallman [this message]
2007-04-15 21:24   ` Chong Yidong
2007-04-16 15:37     ` 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=E1Hd9yH-0006ag-DO@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=belanger@truman.edu \
    --cc=emacs-devel@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).