all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
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 03:41:26 +0100	[thread overview]
Message-ID: <86y2erhj1l.fsf@gmail.com> (raw)
In-Reply-To: <YEwR/sTVeVMH+b41@jasmine.lan>

Hi,

On Fri, 12 Mar 2021 at 20:14, Leo Famulari <leo@famulari.name> wrote:
> On Sat, Mar 13, 2021 at 01:46:35AM +0100, zimoun wrote:
>> On Fri, 12 Mar 2021 at 15:32, Leo Famulari <leo@famulari.name> wrote:
>> Making it explicit, what does it mean “inactivity” in “after 12 months
>> of inactivity”?  Instead why not «after 12 months without using their
>> commit access rights»?
>
> They might have been highly active on the mailing lists and the bug
> tracker, in which case there may not be any reason to remove them. These
> are just guidelines, they will not be enforced exactly.

In the issue [1] introducing the Commit Access section, there is a
discussion.  Anyway. :-)

In my views, they do not need commit access to be active on the mailing
lists and/or the bug tracker.  The set of people with commit access
should be restricted to people who effectively commit; especially with
the authentication dance.  Well, if in the past 12 (or 18?) months, they
are not able to push couple* of patches waiting in the tracker or update
couple* of packages or push a fix or … I miss why do they need a commit
access, i.e., in my views they are inactive as committer.  It’s fine,
life happens.  And since commit access is about trust and they are
already trusted, they can request later a commit access if they are able
to be active again.

*couple meaning here 2 or more. :-)


I agree that these are just guidelines and they will not be enforced
exactly, e.g., counting the number of days of “inactivity”. :-)

Well, I am only suggesting something that appeared vague when I read
it.  Otherwise, LGTM. :-)


1: <http://issues.guix.gnu.org/issue/38846>


Cheers,
simon




      reply	other threads:[~2021-03-13  2:51 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
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 [this message]

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=86y2erhj1l.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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.