1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
2 |
Hash: SHA256
|
3 |
|
4 |
On Fri, 12 Apr 2019 18:10:43 +0200
|
5 |
Michał Górny <mgorny@g.o> wrote:
|
6 |
|
7 |
> On Fri, 2019-04-12 at 17:19 +0200, Ulrich Mueller wrote: |
8 |
> > > > > > > On Fri, 12 Apr 2019, Michał Górny wrote: |
9 |
> > > Update the wording of GLEP 48 to provide clear information on what |
10 |
> > > kind of disciplinary actions QA can issue, and in what |
11 |
> > > circumstances they can be exercised. Remove the unclear reference |
12 |
> > > to ComRel that is either meaningless or violation of scope. |
13 |
> > |
14 |
> > Comrel is about disciplinary actions, while QA is about the status |
15 |
> > of the tree. IMHO we should keep that distinction, and not try to |
16 |
> > transform QA into a second Comrel. This has been discussed several |
17 |
> > times in the past, and the outcome always was that QA doesn't need |
18 |
> > such additional superpowers. |
19 |
> |
20 |
> Then how are things exactly supposed to work? I think you can agree |
21 |
> that the way it's defined now is open to wide range of interpretation. |
22 |
> |
23 |
> If I file a bug asking ComRel to consider acting on a developer |
24 |
> causing repeated issues, ComRel's going to close the bug as 'QA |
25 |
> business'. Now, if I said I'm filing the bug on behalf of QA, QA is |
26 |
> going to shot me for unilaterally requesting something on behalf of |
27 |
> QA. |
28 |
> |
29 |
> Therefore, according to the de facto policy QA votes first on whether |
30 |
> to ask ComRel to vote for a disciplinary action. However, by its role |
31 |
> ComRel is not guaranteed to have competence judging QA violations. |
32 |
> How does this bureaucracy exactly help anyone? |
33 |
|
34 |
comrel shouldn't close the bug as 'QA business': What comrel is
|
35 |
supposed to act on is the "repeated and on purpose" part.
|
36 |
-----BEGIN PGP SIGNATURE-----
|
37 |
|
38 |
iHUEAREIAB0WIQSpOxaxaZikKNVNlsYOJUi7xgflrgUCXMMVHAAKCRAOJUi7xgfl
|
39 |
rr7jAP46eAaR03FF6Lo/9ZyI4X6Ps2czp0PeW5u/zGBcdqBS7wD+IkCnbofHYhCH
|
40 |
Tbb2iUh8ExF5rhLlW77n08xU7j8QBdE=
|
41 |
=vHY8
|
42 |
-----END PGP SIGNATURE----- |