unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, wip-manual-2, updated. release_1-9-9-85-g0a864be
Date: Mon, 12 Apr 2010 01:15:16 +0100	[thread overview]
Message-ID: <87iq7xpluz.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87tyrhbn13.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 12 Apr 2010 01:13:44 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Hi Neil,

Hi Ludo!

> "Neil Jerram" <neil@ossau.uklinux.net> writes:
>
>>     Improvements to Introduction chapter
>>     
>>     * doc/ref/intro.texi (Introduction): Change "some" to "the".
>>       (Guile and Scheme): "multithreading" -> "multithreaded".
>>       (Combining with C): Mention "libguile" as library name.
>>       (Guile and the GNU Project): New text.
>>       (Interactive Programming): New text.
>>       (Supporting Multiple Languages): New text, reflecting currently
>>       supported languages.
>>       (Obtaining and Installing Guile): Use @var for version placeholder.
>>       Remove mention of separate tutorial.
>
> FWIW I really like “Guile and the GNU Project” and “Interactive
> Programming”.  I think they concisely convey the GNU vision to provide
> software that’s not only released under a free software license (the
> legal aspect of freedom) but is also liberating and empowering (the
> technical aspect).

Hey, thanks!  Your feedback is very much appreciated.

I'm not sure if I raised it on the list, but for a while I was worried
about the manual being so big, and I wasn't sure about how to form its
contents into a coherent narrative - or about the extent to which that
matters.

My eventual conclusion from that was that what's really important is to
have a good Introduction chapter.  If the Introduction does a good
enough job of laying out the Big Picture, I think that effectively
_creates_ the narrative for the whole manual, and the job for the rest
of the manual is simplified to making sure that it is complete and
technically correct (and has pleasant smaller-scale structure, of
course).

Hence, that's what I've been focussing on recently in the wip-manual-2
branch.  I'm sure I'm still not getting everything perfect, though, so
please do keep an occasional eye on that branch, and let me know if you
have any developing concerns.  I will merge from master regularly so as
not to miss stuff that's added there, and to avoid building up a
conflict backlog.  Then, hopefully, at a point in the not too distant
future, the manual in wip-manual-2 will be ready for pulling back into
master, and publishing.

<tongue slightly in cheek>

The trouble is, though, when the ground keeps shifting under one's
feet.  Now that multiple language support is really starting to take
off, last night I was thinking that the first sentence "Guile is an
implementation of the Scheme programming language." is probably not the
right first sentence any more...

</>

> Thanks,
> Ludo’ (looking forward to having this nice manual on his bookshelf.  :-))

Me too, and that reminds me that I need to get in touch with Brian to
discuss a new realistic schedule.

Thanks again,

     Neil




  reply	other threads:[~2010-04-12  0:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1O0l18-0003HJ-PM@vcs-noshell.in.savannah.gnu.org>
2010-04-11 23:13 ` [Guile-commits] GNU Guile branch, wip-manual-2, updated. release_1-9-9-85-g0a864be Ludovic Courtès
2010-04-12  0:15   ` Neil Jerram [this message]
2010-04-12  8:23     ` Ludovic Courtès
2010-04-15 19:40     ` Andy Wingo
2010-04-16 21:18       ` Neil Jerram

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=87iq7xpluz.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).