From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Manolis Ragkousis" <manolis837@gmail.com>
Subject: GNU Guix/Guile day just before FOSDEM 2018
Date: Sat, 30 Dec 2017 17:58:28 +0000 [thread overview]
Message-ID: <CAL7_Mo9-KH_07ghzapT=soBNAXU+Terj0piNY0Zbud-LedjaxQ@mail.gmail.com> (raw)
Hello,
Pjort, Ludo and Manolis are organizing a Guix/Guile day just before FOSDEM
2018 at the very beginning of February the 02/02/2018 just before FOSDEM.
They mentioned http://icab.be/b_and_b_programme.php for accommodation which
is the place where the Guix event is happening.
There is information about the event at
https://libreplanet.org/wiki/Group:Guix/FOSDEM2018
Sadly there is no talks about Guile itself, does anyone want to produce a
talk about Guile? Maybe, I can do it myself, but I am not sure I am
going... Anyway some more guilers must be there!
Or what do you think of this: We make a list of all the awesome stuff that
happened in 2017 and make a few slides about it!
Here is my list:
- Guile ffi helper by Matt Wette: is really a step in the right direction
- Haunt by David Thomson: his static blog generator got more users,
- GNU Foliot by David Pirotte: is the first GNU app written in Guile using
GTK3
- Guile-CV by David Pirotte: a tool to analyze images using somekind of
aglgorithms
- Guile JS backend: Ian Price made the JavaScript compiler backend (and it
works on my machine :)
- Guile 2.2.3 was released, what's new?
Any ideas what else to do a 2017 Guile recap?
next reply other threads:[~2017-12-30 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 17:58 Amirouche Boubekki [this message]
2017-12-30 18:23 ` GNU Guix/Guile day just before FOSDEM 2018 Amirouche Boubekki
2017-12-31 12:58 ` David Pirotte
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='CAL7_Mo9-KH_07ghzapT=soBNAXU+Terj0piNY0Zbud-LedjaxQ@mail.gmail.com' \
--to=amirouche.boubekki@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=manolis837@gmail.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).