From: "Mike Gran" <spk121@yahoo.com>
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>,
me@tobias.gr, guix-devel <guix-devel@gnu.org>,
wingo@pobox.com, "Pjotr Prins" <pjotr2017@thebird.nl>
Subject: Re: FOSDEM 2019
Date: Tue, 21 Aug 2018 19:33:28 -0700 [thread overview]
Message-ID: <20180822023328.GA28373@joshua.dnsalias.com> (raw)
In-Reply-To: <6159e90a-b5d9-026e-24de-ea7d897f0ed0@gmail.com>
> I created a libreplanet page[2] to start writing possible talk ideas in
> case we get a devroom.
>
> We also need to write a proposal for our devroom application. The last
> year's proposal should be a good start. (attached) We should also talk
> with the Lua people in case we can share a devroom with them.
>
> Start sending ideas people!! This FOSDEM is going to be awesome!
Under the topic of encouraging newbies (and tangentially in the topic
of increasing diversity), I could do a talk about my experiments in
writing interactive fiction in Guile. I have had a goal of making
something as simple to use as the Twine interactive fiction engine. I
posted that on the wiki for now.
-Mike Gran
next prev parent reply other threads:[~2018-08-22 2:33 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 13:33 FOSDEM 2019 Manolis Ragkousis
2018-08-21 17:57 ` Ricardo Wurmus
2018-08-22 16:27 ` Andy Wingo
2018-08-22 2:33 ` Mike Gran [this message]
2018-08-23 0:08 ` Mike Gran
2018-08-24 9:23 ` FOSDEM 2019 (ACTION: please register or mail) Pjotr Prins
2018-08-24 9:29 ` alex sassmannshausen
2018-08-24 9:42 ` Ricardo Wurmus
2018-09-12 8:18 ` Efraim Flashner
2018-08-24 9:58 ` GNU Guix Days before FOSDEM Ludovic Courtès
2018-12-09 4:09 ` Chris Marusich
2019-01-05 8:44 ` Pjotr Prins
2019-01-05 21:43 ` Ludovic Courtès
2019-01-06 11:29 ` Pierre Neidhardt
2019-01-06 18:14 ` zimoun
2019-01-08 16:31 ` Ludovic Courtès
2019-01-08 17:14 ` Pierre Neidhardt
2018-08-24 10:10 ` FOSDEM 2019 (ACTION: please register or mail) Jonathan Brielmaier
2018-10-21 22:42 ` Leo Famulari
2018-10-22 3:34 ` Björn Höfling
2018-10-22 4:07 ` Leo Famulari
2018-08-24 12:23 ` FOSDEM 2019 Christopher Lemmer Webber
2018-08-29 21:08 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2019-02-03 21:34 Mikael Djurfeldt
2019-02-03 23:13 ` Arne Babenhauserheide
2019-02-04 5:21 ` Nala Ginrut
2019-02-05 21:25 ` Christopher Lemmer Webber
2019-02-06 13:46 ` Alex Sassmannshausen
2019-02-06 15:22 ` Amirouche Boubekki
2019-02-06 15:33 ` Amirouche Boubekki
2019-02-06 15:42 ` Alex Sassmannshausen
2019-02-06 21:03 ` Ricardo Wurmus
2019-02-06 22:09 ` Alex Sassmannshausen
2019-02-26 8:57 ` swedebugia
2019-02-06 20:40 ` Arne Babenhauserheide
2019-02-05 21:26 ` Christopher Lemmer Webber
2019-02-04 13:06 ` Amirouche Boubekki
2019-02-04 14:44 ` Ludovic Courtès
2019-02-04 18:01 ` Jan Nieuwenhuizen
2019-02-05 11:09 ` Amirouche Boubekki
2019-02-05 16:58 ` Ludovic Courtès
2019-02-06 0:31 ` Nala Ginrut
2019-02-06 12:59 ` Ludovic Courtès
2019-02-06 19:09 ` Amirouche Boubekki
2019-02-06 0:37 ` Matt Wette
2019-02-06 0:56 ` Nala Ginrut
2019-02-06 1:40 ` Amirouche Boubekki
2019-02-05 2:30 ` Matt Wette
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=20180822023328.GA28373@joshua.dnsalias.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=manolis837@gmail.com \
--cc=me@tobias.gr \
--cc=pjotr2017@thebird.nl \
--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).