all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 47111@debbugs.gnu.org, leo@famulari.name
Subject: [bug#47111] [PATCH] doc: Document the guidelines for removing inactive committers.
Date: Sat, 13 Mar 2021 09:02:52 +0100	[thread overview]
Message-ID: <87tupfzdjn.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87zgz7aolq.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sat, 13 Mar 2021 01:23:13 +0100")

Hello,

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

> I'd prefer it not justifying itself nor making more claims than
> strictly necessary.

My concern is that removing commit access is also a symbolic act, which
could be taken personally. I think it is necessary to explain the reason
behind it. IOW, I suggest to make sure the message is not understood as
"you are deemed useless after 12 months not working for us".

Minimal explanation leads to maximal interpretation, and not everyone
has the same English command.

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2021-03-13  8:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 20:32 [bug#47111] [PATCH] doc: Document the guidelines for removing inactive committers Leo Famulari
2021-03-12 23:51 ` Nicolas Goaziou
2021-03-13  0:23   ` Tobias Geerinckx-Rice via Guix-patches via
2021-03-13  8:02     ` Nicolas Goaziou [this message]
2021-03-17  9:56       ` Ludovic Courtès
2021-03-13  0:44   ` Leo Famulari
2021-03-13  8:07     ` Nicolas Goaziou
2021-03-13 19:13       ` Leo Famulari
2021-03-14 18:13         ` Nicolas Goaziou
2021-03-17 10:05     ` Ludovic Courtès
2021-03-17 12:12       ` zimoun
2021-03-18 20:10         ` bug#47111: " Leo Famulari
2021-03-13  0:46 ` [bug#47111] " zimoun
2021-03-13  1:14   ` Leo Famulari
2021-03-13  2:41     ` zimoun

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=87tupfzdjn.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=47111@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=me@tobias.gr \
    /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.