all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
	guix-devel@gnu.org, Mark H Weaver <mhw@netris.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Statement from the Guix maintainers regarding recent events
Date: Mon, 14 Mar 2022 14:31:23 +0100	[thread overview]
Message-ID: <871qz4fyok.fsf@xelera.eu> (raw)
In-Reply-To: <87F646A6-A9AA-4813-BCF1-5B1EFB5CD96A@tobias.gr>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

Dear all,

sorry if I comment this thread just today, but I had a very long backlog
of guix-devel messages

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Maxim wasn't directly involved.  Neither was the CoC.  I was.
>
> If you're really curious about what happened you can read the past
> days' archived threads in which Taylan participated.

OK, now we know that the involved messages was from Taylan and we could
check the archives

> We're not going to rehash them here.

I don't want to rehash them at all, but please consider that the
original statement cannot be understood since it lacks proper references
to the facts that led to the decision, at least for people like me who
does not read each and every thread.

Thankk you for your patience in moderating this list!

[...]

Ciao, Giovanni

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2022-03-14 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 15:25 Statement from the Guix maintainers regarding recent events Maxim Cournoyer
2022-03-01 17:39 ` 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qz4fyok.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    --cc=mhw@netris.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.