From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: guile 2012
Date: Sat, 07 Jan 2012 03:34:39 +0100 [thread overview]
Message-ID: <87ty48gs00.fsf@pobox.com> (raw)
Greetings, Guilers!
I hope this message finds all of you well: you, and yours, and all the
beings in your lives. It was really a pleasure to hack with yall last
year.
It might be useful to reflect, at the start of this new year. We should
look back, first. In 2011, we released Guile 2.0: a huge effort, and a
great improvement over 1.8. More than that, I really dig the energy
around Guile now, that we are many active people, caring about where
Scheme and Guile and GNU are going.
A few years ago, Guile was going through some tough times: declining
user base, performance problems, and lack of modern features. But in
the last year or three we have really pulled together and delivered a
great Scheme system. So many people have applied their talent and time
to Guile that it's really impossible to make a proper list, so let us
instead raise our symbolic cup to us all. Thanks, us!
We should also take this moment to look forward, to our challenges and
opportunities. I'll give my impressions, but feel very free to chime in
with your thoughts.
I think 2012 will be a good year for Guile. We'll be solidifying the
2.0 series, even as we start producing the first pre-release or two of
2.2. I would really love to get a register VM and a first stab at
native compilation out this year. We'll see.
If I could vote for one thing to focus on in 2012, for the broader Guile
community, I'd pick two things ;-) I'd pick Guile in Emacs, first of
all. We have the hack power, the time is right, and we just need to
focus on the task. By the end of the year we could have a credible,
attractive offering.
The other thing I'd like for us to focus on, in a stable-2.0 sense,
would be the guildhall. There's some hacking that needs to be done
there, but I'm hoping to get out a first workable prototype within a
month or two, then let the meta-maintenance be driven by patches, while
the repository of modules in the guildhall has time to grow and grow.
Help here is much appreciated! :-)
As far as challenges go, I think that we can make some projections based
on the last few months of 2011. Specifically, I think that we will need
to focus on maintain a positive, constructive environment, both for old
and new Guilers. Some of this focus will have to be directed in the
form of patches to the documentation. Some of it will patch code, to
make Guile more approachable and coherent. And some of it, a very
important part of it, will be spent in consciously maintaining a good
environment on the mailing lists, and in the chat rooms. There will be
lots of new folks, with lots of questions. We're going to grow this
year, and we're going to have to teach the new people about our
community, and about our software. Let's all have patience and
positivity. With luck, next year some of these newbies will be experts.
Again, speaking personally, 2011 has really been great. We have done
some great things, and we should be proud of them. It sounds terribly
cheesy, but hey: let's go on and make 2012 the best year Guile has had
yet :-)
Happy hacking,
Andy
--
http://wingolog.org/
next reply other threads:[~2012-01-07 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 2:34 Andy Wingo [this message]
2012-01-12 22:50 ` guile 2012 Ludovic Courtès
2012-01-13 22:21 ` Dirk-Jan C. Binnema
2012-01-17 22:37 ` Mike Gran
2012-01-18 0:27 ` Aleix Conchillo Flaqué
2012-01-19 12:27 ` Nala Ginrut
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=87ty48gs00.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@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).