all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Leo Famulari <leo@famulari.name>
Cc: 47111@debbugs.gnu.org
Subject: [bug#47111] [PATCH] doc: Document the guidelines for removing inactive committers.
Date: Sat, 13 Mar 2021 09:07:16 +0100	[thread overview]
Message-ID: <87mtv7zdcb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <YEwK01cSgyCur1ON@jasmine.lan> (Leo Famulari's message of "Fri, 12 Mar 2021 19:44:03 -0500")

Hello,

Leo Famulari <leo@famulari.name> writes:

> To me, security is less of a concern that potential for making mistakes.
> If someone is out of the loop and the committer workflow changes, they
> won't have noticed and could push commits that don't work for `guix
> pull`, or that cause too many rebuilds, or whatever.
>
> How about this:
>
> "In order to reduce the possibility of mistakes, committers will have
> ..."

Sure, if that's the reason why. 

Also, about my second suggestion at the end of the message, I want to
make it clear that regaining commit access is trivial, and does not
imply another vouching process (IIUC), i.e., "you can ask to..." sounds
like it could be refused.

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2021-03-13  8:08 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
2021-03-17  9:56       ` Ludovic Courtès
2021-03-13  0:44   ` Leo Famulari
2021-03-13  8:07     ` Nicolas Goaziou [this message]
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=87mtv7zdcb.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=47111@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.