public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: comrel changes
Date: Mon, 24 Feb 2020 09:19:26 +0100	[thread overview]
Message-ID: <7c54caacaed187e36b3302ccc7d8d4c435247d24.camel@gentoo.org> (raw)
In-Reply-To: <ef617fa0-6a52-7433-062f-976bc4bd7942@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]

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

The individual can only judge the reply to his own request.  He lacks
the wider context to audit the process and decisions (or lack of them)
wrt multiple different requests.

This works both ways.  People are also making accusations and claim
about ComRel based on what they guess might be happening.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2020-02-24  8:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 16:18 [gentoo-project] rfc: comrel changes William Hubbs
2020-02-17 16:36 ` Michał Górny
2020-02-17 18:10   ` William Hubbs
2020-02-17 20:31     ` Michał Górny
2020-02-17 20:51       ` William Hubbs
2020-02-17 16:43 ` [gentoo-project] " Matt Turner
2020-02-18  0:08   ` William Hubbs
2020-02-18  5:23     ` Michał Górny
2020-02-18 20:12 ` [gentoo-project] " Alec Warner
2020-02-18 22:06   ` Matt Turner
2020-02-18 22:53     ` Roy Bamford
2020-02-18 23:30   ` Michael 'veremitz' Everitt
2020-02-20 21:24   ` Chí-Thanh Christopher Nguyễn
2020-02-20 23:40     ` Thomas Deutschmann
2020-02-21  8:17       ` Luca Barbato
2020-02-21  8:28         ` Mikle Kolyada
2020-02-21  9:31       ` Michał Górny
2020-02-21  9:19     ` Michał Górny
2020-02-21  9:26       ` Luca Barbato
2020-02-21  9:38         ` Michał Górny
2020-02-21  9:43           ` Luca Barbato
2020-02-21 22:11       ` Roy Bamford
2020-02-22  5:39         ` Michał Górny
2020-02-22 19:44           ` Michael 'veremitz' Everitt
2020-02-23  6:35           ` Alec Warner
2020-02-24  7:47             ` Michał Górny
2020-02-24  8:08               ` Mikle Kolyada
2020-02-24  8:19                 ` Michał Górny [this message]
2020-02-24  8:36                   ` Mikle Kolyada
2020-02-24  8:39                     ` Michał Górny
2020-02-24  8:47                       ` Mikle Kolyada
2020-02-24  8:55                         ` Michał Górny
2020-02-24 21:04                           ` Roy Bamford
2020-02-25  1:27                             ` Matt Turner
2020-02-26 16:54                               ` William Hubbs
2020-02-26 17:18                                 ` Rich Freeman
2020-02-26 18:14                                   ` William Hubbs
2020-02-26 18:33                                     ` Rich Freeman
2020-02-26 18:56                                   ` Andreas K. Huettel
2020-02-26 18:38                                 ` Mikle Kolyada
2020-02-26 18:57                                 ` Michał Górny
2020-02-26 20:13                                   ` William Hubbs
2020-02-26 20:22                                     ` William Hubbs
2020-02-26 20:30                                       ` Michał Górny
2020-02-26 20:51                                         ` Raymond Jennings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7c54caacaed187e36b3302ccc7d8d4c435247d24.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox