From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: who wrote the manual?
Date: Mon, 11 Oct 2010 23:01:25 +0200 [thread overview]
Message-ID: <m339sce95m.fsf@unquote.localdomain> (raw)
In-Reply-To: <878w24h4e0.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 11 Oct 2010 22:16:07 +0200")
On Mon 11 Oct 2010 22:16, ludo@gnu.org (Ludovic Courtès) writes:
> And kudos to Neil, I think we owe him a great debt!
Indeed, and it's ongoing :)
Here is what I put into preface.texi. Feel free to criticize or, better
yet, fix directly :)
Like Guile itself, the Guile reference manual is a living entity, cared
for by many people over a long period of time. As such, it is hard to
identify individuals of whom to say ``yes, this person, she wrote the
manual.''
Still, among the many contributions, some caretakers stand out. First
among them is Neil Jerram, who has been working on this document for ten
years now. Neil's attention both to detail and to the big picture have
made a real difference in the understanding of a generation of Guile
hackers.
Next we should note Marius Vollmer's effect on this document. Marius
maintained Guile during a period in which Guile's API was
clarified---put to the fire, so to speak---and he had the good sense to
effect the same change on the manual.
Martin Grabmueller made substantial contributions throughout the manual
in preparation for the Guile 1.6 release, including filling out a lot of
the documentation of Scheme data types, control mechanisms and
procedures. In addition, he wrote the documentation for Guile's SRFI
modules and modules associated with the Guile REPL.
Ludovic Courtès and Andy Wingo, the Guile maintainers at the time of
this writing (late 2010), have also made their dent in the manual,
writing documentation for new modules and subsystems in Guile 2.0. They
are also responsible for ensuring that the existing text retains its
relevance as Guile evolves. @xref{Reporting Bugs}, for more information
on reporting problems in this manual.
The content for the first versions of this manual incorporated and was
inspired by documents from Aubrey Jaffer, author of the SCM system on
which Guile was based, and from Thomas Lord, Guile's first maintainer.
Although most of this text has been rewritten, all of it was important,
and some of the structure remains.
The first versions of the first versions of Guile were written and
edited largely by Mark Galassi and Jim Blandy. In particular, Jim wrote
the original tutorial on Guile's data representation and the C API for
accessing Guile objects.
Significant portions were also contributed by Thien-Thi Nguyen, Kevin
Ryde, Mikael Djurfeldt, Christian Lynbech, Julian Graham, Gary Houston,
Tim Pierce, and a few dozen more. You, reader, are most welcome to join
their esteemed ranks. Visit Guile's web site at
@uref{http://www.gnu.org/software/guile/} to find out how to get
involved.
--
http://wingolog.org/
next prev parent reply other threads:[~2010-10-11 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 19:39 who wrote the manual? Andy Wingo
2010-10-11 20:16 ` Ludovic Courtès
2010-10-11 21:01 ` Andy Wingo [this message]
2010-10-12 9:45 ` Ludovic Courtès
2010-10-30 15:42 ` Neil Jerram
2010-10-11 20:27 ` Mike Gran
2010-10-11 21:30 ` Neil Jerram
2010-10-11 22:06 ` Andy Wingo
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=m339sce95m.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).