Gentoo Archives: gentoo-dev

From: Alan McKinnon <alan.mckinnon@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights
Date: Wed, 22 Jan 2014 22:06:36
In Reply to: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights by Patrick Lauer
1 On 01/22/14 14:34, Patrick Lauer wrote:
2 >> Do you realise the message that is sent by denying someone access? You
3 >> > are saying that person is not good enough to work on Gentoo. Do you
4 >> > really want to send that message?
5 > Yes. And I have no problem being the Evil Guy who pulls the trigger,
6 > err, presses the enter key.
7 >
8 > You are saying that *any* contribution should be accepted just to not
9 > hurt someones feelings.
12 No, I'm not even remotely saying that. Please go back and read gain what
13 I did say.
15 I never mentioned anything about "any contribution". What I did say
16 comes after the qualifier "by denying someone access", which is a very
17 far cry indeed from "any contribution".
19 I also have no problem being the Evil Guy, because I am that
20 sonofabitch. I really know what happens when you suspend/nuke/delete
21 access because I have done it. And every single time it was the wrong
22 thing to do.
24 The only time it was acceptable is for a runaway script or similar, or
25 an honest mistake where I can fix the fallout far faster than the user
26 can. As the sysadmin and root, I know more about the systems than the
27 users do, similarly in Gentoo land it's a fair assumption that the
28 average QA person is more knowledgeable about the tree and policies than
29 the average dev. So when QA takes action in a spirit of help and with
30 communication in place, all is good and things usually work out well.
32 When it swings the other way and suspension is done as a means of
33 punishment (to whatever degree) then QA has stepped beyond the bounds of
34 what QA is about and into something else.
36 I still don't see any suggestions in this thread on how to limit the
37 scope of what QA wants. No-one will seriously try prevent a good QA guy
38 from limiting damage, but what happens when QA itself abuses the policy?
39 And it will happen, we both know this. How does QA propose to curb that
40 downside?
43 --
44 Alan McKinnon
45 alan.mckinnon@×××××.com