unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>,
	"Ludovic Courtès" <ludo@gnu.org>,
	me@tobias.gr, wingo@pobox.com, guix-devel <guix-devel@gnu.org>,
	"Pjotr Prins" <pjotr2017@thebird.nl>
Subject: Re: FOSDEM 2019 (ACTION: please register or mail)
Date: Fri, 24 Aug 2018 11:23:43 +0200	[thread overview]
Message-ID: <20180824092343.grrrmtmrucbl7b7d@thebird.nl> (raw)
In-Reply-To: <6159e90a-b5d9-026e-24de-ea7d897f0ed0@gmail.com>

Who wants to come to a separate 2 day GNU Guix event?

That is the Thursday Jan 31st and/or Friday Feb 1st right before
FOSDEM. I.e., 4 days of hacker nirvana.

FOSDEM is really great. Look at last year's schedule for Saturday

  https://archive.fosdem.org/2018/schedule/day/saturday/

Last year we had a 1 day event with about 25 people before FOSDEM.
See

  https://libreplanet.org/wiki/Group:Guix/FOSDEM2018

If you intend to come and/or want to speak please add your name and
proposed title to the new page at

  https://libreplanet.org/wiki/Group:Guix/FOSDEM2018

Alternatively, reply here or mail me privately so we can keep a tally.

Please do so because we need to find a venue again on a first come
first go basis if we run out of seats.

Pj.

On Tue, Aug 21, 2018 at 04:33:53PM +0300, Manolis Ragkousis wrote:
> Hello everyone,
> 
> It's that time of the year again we need to start organizing about
> FOSDEM. We have a deadline for the 20th of September[1] to apply for a
> devroom. We also need to start looking for a place for this year's
> fringe event!

  parent reply	other threads:[~2018-08-24  9:23 UTC|newest]

Thread overview: 25+ 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
2018-08-23  0:08 ` Mike Gran
2018-08-24  9:23 ` Pjotr Prins [this message]
2018-08-24  9:29   ` FOSDEM 2019 (ACTION: please register or mail) 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-12-06  8:52     ` Pjotr Prins
2018-10-21 22:42   ` Leo Famulari
2018-10-22  3:34     ` Björn Höfling
2018-10-22  4:07       ` Leo Famulari
2018-11-01  9:14         ` Pjotr Prins
2018-08-24 12:23 ` FOSDEM 2019 Christopher Lemmer Webber
2018-08-29 21:08   ` Ludovic Courtès

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180824092343.grrrmtmrucbl7b7d@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).