unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Guix co-maintainers rotation
Date: Wed, 04 Aug 2021 11:06:25 -0400	[thread overview]
Message-ID: <8735rp8d1q.fsf@gmail.com> (raw)

Dear Guix community,

For some time already, two current Guix co-maintainers have expressed
the wish to withdraw themselves from their current duties: Ludovic
Courtès and Marius Bakke.  This would reduce the current co-maintainers
collective to the following remaining individuals: Tobias
Geerinckx-Rice, Mathieu Othacehe and myself, Maxim Cournoyer.

While this may come as sad news, I like to think that this will free
their hands from the administrative work, and hopefully allow them to
continue delivering neat and clever Guix-related hacks, as they see fit
and as time permits, of course :-).  It will also be an opportunity to
test if the co-maintainers collective that formed back in 2019 [0] has
sufficiently matured to take on the various challenges involved in
keeping the project and the community thriving, independently of
Ludovic, which created and nurtured GNU Guix from its beginning in 2012
and played key roles in various aspects of the project.

As a reminder, the core duties of Guix co-maintainers are:

1. Enforcing GNU and Guix policies, such as the project’s commitment to
be released under a copyleft free software license (GPLv3+) and to
follow the Free System Distribution Guideline (FSDG).

2. Enforcing our code of conduct: maintainers are the contact point for
anyone who wants to report abuse.

3. Making decisions, about code or anything, when consensus cannot be
reached.

We'd like to use this opportunity to send a new call for volunteers who
would be interested in becoming co-maintainers and helping out with the
above, and more!  We are looking for people with a time-proven track
record of GNU Guix contributions, with good communication and mediation
skills.

Let's all take a moment to share our gratitude to both Marius and
Ludovic, who have done so much to make GNU Guix the enjoyable project
(both as a technical project and community) that it is today.

Thank you!

Maxim
On behalf of the Guix co-maintainers

[0]  https://guix.gnu.org/blog/2019/gnu-guix-maintainer-collective-expands/


             reply	other threads:[~2021-08-04 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 15:06 Maxim Cournoyer [this message]
2021-08-04 18:13 ` Guix co-maintainers rotation Jack Hill
2021-08-04 19:09   ` Anadon
2021-08-04 19:31 ` Luis Felipe
2021-08-04 22:26 ` Thiago Jung Bauermann

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=8735rp8d1q.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@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.
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).