From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: comrel changes
Date: Mon, 24 Feb 2020 21:04:17 +0000 [thread overview]
Message-ID: <PF2TDTVI.QKTD6YDJ.ME35OEF3@YVLG7TNB.GUN54PEQ.E3MLKGXU> (raw)
In-Reply-To: <1c28039f9bf22ee07a473b8bfde840727db848e5.camel@gentoo.org> (from mgorny@gentoo.org on Mon Feb 24 08:55:27 2020)
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
On 2020.02.24 08:55, Michał Górny wrote:
> On Mon, 2020-02-24 at 11:47 +0300, Mikle Kolyada wrote:
> > On 24.02.2020 11:39, Michał Górny wrote:
> > > On Mon, 2020-02-24 at 11:36 +0300, Mikle Kolyada wrote:
> > > > As a result we have more busywork, this all can be conveyed to
> Council
> > > > directly. Also this is unclear to me how a review body will
> decide what
> > > > to appeal and what hot to, as the data is still being kept
> private and
> > > > reviewers are going to only have a decision on hands. Having
> only
> > > > decision is not enough to start thinking ComRel did anything
> wrong
> > > > (well, unless there were direct rules violation, which, to my
> knowledge
> > > > has never been the case).
> > > The whole point is that the review body has direct access to all
> > > the data (i.e. bugzilla privs, comrel@ alias, IRC channels).
> Unlike
> > > your 'individual' it is considered trusted and therefore you don't
> have
> > > to 'prepare' data for it.
> > >
> > Then as a result you are going to have yet another semi-closed
> process
> > which does not make the entire procedure more transparent (which was
> the
> > main concern of this thread).
> >
>
> Obviously. When you can't publish all the data, an 'independent'
> audit
> is the best you can get.
>
>
> --
> Best regards,
> Michał Górny
>
>
Team,
We are trying to define a solution before the problem(s) we want to solve
has/have been framed.
What problems, (if any), need to be addressed?
Once problems and potential solutions have been agreed then metrics
can be designed to measure the efficacy (or oherwise) of the solutions.
So what are the perceived problem(s) ?
Potential solutions and metrics are out of scope meanwhile.
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
arm64
[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-24 21:04 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
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 [this message]
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=PF2TDTVI.QKTD6YDJ.ME35OEF3@YVLG7TNB.GUN54PEQ.E3MLKGXU \
--to=neddyseagoon@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