1 |
On Fri, 2019-04-12 at 17:19 +0200, Ulrich Mueller wrote: |
2 |
> > > > > > On Fri, 12 Apr 2019, Michał Górny wrote: |
3 |
> > Update the wording of GLEP 48 to provide clear information on what |
4 |
> > kind of disciplinary actions QA can issue, and in what circumstances |
5 |
> > they can be exercised. Remove the unclear reference to ComRel that is |
6 |
> > either meaningless or violation of scope. |
7 |
> |
8 |
> Comrel is about disciplinary actions, while QA is about the status of |
9 |
> the tree. IMHO we should keep that distinction, and not try to transform |
10 |
> QA into a second Comrel. This has been discussed several times in the |
11 |
> past, and the outcome always was that QA doesn't need such additional |
12 |
> superpowers. |
13 |
|
14 |
Then how are things exactly supposed to work? I think you can agree |
15 |
that the way it's defined now is open to wide range of interpretation. |
16 |
|
17 |
If I file a bug asking ComRel to consider acting on a developer causing |
18 |
repeated issues, ComRel's going to close the bug as 'QA business'. Now, |
19 |
if I said I'm filing the bug on behalf of QA, QA is going to shot me for |
20 |
unilaterally requesting something on behalf of QA. |
21 |
|
22 |
Therefore, according to the de facto policy QA votes first on whether to |
23 |
ask ComRel to vote for a disciplinary action. However, by its role |
24 |
ComRel is not guaranteed to have competence judging QA violations. How |
25 |
does this bureaucracy exactly help anyone? |
26 |
|
27 |
> Also in my role as deputy QA lead, I find it strange that you post a |
28 |
> patch to the mailing list, without first discussing your proposal within |
29 |
> the QA team. |
30 |
> |
31 |
|
32 |
Are you suggesting that we should handle such affairs in secret, rather |
33 |
than discuss them in the open? How does that help transparency, |
34 |
especially given all the past accusations of making arbitrary decisions |
35 |
behind the scenes. |
36 |
|
37 |
-- |
38 |
Best regards, |
39 |
Michał Górny |