public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: hasufell <hasufell@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights
Date: Wed, 22 Jan 2014 00:20:54 +0100	[thread overview]
Message-ID: <52DF00D6.8060205@gentoo.org> (raw)
In-Reply-To: <52DD2E2A.2020303@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/20/2014 03:09 PM, Alan McKinnon wrote:
> On 01/20/14 15:59, Rich Freeman wrote:
>> On Sun, Jan 19, 2014 at 9:54 PM, Tom Wijsman <TomWij@gentoo.org>
>> wrote:
>>> #gentoo-qa | @hwoarang: pretty sure diego had the powerzz to
>>> suspend people
>>> 
>>> Whether this has actually happened is something that is
>>> questionable;
>> 
>> Not that this necessarily needs to make it into the GLEP, and
>> I'm still on the fence regarding whether we really need to make
>> this change at all, but things like access suspensions and other 
>> administrative/disciplinary procedures should be documented.  I
>> think whether this is a matter of public record or not is open to
>> debate, but I don't like the fact that we can really say for sure
>> when/if this has actually happened.
> 
> 
> Speaking as someone who had this power in his day job, for QA to be
> able to suspend accounts is a very bad idea indeed. It always ends
> badly. I suspended 20+ accounts in my current job over the years
> and the number of cases where it was the right thing to do is
> precisely 0.
> 
> It was always a case of ill-advised action taken out of
> frustration, or bypass the training step, or don't try hard enough
> to reach the "infringer" and communicate like grown adults. Yup, I
> did all three.
> 
> Suspending an account is a very serious thing to undertake, the
> effects on the suspended person are vast and this power should
> never lie with the person who is feeling the pain. Instead, there
> are well established channels to the body who can make the
> decision. If QA has a problem with a dev for any reason whatsoever,
> then QA should make a well-thought out case to that other body for
> decision. Anything else is madness and open invitation for it to
> all go south.
> 
> 

Yep. This proposal is actually another workaround that emerges,
because people do not communicate and ignore each other. This is a
common habit in the gentoo dev community and it seems we have accepted
that fact.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS3wDWAAoJEFpvPKfnPDWzPYYH/A87fN34q1ShBhPvIh2uqP1K
UogA7se08pol0abNpDenYM2qDcTxYWXRPgYS7xXcrjh1bbhDmI+/0zuW7vd8/AWh
V20TffIkMHr1hMWyFKysFD6VKZC8DYr8fCGkgEfTRAjv1mdGFvfX+k1cqUZ+VtKB
bNPiH5Op7EOqpBp/5oz/CmGNFB8nPPEsDRrUbkE/hBPO3JfufBVHdDnmgJg9s0Og
Yd5dS55wQTTX7mbLDL4LePDF5pEtM9LnGc2uLgvDrepyX0Z2rio8aNnn/UI0IrY2
p7gkpMK9aA8vSixuvz3qpQbDs0julAswv5ZjTNgu237nukp1yiJGcAwjCDrCRl0=
=HdSb
-----END PGP SIGNATURE-----


      parent reply	other threads:[~2014-01-21 23:21 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
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 [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=52DF00D6.8060205@gentoo.org \
    --to=hasufell@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