From: raingloom <raingloom@riseup.net>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: Leaving the GNU Guix community
Date: Wed, 5 May 2021 16:27:51 +0200 [thread overview]
Message-ID: <20210505162751.07eee305@riseup.net> (raw)
In-Reply-To: <4b0a5a3eee7f0c2cad7ede9b31fd6d5544c0dfad.camel@zaclys.net>
On Sat, 01 May 2021 19:47:40 +0200
Léo Le Bouter <lle-bout@zaclys.net> wrote:
> I think it is a disaster that you (maintainers) choose to blame
> someone publicly for feeling so bad after having received messages of
> exceptional aggressivity.
Disclaimer: I only saw some of the relevant discussion, so, please don't
shout at me or assume I'm saying this to hurt anyone.
For what it's worth, blame-free security culture is possible. I was
reading Google's Site Reliability Engineering stuff a few months ago,
which - among other things - talked about exactly this. People need to
feel like they can make mistakes without being attacked for them,
otherwise they won't be open when they inevitably do mess something up.
But I should add that if someone does mess up, it should not be
controversial - to them or their team - to put more oversight on them.
Anyways, I hope you'll stay, and that everyone will strive to make this
an actually inclusive community.
next prev parent reply other threads:[~2021-05-05 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 23:43 Leaving the GNU Guix community Leo Le Bouter
2021-04-30 0:31 ` Ryan Prior
2021-04-30 1:01 ` aviva
2021-04-30 11:03 ` Leo Prikler
2021-04-30 11:10 ` Ludovic Courtès
2021-04-30 17:54 ` Pierre Neidhardt
2021-05-01 2:34 ` Tobias Geerinckx-Rice
2021-05-01 14:45 ` Joshua Branson
2021-05-01 17:47 ` Léo Le Bouter
2021-05-05 14:27 ` raingloom [this message]
2021-05-01 4:51 ` Chris Marusich
2021-05-02 0:15 ` Making technology more inclusive Was: " Denis 'GNUtoo' Carikli
2021-05-05 21:11 ` raingloom
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=20210505162751.07eee305@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
/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).