all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 47111@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#47111] [PATCH] doc: Document the guidelines for removing inactive committers.
Date: Wed, 17 Mar 2021 11:05:14 +0100	[thread overview]
Message-ID: <878s6m5c4l.fsf_-_@gnu.org> (raw)
In-Reply-To: <YEwK01cSgyCur1ON@jasmine.lan> (Leo Famulari's message of "Fri, 12 Mar 2021 19:44:03 -0500")

Hi Leo,

Leo Famulari <leo@famulari.name> skribis:

> How about this:
>
> "In order to reduce the possibility of mistakes, committers will have
> ..."

I like this.

> On Sat, Mar 13, 2021 at 09:07:16AM +0100, Nicolas Goaziou wrote:
>> 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.
>
> It could be refused. It really depends on the situation, and the
> decision is at the discretion of the maintainers. In many cases a simple
> "Hi, I'm back!" email will be enough, but the text I propose is not
> offering a guarantee.

Perhaps, after “they can ask to regain commit access by emailing the
maintainers” we can add “without going through the vouching process”?
Would that address your concerns, Nicolas?

To be clear, I think this would be dealt with on a case-by-case basis.
I expect that by far the most frequent situation would be one where
maintainers know the person and immediately restore their access.  In
other cases, as the project gets older, maintainers could feel the need
to go through the regular contribution and vouching process.

IOW, I think this process should be as smooth as possible, but we should
not suggest it’s automatic.

Thoughts?

Ludo’.




  parent reply	other threads:[~2021-03-17 10:06 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
2021-03-13 19:13       ` Leo Famulari
2021-03-14 18:13         ` Nicolas Goaziou
2021-03-17 10:05     ` Ludovic Courtès [this message]
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=878s6m5c4l.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=47111@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=mail@nicolasgoaziou.fr \
    /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.