From: Tom Wijsman <TomWij@gentoo.org>
To: antarus@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights
Date: Thu, 23 Jan 2014 00:29:28 +0100 [thread overview]
Message-ID: <20140123002928.52f32f5b@TOMWIJ-GENTOO> (raw)
In-Reply-To: <CAAr7Pr8iv0B43-P65nPgFBzw7PD9=jOZxaZ8aoSxeTtfEt=Sww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
On Wed, 22 Jan 2014 02:58:45 -0800
Alec Warner <antarus@gentoo.org> wrote:
> Of course it is. We want to send the message that if a person's
> contributions are not up to par, their access to commit to the
> project will be revoked, until they can prove that they can
> contribute at a level that is not detrimental to users or other
> developers. A large portion of the QA team's role in Gentoo is to
> define what 'par' means and at some level, get the community to agree
> with them.
>
> Developer mentorship, for example, generally requires that a
> prospective developer submits changes to their mentor and the mentor
> reviews them. Part of that process is to determine that prospective
> developers can contribute at the expected level and we have quizzes
> to try and verify that developers understand key facets of ebuild
> development. Certainly if a prospective developer routinely submits
> faulty ebuilds and doesn't show improvement, we are unlikely to grant
> them commit access.
True; becoming a developer goes further than obtaining access, it also
involves keeping that access. And everyone knows well enough that it
takes more than a single breakage to permanently lose that access; to
determine where the limits are, one can remember the case with
python-exec where you see that the developer is still around.
Permanently losing it thus takes quite a big effort; in comparison, a
temporary suspension is something rather helpful ("Oh, were I breaking
the tree? Thanks for preventing me from making further damage; sorry, I
forgot to check IRC and/or e-mails. What can we do to fix it?"),
temporary suspensions do not have to be worried about.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-22 23:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 5:02 [gentoo-dev] rfc: formally allow qa to suspend commit rights William Hubbs
2014-01-19 5:07 ` William Hubbs
2014-01-19 5:17 ` [gentoo-dev] " W. Trevor King
2014-01-19 12:46 ` [gentoo-dev] " hasufell
2014-01-20 1:05 ` Tom Wijsman
2014-01-19 20:22 ` Denis Dupeyron
2014-01-20 1:01 ` Tom Wijsman
2014-01-20 1:22 ` Denis Dupeyron
2014-01-20 2:47 ` Tom Wijsman
2014-01-22 16:30 ` Jeroen Roovers
2014-01-20 1:24 ` Alec Warner
2014-01-20 2:54 ` Tom Wijsman
2014-01-20 13:59 ` Rich Freeman
2014-01-20 14:09 ` Alan McKinnon
2014-01-21 0:22 ` Patrick Lauer
2014-01-21 0:46 ` Rich Freeman
2014-01-21 5:29 ` Alec Warner
2014-01-21 5:27 ` Alec Warner
2014-01-22 17:54 ` Ciaran McCreesh
2014-01-22 22:37 ` Andreas K. Huettel
2014-01-22 22:59 ` Tom Wijsman
2014-01-21 14:56 ` Tom Wijsman
2014-01-21 15:47 ` Rich Freeman
2014-01-21 17:26 ` William Hubbs
2014-01-21 17:50 ` Rich Freeman
2014-01-21 17:56 ` Peter Stuge
2014-01-21 18:11 ` Tom Wijsman
2014-01-21 18:16 ` Peter Stuge
2014-01-21 19:18 ` Tom Wijsman
2014-01-21 21:03 ` Thomas Sachau
2014-01-21 22:56 ` Tom Wijsman
2014-01-21 23:14 ` William Hubbs
2014-01-22 7:00 ` Alan McKinnon
2014-01-22 10:36 ` hasufell
2014-01-22 10:39 ` hasufell
2014-01-22 10:58 ` Alec Warner
2014-01-22 23:29 ` Tom Wijsman [this message]
2014-01-22 12:34 ` Patrick Lauer
2014-01-22 19:42 ` Rich Freeman
2014-01-22 23:40 ` Tom Wijsman
2014-01-22 22:06 ` Alan McKinnon
2014-01-22 23:15 ` Tom Wijsman
2014-01-21 23:20 ` hasufell
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=20140123002928.52f32f5b@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=antarus@gentoo.org \
--cc=gentoo-dev@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