all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org, Manolis Ragkousis <ragkousism@protonmail.com>
Subject: Re: Guix Days and FOSDEM 2021
Date: Thu, 21 Jan 2021 11:53:40 +0100	[thread overview]
Message-ID: <87mtx2blxn.fsf@gnu.org> (raw)
In-Reply-To: <20210116204253.6fkajnshcan2itha@thebird.nl> (Pjotr Prins's message of "Sat, 16 Jan 2021 21:42:53 +0100")

Hi,

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> A reminder that thanks to our organising team we have a great line up
> for FOSDEM:
>
>   https://fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/
>
> with famous Guix contributors and Guixers doing the moderating :) All
> virtual and online this year, so you can attend from anywhere! Put
> Sunday February 7th in your diary!

Yay!

> And then on Monday 8th we have another Guix day online as a low
> profile unconference. Do sign up and we'll send a reminder here. See
>
>   https://libreplanet.org/wiki/Group:Guix/FOSDEM2021
>
> It is great to do a virtual FOSDEM this way and be able to reach a far
> wider audience. Even so we are also happy if just 10 people show up and
> get some declarative hacking done :)

We’ll have to refine the program or at least the main parts for the Guix
day (I think some of the items were copied from last year :-)).

Let’s also have a blog post on-line around Feb 1st along the lines of
<https://guix.gnu.org/en/blog/2020/meet-guix-at-fosdem-2020/>!

Thank you Manolis & Pjotr for organizing all this as always!

Ludo’.


      reply	other threads:[~2021-01-21 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 14:04 Guix Days and FOSDEM 2021 Pjotr Prins
2021-01-16 20:42 ` Pjotr Prins
2021-01-21 10:53   ` Ludovic Courtès [this message]

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

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

  git send-email \
    --in-reply-to=87mtx2blxn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    --cc=ragkousism@protonmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.