unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org,  guix-europe@gnu.org,
	Julien Lepiller <julien@lepiller.eu>
Subject: Re: Booth at FOSDEM (Brussels), 4-5 Feb 2023?
Date: Thu, 20 Oct 2022 15:09:07 +0200	[thread overview]
Message-ID: <87ilkefxqk.fsf@gnu.org> (raw)
In-Reply-To: <86czapxe2u.fsf@gmail.com> (zimoun's message of "Tue, 18 Oct 2022 18:59:37 +0200")

Hello!

zimoun <zimon.toutoune@gmail.com> skribis:

> As the winter, FOSDEM 2023 is coming…
>
>     https://fosdem.org/2023
>
>
> Three questions:
>
>  1. do we run for a booth?
>  2. who is in?
>  3. who is volunteer to make that happens?

Having a booth can be a way to have informal conversations with folks
who are curious about Guix or haven’t heard about it before.

IIRC, Julien was responsible for a booth at FOSDEM for Linux From
Scratch some years ago, so maybe they can share their experience?

For this to be viable, I suppose there needs to be about at the very
least 4 people (that’d still be half a day each!).  However,
pre-pandemic, there would usually be somewhere between 20 and 40 Guix
people joining, so I’m sure 10 of us or so could take care of the booth
for a couple of hours.

Thanks,
Ludo’.


  reply	other threads:[~2022-10-20 15:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 16:59 Booth at FOSDEM (Brussels), 4-5 Feb 2023? zimoun
2022-10-20 13:09 ` Ludovic Courtès [this message]
2022-10-20 17:36   ` zimoun
2022-10-20 22:15     ` Julien Lepiller
2022-10-20 14:44 ` Jonathan Brielmaier
2022-10-20 16:18   ` Julien Lepiller
2022-10-21 16:44     ` Joshua Branson
2022-10-22  3:09       ` John Kehayias
2022-10-22  8:02 ` Josselin Poiret
2022-11-15 15:18 ` zimoun
2022-12-09 17:48   ` zimoun

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=87ilkefxqk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-europe@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=zimon.toutoune@gmail.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).