all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: License questions for Emacs doc files
Date: Fri, 13 Jun 2008 10:21:58 -0400	[thread overview]
Message-ID: <jwv3anh4dv5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <jriqwermjj.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 13 Jun 2008 00:22:56 -0400")

> i) doc/emacs/gnu.texi is the GNU Manifesto, which is an invariant
> section of the Emacs manual. Yet at the start of gnu.texi, there is a
> standard GFDL license notice, which says there are no invariant
> sections! This is weird, isn't it? Shouldn't gnu.texi just say "see
> file emacs.texi for copying conditions", or perhaps have a verbatim
> license like etc/GNU?

Look odd, indeed.  Could someone figure out what's the right thing to
do here.

> ii) doc/emac/misc/mh-e.texi is dual licensed under GPLv3+ and GFDL 1.2
> (with no invariants and no cover text). Is that OK?

That's perfectly fine by me.

> iii) Should all the doc/emac/misc/*.texi files be standardized in
> terms of their Invariant and Cover text sections? Most of them have no
> Invariant, front cover "a GNU Manual", and back cover "You have the
> freedom to copy and modify...". Some of them are missing the cover
> texts - should these be added?

Some consistency would be good, yes.  But if the manual (and the
corresponding package) is also distributed separately, they may prefer
a slightly different arrangement and it's good to stick to it in
that case.


        Stefan




  reply	other threads:[~2008-06-13 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13  4:22 License questions for Emacs doc files Glenn Morris
2008-06-13 14:21 ` Stefan Monnier [this message]
2008-06-13 22:48 ` Richard M 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=jwv3anh4dv5.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.