From: "Sam Jorna (wraeth)" <wraeth@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] How do you feel about non-contributing developers with commit access?
Date: Tue, 6 Nov 2018 12:11:15 +1100 [thread overview]
Message-ID: <5eb0ec2e-0a19-c7e5-83c6-b630e5116a0b@gentoo.org> (raw)
In-Reply-To: <1541171135.899.23.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1839 bytes --]
On 3/11/18 2:05 am, 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.
Hello.
I'd like to suggest that developers be allowed to retain commit
privileges until and unless they are unresponsive to status queries or
have demonstrated some kind of negative intent.
I understand the concern of allowing commit access to persist for AWOL
contributors, but for those with low commit frequency it's effectively
saying "your volunteer contributions aren't enough".
For myself, due to various factors my time for productive commit
development is severely limited, but as I only maintain a couple of
packages which, to my knowledge, don't have any issues, removing commit
access just means those that I do maintain become orphaned, and when I
do get time to work on something I have to work through GitHub or
Bugzilla, increasing work for whichever developer is kind enough to
facilitate my contribution. I am, however, able to be reached quickly,
and responsive to queries.
If a developer is present, is not neglecting anything they maintain, has
not demonstrated any malicious intent, and is offering to spend what
time they can on contributions when they have the time to ensure they
don't break anything, why stop them?
Thanks;
--
Sam Jorna (wraeth)
GPG ID: 0xD6180C26
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-06 1:11 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
2018-11-06 1:11 ` Sam Jorna (wraeth) [this message]
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=5eb0ec2e-0a19-c7e5-83c6-b630e5116a0b@gentoo.org \
--to=wraeth@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