1 |
On 24.02.2020 10:47, Michał Górny wrote: |
2 |
> On Sat, 2020-02-22 at 22:35 -0800, Alec Warner wrote: |
3 |
>> On Fri, Feb 21, 2020 at 9:39 PM Michał Górny <mgorny@g.o> wrote: |
4 |
>> |
5 |
>>> On Fri, 2020-02-21 at 22:11 +0000, Roy Bamford wrote: |
6 |
>>>> This 'revision' group alread exists. Its called the Gentoo council. |
7 |
>>>> Unless, that is, council have no oversight of comrel? |
8 |
>>> No, that's not how things work. You don't have an appeal body |
9 |
>>> proactively look into what all projects are doing. |
10 |
>>> |
11 |
>> I think by definition this is reactive. Comrel publishes a report[0], and |
12 |
>> the Council[1] reviews it. |
13 |
> I thought we've already established that the reports are meaningless. |
14 |
> |
15 |
> The way I see it, your system basically means that, repeatedly: |
16 |
> |
17 |
> 1. ComRel does their job. |
18 |
> |
19 |
> 2. ComRel wastes their time publishing a meaningless report. |
20 |
> |
21 |
> 3. Since the report is meaningless, Council has to audit ComRel's work. |
22 |
> |
23 |
> Since digging for past data is usually more effort than processing it |
24 |
> as it flows, Council may as well start proactively auditing everything. |
25 |
> Except that's not its purpose, and I don't see why we should throw |
26 |
> random extra tasks on their plate just because. |
27 |
> |
28 |
> In my opinion, if we are to go for auditing ComRel, we should select |
29 |
> a separate group of people for that, people that choose to put their |
30 |
> effort into auditing rather than incidentally get dragged into it. |
31 |
> Furthermore, I believe this group should not have any direct deciding |
32 |
> power. Instead, they should bring any issues their find to ComRel's |
33 |
> attention and/or appeal them to the Council. |
34 |
> |
35 |
|
36 |
This is meaningless also, because an individual who finds ComRel |
37 |
decision unacceptable can appeal to Council directly, you do not need |
38 |
third party layer here. |