From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: doc license section
Date: Wed, 21 Jan 2004 22:56:41 +0100 [thread overview]
Message-ID: <87y8s19d9i.fsf@zagadka.ping.de> (raw)
In-Reply-To: <873cai3vg1.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 15 Jan 2004 10:30:06 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Might be worth thinking about GFDL for the manuals, while on the
> subject of licenses.
Yes, indeed. Maintain.texi says: "Manuals should use the GNU Free
Documentation License".
This would be the copyright notice, I'd say:
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software
Foundation; with the no Invariant Sections, with the Front-Cover
Texts being ``A GNU Manual,'' and with the Back-Cover Texts as in
(a) below. A copy of the license is included in the section
entitled "GNU Free Documentation License".
(a) The FSF's Back-Cover Text is: ``You are free to copy and modify
this GNU Manual.''
I'm also unhappy about the list of authors on the front cover. It is
quite long already and not even complete. What can we do about this?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-21 21:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 0:30 doc license section Kevin Ryde
2004-01-15 2:12 ` Stephen Compall
2004-01-20 0:46 ` Kevin Ryde
2004-01-15 21:37 ` Neil Jerram
2004-01-21 21:56 ` Marius Vollmer [this message]
2004-01-21 22:04 ` Carl Witty
2004-01-21 22:58 ` Kevin Ryde
2004-01-21 23:07 ` Marius Vollmer
2004-01-21 23:22 ` Marius Vollmer
2004-01-22 18:08 ` Pierre Bernatchez
2004-01-22 18:22 ` Paul Jarc
2004-01-22 23:18 ` Marius Vollmer
2004-01-21 22:13 ` Kevin Ryde
2004-01-21 22:40 ` Neil Jerram
2004-02-18 20:34 ` Marius Vollmer
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y8s19d9i.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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.
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).