| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01/20/2014 03:09 PM, Alan McKinnon wrote: |
| 5 |
> On 01/20/14 15:59, Rich Freeman wrote: |
| 6 |
>> On Sun, Jan 19, 2014 at 9:54 PM, Tom Wijsman <TomWij@g.o> |
| 7 |
>> wrote: |
| 8 |
>>> #gentoo-qa | @hwoarang: pretty sure diego had the powerzz to |
| 9 |
>>> suspend people |
| 10 |
>>> |
| 11 |
>>> Whether this has actually happened is something that is |
| 12 |
>>> questionable; |
| 13 |
>> |
| 14 |
>> Not that this necessarily needs to make it into the GLEP, and |
| 15 |
>> I'm still on the fence regarding whether we really need to make |
| 16 |
>> this change at all, but things like access suspensions and other |
| 17 |
>> administrative/disciplinary procedures should be documented. I |
| 18 |
>> think whether this is a matter of public record or not is open to |
| 19 |
>> debate, but I don't like the fact that we can really say for sure |
| 20 |
>> when/if this has actually happened. |
| 21 |
> |
| 22 |
> |
| 23 |
> Speaking as someone who had this power in his day job, for QA to be |
| 24 |
> able to suspend accounts is a very bad idea indeed. It always ends |
| 25 |
> badly. I suspended 20+ accounts in my current job over the years |
| 26 |
> and the number of cases where it was the right thing to do is |
| 27 |
> precisely 0. |
| 28 |
> |
| 29 |
> It was always a case of ill-advised action taken out of |
| 30 |
> frustration, or bypass the training step, or don't try hard enough |
| 31 |
> to reach the "infringer" and communicate like grown adults. Yup, I |
| 32 |
> did all three. |
| 33 |
> |
| 34 |
> Suspending an account is a very serious thing to undertake, the |
| 35 |
> effects on the suspended person are vast and this power should |
| 36 |
> never lie with the person who is feeling the pain. Instead, there |
| 37 |
> are well established channels to the body who can make the |
| 38 |
> decision. If QA has a problem with a dev for any reason whatsoever, |
| 39 |
> then QA should make a well-thought out case to that other body for |
| 40 |
> decision. Anything else is madness and open invitation for it to |
| 41 |
> all go south. |
| 42 |
> |
| 43 |
> |
| 44 |
|
| 45 |
Yep. This proposal is actually another workaround that emerges, |
| 46 |
because people do not communicate and ignore each other. This is a |
| 47 |
common habit in the gentoo dev community and it seems we have accepted |
| 48 |
that fact. |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 51 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 52 |
|
| 53 |
iQEcBAEBAgAGBQJS3wDWAAoJEFpvPKfnPDWzPYYH/A87fN34q1ShBhPvIh2uqP1K |
| 54 |
UogA7se08pol0abNpDenYM2qDcTxYWXRPgYS7xXcrjh1bbhDmI+/0zuW7vd8/AWh |
| 55 |
V20TffIkMHr1hMWyFKysFD6VKZC8DYr8fCGkgEfTRAjv1mdGFvfX+k1cqUZ+VtKB |
| 56 |
bNPiH5Op7EOqpBp/5oz/CmGNFB8nPPEsDRrUbkE/hBPO3JfufBVHdDnmgJg9s0Og |
| 57 |
Yd5dS55wQTTX7mbLDL4LePDF5pEtM9LnGc2uLgvDrepyX0Z2rio8aNnn/UI0IrY2 |
| 58 |
p7gkpMK9aA8vSixuvz3qpQbDs0julAswv5ZjTNgu237nukp1yiJGcAwjCDrCRl0= |
| 59 |
=HdSb |
| 60 |
-----END PGP SIGNATURE----- |
Archives