unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Todor Kondić" <tk.code@protonmail.com>
To: help-guix@gnu.org
Subject: Re: GNU Guix maintainer rotation
Date: Sun, 09 Jan 2022 16:43:50 +0000	[thread overview]
Message-ID: <rqtnWOImZfqnDlZ70JDr8z8r3pZQG1kFRnEOOlwA_vYhBW3dLfRs6YzBVlo7OoM2kwe9iqg7odyZshKpgvK1PBn0ntfZvxSxf02Xyv8R04c=@protonmail.com> (raw)
In-Reply-To: <8735lyjq9k.fsf@rdklein.fr>

> Thank you Ludovic and Marius :)
>
> And good luck to Efraim !
>
> Maxim Cournoyer maxim.cournoyer@gmail.com writes:
>
> > Hello Guix!
> >
> > I'd like to bring your attention to a change to the current Guix
> >
> > maintainers collective; in a nutshell, Ludovic and Marius are stepping
> >
> > down from maintainer-ship while Efraim is joining.
> >
> > I won't write more as you can find all the details in this blog post:
> >
> > https://guix.gnu.org/en/blog/2022/gnu-guix-maintainer-rotation/.
> >
> > Many thanks to Ludovic and Marius for their past roles as Guix
> >
> > co-maintainers, and a warm welcome to Efraim!
> >
> > Happy hacking!
> >
> > Maxim


Wow, what news!

I am one of those perpetual users and very occasional (package) contributors [so, mostly useless ;) ]. First heard about Guix on the Guile mailing list around the time of its beginnings before what now what feels ages ago (just checked ... nine years), but only started actually using it cca 0.1 version thanks to a blog post by Andy Wingo. These days it's reproducibly powering virtually every compute platform I use as, at least, a package (and "container") manager. What a road must have it been for Ludovic and the early crew. Many thanks to them and of course good luck to the new maintainers.


      reply	other threads:[~2022-01-09 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 20:22 GNU Guix maintainer rotation Maxim Cournoyer
2022-01-06 21:22 ` Jérémy Korwin-Zmijowski
2022-01-07 15:21 ` Katherine Cox-Buday
2022-01-08  1:09 ` Leo Famulari
2022-01-08 11:48   ` Oliver Propst
2022-01-08 13:43 ` Edouard Klein
2022-01-09 16:43   ` Todor Kondić [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

  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='rqtnWOImZfqnDlZ70JDr8z8r3pZQG1kFRnEOOlwA_vYhBW3dLfRs6YzBVlo7OoM2kwe9iqg7odyZshKpgvK1PBn0ntfZvxSxf02Xyv8R04c=@protonmail.com' \
    --to=tk.code@protonmail.com \
    --cc=help-guix@gnu.org \
    /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.
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).