public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] How do you feel about non-contributing developers with commit access?
Date: Fri, 2 Nov 2018 21:27:22 +0300	[thread overview]
Message-ID: <20181102212722.5908278c22a9f29900db4609@gentoo.org> (raw)
In-Reply-To: <1541171135.899.23.camel@gentoo.org>

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

Hi,

On Fri, 02 Nov 2018 16:05:35 +0100 Michał Górny wrote:
> Hello,
> 
> The Undertakers team has frequently received various forms of
> 'criticism' of their effort in attempting to find and retire inactive
> developers.  This is getting as far as to claim that we shouldn't retire
> anyone because there are no limits on commit slots.
> 
> Therefore, I would like to ask the wider community a general question:
> how do you feel about preserving commit access for people who no longer
> actively commit to Gentoo?  I'm talking about extreme cases, say,
> no commits to any user-visible repository for over a year.

Due to security concerns one year of inactivity is a fair margin for
retirement, but AFAIK with current policy undertakers may become
active after 2 months of inactivity and are quite active after half
a year.

Also care should be taken to account indirect commits, e.g. when
developer in question is author, but not commiter. This may happen
due to many reasons, e.g. review and commit by a maintainer which
is another dev.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-11-02 18:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 15:05 [gentoo-project] How do you feel about non-contributing developers with commit access? Michał Górny
2018-11-02 16:22 ` Matthew Thode
2018-11-02 16:43   ` M. J. Everitt
2018-11-02 18:18     ` Andrew Savchenko
2018-11-07 12:45   ` Jason Zaman
2018-11-12  4:38     ` desultory
2018-11-14 20:08       ` Matt Turner
2018-11-14 20:13         ` M. J. Everitt
2018-11-14 20:14           ` M. J. Everitt
2018-11-02 16:35 ` Michael Orlitzky
2018-11-02 18:27 ` Andrew Savchenko [this message]
2018-11-06  1:11 ` Sam Jorna (wraeth)
2018-11-06  5:12   ` Raymond Jennings
2018-11-06  9:15     ` Sam Jorna (wraeth)
2018-11-06 13:06       ` Raymond Jennings
2018-11-12 23:21 ` Alec Warner
2018-11-12 23:40   ` Raymond Jennings

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=20181102212722.5908278c22a9f29900db4609@gentoo.org \
    --to=bircoph@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox