unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: syncase merged to master
Date: Tue, 21 Apr 2009 00:28:41 +0100	[thread overview]
Message-ID: <87prf6c3bq.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3tz4jnhqv.fsf@pobox.com> (Andy Wingo's message of "Mon\, 20 Apr 2009 23\:21\:44 +0200")

Andy Wingo <wingo@pobox.com> writes:

> While it's true I have had a bit of time lately to poke at things,
> you've been looking at R6RS syntactic integration, Ludovic has been on
> the R6RS library problem (in addition to doing great work on the GC),
> Neil does great work with the manual and on subtle bugs, Mike will bring
> us something nice with Unicode support... and then besides the past that
> we are building on, there are those waiting in the wings to hack Elisp
> and threads and persistent data structures and better Emacs integration
> and on and on and on.

And Julian did major work on SRFI-18 threads!

> It's a lovely time to hack Guile :-)

I'm pleased that you think so.  Tool-wise I think Git has been a
massive help, so major kudos to Ludovic for that.  Otherwise, I think
the main things Guile needs to encourage development are senses on one
hand of stability, and on the other of a clear release plan; so I have
tried to do what I can to help with that.

>> some kind of marketing blitz is in order. Can the FSF / GNU project
>> help with publicity in any way?
>
> I think you're totally right. FSF/GNU can help, but we need to have the
> vision -- strongly articulated, so as to cut through cobwebs of the
> past.

From a GNU project point of view, I think the vision has been clear
for a long time: an easily embeddable extension language library,
allowing GNU applications to be extended in several different
languages.  We're closer now to that than we've ever been before, I
think.

> But, and this is my perception, I think we have to be ready for the push
> when it comes. Documentation is /really/ important in that regard. As
> far as the new developments are concerned, we need to have a depth of
> documentation in place -- and already some of the stuff I wrote a few
> months ago needs updating already. 

Yes - except that I wouldn't want in-depth documentation to delay the
2.0 release a lot!  I'd rather get all the fantastic new stuff out
there.

> So I think we need to have our ducks in a row before we really start
> pushing FSF/GNU.

But what are the ducks?  Ideally I think they'd be example
applications, with beautiful and useful scripting code extending
them.  But I'm not sure how we can come up with such examples very
quickly.

Regards,
        Neil





  parent reply	other threads:[~2009-04-20 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 20:35 syncase merged to master Andy Wingo
2009-04-20 20:56 ` Julian Graham
2009-04-20 21:21   ` Andy Wingo
2009-04-20 21:30     ` Julian Graham
2009-04-20 23:28     ` Neil Jerram [this message]
2009-04-20 23:03 ` Neil Jerram
2009-04-28 20:10 ` Ludovic Courtès

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=87prf6c3bq.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).