From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: help-guix <help-guix@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: GNU Guix maintainer collective update
Date: Mon, 04 May 2020 09:31:46 -0400 [thread overview]
Message-ID: <87v9lb3jy5.fsf@gmail.com> (raw)
Hello Guix!
There's a new blog post about a recent update to the GNU Guix maintainer
collective [0]. I won't repeat the blog post here, but in a few words,
Ricardo Wurmus is stepping down from his role and Mathieu Othacehe
is joining in.
Let's take a moment to thank Ricardo for his time as a Guix
co-maintainer. He's been immensely useful to the project and I hope
we'll continue to see him around.
Let's also welcome Mathieu Othacehe in his new role! Congratulations,
Mathieu! :-)
[0] https://guix.gnu.org/blog/2020/gnu-guix-maintainer-collective-update/
Maxim
next reply other threads:[~2020-05-04 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:31 Maxim Cournoyer [this message]
2020-05-04 14:27 ` GNU Guix maintainer collective update sirgazil
2020-05-04 15:08 ` Jack Hill
2020-05-11 17:08 ` Christopher Lemmer Webber
2020-05-05 0:58 ` John Soo
2020-05-05 21:18 ` Björn Höfling
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=87v9lb3jy5.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--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).