From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guile-devel@gnu.org, guix-devel@gnu.org,
guile-user-bounces+amirouche=hypermove.net@gnu.org,
pjotr.public12@thebird.nl, alex@pompo.co, guile-user@gnu.org
Subject: FOSDEM 2017 what a success!!
Date: Mon, 6 Feb 2017 11:44:22 +0000 [thread overview]
Message-ID: <20170206114422.GA1983@mail.thebird.nl> (raw)
In-Reply-To: <20170203.145206.210212521671786630.post@thomasdanckaert.be>
Big thanks to the great speakers - personally I enjoyed every single
talk!! And then a hand to those who helped, especially Manolis who
supported getting the program lined up from the start!
Great stuff - and I know we made some new converts :). As a colleague
said: I thought the Ruby dev-room was great, but then the Guile
dev-room blew me away...
Pj.
next prev parent reply other threads:[~2017-02-06 11:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 22:47 FOSDEM 2017: GNU Guile & Guix call for talks! Ludovic Courtès
2016-11-07 16:58 ` Efraim Flashner
2016-11-08 2:23 ` Pjotr Prins
2016-12-18 15:26 ` FOSDEM 2017 Schedule is there! Pjotr Prins
2016-12-19 7:37 ` Alex Sassmannshausen
2017-01-03 14:46 ` FOSDEM 2017 Schedule is there! Change of schedule!:wq Pjotr Prins
2017-01-03 15:35 ` Amirouche Boubekki
2017-01-06 16:23 ` Pjotr Prins
2017-01-10 4:02 ` FOSDEM 2017 audio/video volunteers needed Pjotr Prins
2017-01-11 3:49 ` Pjotr Prins
2017-01-11 8:05 ` Ricardo Wurmus
2017-01-11 10:52 ` Amirouche Boubekki
2017-01-11 13:08 ` Catonano
2017-01-11 15:17 ` Pjotr Prins
2017-02-03 13:49 ` Catonano
2017-02-03 13:52 ` Thomas Danckaert
2017-02-06 11:44 ` Pjotr Prins [this message]
2017-02-06 12:59 ` FOSDEM 2017 what a success!! Ludovic Courtès
2017-02-07 21:32 ` Christopher Allan Webber
2017-02-03 14:00 ` FOSDEM 2017 audio/video volunteers needed Pjotr Prins
2017-02-04 12:42 ` Tobias Geerinckx-Rice
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170206114422.GA1983@mail.thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=alex@pompo.co \
--cc=guile-devel@gnu.org \
--cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.