From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Organising Guix Days
Date: Mon, 20 Dec 2021 18:51:26 +0100 [thread overview]
Message-ID: <87tuf3f9lt.fsf@gnu.org> (raw)
In-Reply-To: <20211211023721.7e7c6099@tachikoma.lepiller.eu> (Julien Lepiller's message of "Sat, 11 Dec 2021 02:37:21 +0100")
Hello!
Julien Lepiller <julien@lepiller.eu> skribis:
> I think it's time to start organising the Guix Days, traditionally held
> around Fosdem.
>
> During our guix-europe assembly, we discussed some options and everyone
> agreed they wanted a two-day event, online just as Fosdem. I attached a
> proposed blog post that we should put on the website as soon as we
> agree on the first details.
>
> I suggest that we have these days right after Fosdem, Monday and
> Tuesday. This should give us just a few more days to prepare, as I think
> we're starting pretty late already. If you prefer to have them before
> fosdem, I can change the blog post of course.
No strong opinion, but I wonder if some might prefer to have it a few
days later, so they can give their eyes and ears some rest. :-)
> As for how it'll be organised. I propose to do something similar to
> what we need in November 2020. I'd love to get some talks from people
> outside the usual maintainers and commiters, to have an overview of the
> diversity of people and usage around Guix.
>
> Last year, we asked speakers to prepare a video in advance, and they
> would only have an extended Q&A/discussion session. I think this year
> we should have the same process, but ask for a short (3-5 minutes) talk
> at the start of the session to refresh our minds on the main points of
> the presentation before discussions start.
[…]
The whole program sounds great to me!
> Also, we need to secure a BBB instance :)
I think we can still use the same one as last year (zimoun?). If that
doesn’t work, there’s a couple of options, such as Inria’s instance.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-12-20 19:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 1:37 Organising Guix Days Julien Lepiller
2021-12-11 11:09 ` Gábor Boskovits
2021-12-13 9:07 ` zimoun
2021-12-18 17:56 ` Pjotr Prins
2021-12-20 17:51 ` Ludovic Courtès [this message]
2021-12-20 22:37 ` zimoun
2022-01-06 19:54 ` zimoun
2022-01-10 17:16 ` [PATCH] website: Announce Guix days! Julien Lepiller
2022-01-10 19:52 ` Luis Felipe
2022-01-10 21:04 ` Julien Lepiller
2022-01-10 22:44 ` [bug#53166] " Luis Felipe via Guix-patches via
2022-01-10 23:06 ` Julien Lepiller
2022-01-11 0:47 ` Luis Felipe
2022-01-11 9:41 ` Julien Lepiller
2022-01-11 13:15 ` Luis Felipe
2022-01-11 10:56 ` zimoun
2022-01-11 19:16 ` [bug#53166] " Ludovic Courtès
2022-01-12 11:58 ` bug#53166: " Ludovic Courtès
2022-01-12 12:07 ` Julien Lepiller
2022-01-12 12:20 ` Julien Lepiller
2022-01-12 22:07 ` [bug#53166] " Julien Lepiller
-- strict thread matches above, loose matches on Subject: below --
2021-12-30 2:53 Organising Guix Days Blake Shaw
2021-12-31 6:40 ` adriano
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=87tuf3f9lt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).