unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: benjaminsutter@aurora-schools.org
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Guix-devel <guix-devel@gnu.org>, Pjotr Prins <pjotr2017@thebird.nl>
Subject: Re: Let’s meet before FOSDEM!
Date: Wed, 8 Nov 2017 07:20:36 -0500	[thread overview]
Message-ID: <00EF2A1D-6850-41E0-8555-47C6B1DA646C@aurora-schools.org> (raw)
In-Reply-To: <20171108102308.GE1815@macbook41>

It’s times like this when I wish I were older. 

> On Nov 8, 2017, at 5:23 AM, Efraim Flashner <efraim@flashner.co.il> wrote:
> 
>> On Tue, Nov 07, 2017 at 02:39:53PM +0100, Ludovic Courtès wrote:
>> Hello Guix!
>> 
>> Since we didn’t get a devroom this time in spite of the efforts of
>> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
>> before FOSDEM (Feb. 2nd, in Brussels)?
>> 
>> We could meet for the whole day, in a place that remains to be defined,
>> to discuss about all things Guix{,SD}.  The event could be a mixture of
>> short talks on specific topics, discussions on technical and less
>> technical topics (multiple bootloader support & GuixSD on ARM, making
>> ‘guix pull’ great again, Cuirass, reaching out to more
>> users/contributors, Guix & HPC, improving our infrastructure and
>> organization, etc.), and possibly hacking sessions.
>> 
>> Who would be willing to join?  (You can reply privately if you prefer.)
>> 
>> Based on the show of hands, we’ll arrange for a venue of the appropriate
>> size.
>> 
>> Thanks!
>> 
>> Ludo’.
> 
> I should be able to make it again this year. Assuming I'm taking the
> same flight as last time I'll be in Brussels by about 5am. I'm not
> suggesting that we start that early, but depending on what everyone else
> is doing we could aim to have the talks/presentations when we have the
> most number of people and then have time before and after for hacking.
> 
> 
> -- 
> Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
> GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted

  reply	other threads:[~2017-11-08 12:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 13:39 Let’s meet before FOSDEM! Ludovic Courtès
2017-11-07 14:14 ` ng0
2017-11-07 14:19 ` julien lepiller
2017-11-07 14:46 ` myglc2
2017-11-07 22:50   ` Ludovic Courtès
2017-11-07 17:00 ` Pjotr Prins
2017-11-07 18:09 ` Jan Nieuwenhuizen
2017-11-07 18:23 ` Ricardo Wurmus
2017-11-07 19:06 ` Roel Janssen
2017-11-07 19:18   ` Marius Bakke
2017-11-07 21:49 ` Pjotr Prins
2017-11-08  8:49   ` Ludovic Courtès
2018-01-06 17:16   ` Catonano
2017-11-08  7:57 ` Christopher Baines
2017-11-08 10:23 ` Efraim Flashner
2017-11-08 12:20   ` benjaminsutter [this message]
2017-11-08 13:57   ` Ludovic Courtès
2017-11-08 22:51     ` ng0
2017-11-09 15:45     ` Pjotr Prins
2018-01-20 14:16 ` Danny Milosavljevic

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=00EF2A1D-6850-41E0-8555-47C6B1DA646C@aurora-schools.org \
    --to=benjaminsutter@aurora-schools.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=pjotr2017@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.
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).