Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights
Date: Tue, 21 Jan 2014 15:47:58
In Reply to: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights by Tom Wijsman
1 On Tue, Jan 21, 2014 at 9:56 AM, Tom Wijsman <TomWij@g.o> wrote:
2 > If a developer does an unannounced mass action that breaks the tree
3 > severely or is heavily prohibited by policy, is unreachable while he
4 > continues to commit this; then it would be handy to "temporarily" be
5 > able to withdraw the commit access to bring it to that developer's
6 > attention.
8 Hadn't really thought about it in this light. In this situation
9 restricting commit access is being used as a technical solution to a
10 technical problem - not unlike killing a runaway process.
12 I have no issues at all with QA taking action in a manner like this,
13 though unless that mass-update is really slow I doubt we'd ever react
14 in time.
16 What I don't like is the idea of QA taking what amounts to punitive
17 measures. I think that this is a role best held by Comrel. I do
18 appreciate Markos's comments regarding Comrel not being the right
19 solution to a technical problem. I do not see Comrel has having a
20 role in mediating a dispute between QA and a developer over the
21 correctness of policy or its enforcement (personal conflicts are a
22 different matter as Markos acknowledges). What I do see Comrel has
23 having a role in is a developer who simply refuses to follow policy -
24 whether that is CoC, technical policy, or whatever. In the case of
25 CoC Cevrel is judge, jury, and executive (that is, they determine
26 whether it was violated in addition to dealing with the fact that it
27 was). In the case of a QA issue QA is the jury (they determine if the
28 policy was violated), and Comrel is the judge and executive (they
29 determine how to get the dev to go along with policy or get rid of
30 them).
32 If Comrel really objects to this I'm not entirely opposed to letting
33 QA have the reins (certainly we can't just let policy go unenforced
34 entirely). However, I would encourage the teams to give some thought
35 as to whether it makes sense to work together to separate the human vs
36 technical factors here.
38 This discussion has been helpful...
40 Rich


Subject Author
Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights William Hubbs <williamh@g.o>