From: Manolis Ragkousis <manolis837@gmail.com>
To: Guile Devel <guile-devel@gnu.org>, guix-devel <guix-devel@gnu.org>
Cc: "Pjotr Prins" <pjotr2016@thebird.nl>,
"Ludovic Courtès" <ludo@gnu.org>,
"Tobias Geerinckx-Rice" <me@tobias.gr>
Subject: FOSDEM 2018 Guile devroom
Date: Thu, 5 Oct 2017 23:34:37 +0300 [thread overview]
Message-ID: <3b45845d-8c44-bb91-61e6-0ef216e214d5@gmail.com> (raw)
Hello Guile, Hello Guix,
Unfortunately I have bad news. Our proposal for a devroom at FOSDEM 2018
has not been accepted. But I think we can still make the best out of a
bad situation. That's why I want to encourage people to submit talks in
other devrooms/tracks. Ludo posted a list some time ago[1] on possible
options. The confirmed devrooms for 2018 will be announced soon. [2]
We also have the option of organizing a fringe event or a hackathon in
the Friday before, if we find a place and there is interest. The ones
local to Brussels can help with finding a place. Alex any ideas?
Alternatively we can host something later in the year somewhere in
another conference. WDYT?
People this is a good time for suggestions and ideas :). Please do say
what you think and how we could make the best out of this. It will help.
Thank you
Manolis
[1] https://lists.gnu.org/archive/html/guix-devel/2015-11/msg00695.html
[2] https://fosdem.org/2018/schedule/
next reply other threads:[~2017-10-05 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 20:34 Manolis Ragkousis [this message]
2017-10-06 19:15 ` FOSDEM 2018 Guile devroom Ricardo Wurmus
2017-10-18 15:15 ` Thomas Danckaert
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=3b45845d-8c44-bb91-61e6-0ef216e214d5@gmail.com \
--to=manolis837@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=pjotr2016@thebird.nl \
/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).