From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Statement from the Guix maintainers regarding recent events
Date: Tue, 01 Mar 2022 10:25:25 -0500 [thread overview]
Message-ID: <87bkyp3day.fsf@gmail.com> (raw)
Hi everyone,
Given the recent action from one community member on this list that led
to multiple people feeling hurt or uneasy about the whole situation, we,
the Guix maintainers collective, would like to reaffirm our commitment
to protect our community against such actions.
The Guix community has historically been a very inclusive, welcoming and
safe harbor for everyone to enjoy hacking together, and we'd like it to
remain that way. The Code of Conduct that everyone interacting in our
community implicitly agrees to follow has demonstrated its usefulness in
keeping the (thankfully rare) abusive actors at bay.
To reduce the chance of a similar situation reoccurring in the future,
the Guix maintainers have acted on the following:
* The person who lacked judgment and caused hurt by repeatedly pushing
their exclusionary views onto our community have been removed from the
trusted list, meaning each of their messages will now have to go
through moderation.
* Our Code of Conduct copy has been upgraded to its latest version.
* A header to the Code of Conduct now mentions any
suggestions/discussion with regard to the Code of Conduct should now
go through the Guix maintainers rather than in the public fora.
We hope that we as a community can grow stronger and more united in the
aftermath of this regrettable event.
Sincerely,
Maxim
On behalf of the Guix maintainers
next reply other threads:[~2022-03-01 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 15:25 Maxim Cournoyer [this message]
2022-03-01 17:39 ` Statement from the Guix maintainers regarding recent events Ekaitz Zarraga
2022-03-01 20:46 ` Kaelyn
2022-03-02 4:06 ` Mark H Weaver
2022-03-02 5:26 ` Tobias Geerinckx-Rice
2022-03-14 13:31 ` Giovanni Biscuolo
2022-03-02 5:54 ` Maxim Cournoyer
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=87bkyp3day.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).