From: Richard Stallman <rms@santafe.edu>
To: gnu-prog@gnu.org
Subject: What free manuals do we need?
Date: Fri, 02 Oct 1998 13:39:00 -0000 [thread overview]
Message-ID: <199810022037.QAA05425@delysid.gnu.org> (raw)
I would like to make a list of the free software packages that
don't have a full set of the free manuals that they ought to have.
This is to expand the list of neeed manuals in the GNU task list.
Typically, a package ought to have both a tutorial introduction and a
reference manual (though sometimes it is possible to make one manual
do both jobs). A good reference manual is not just a list of
functions and documentation for each one--it should be organized by
topics, and should discuss each topic as a whole, describing
individual functions as a part of that. (Contrast the GNU Emacs Lisp
Reference Manual with the collection of Emacs Lisp doc strings.)
If a package doesn't have all the free documentation it really calls
for have, or if it isn't good enough to publish, then we have a gap.
The goal here is to make a more complete list of these gaps.
This is not limited to GNU programs (programs released under the
auspices of the GNU project). We need documentation for all the
programs used in the GNU/Linux system (if users need to know about
them). So please make suggestions about important non-GNU free
packages also.
Thanks.
next reply other threads:[~1998-10-02 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-02 13:39 Richard Stallman [this message]
1998-12-04 18:05 ` Aubrey Jaffer
1998-12-05 14:40 ` Miguel de Icaza
1998-12-06 3:24 ` lynx-dev " David Woolley
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=199810022037.QAA05425@delysid.gnu.org \
--to=rms@santafe.edu \
--cc=gnu-prog@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox