From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6211D138350 for ; Tue, 18 Feb 2020 22:54:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C8A80E0920; Tue, 18 Feb 2020 22:54:11 +0000 (UTC) Received: from smarthost03d.mail.zen.net.uk (smarthost03d.mail.zen.net.uk [212.23.1.23]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2C5D7E091F for ; Tue, 18 Feb 2020 22:54:11 +0000 (UTC) Received: from [62.3.120.142] (helo=NeddySeagoon_Static) by smarthost03d.mail.zen.net.uk with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1j4Bkn-0006yR-Ng for gentoo-project@lists.gentoo.org; Tue, 18 Feb 2020 22:54:09 +0000 Date: Tue, 18 Feb 2020 22:53:53 +0000 From: Roy Bamford Subject: Re: [gentoo-project] rfc: comrel changes To: gentoo-project@lists.gentoo.org In-Reply-To: (from mattst88@gentoo.org on Tue Feb 18 22:06:23 2020) X-Mailer: Balsa 2.5.6 Message-Id: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; protocol="application/pgp-signature"; boundary="=-VyaVFopvPZziPCWBx3PX" X-Originating-smarthost03d-IP: [62.3.120.142] Feedback-ID: 62.3.120.142 X-Archives-Salt: 123bf948-46a5-4853-8f08-60981f7435ab X-Archives-Hash: f158bd5bd7fd4c5b6e726eb7819a060c --=-VyaVFopvPZziPCWBx3PX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2020.02.18 22:06, Matt Turner wrote: > On Tue, Feb 18, 2020 at 12:13 PM Alec Warner > wrote: > > > > > > > > On Mon, Feb 17, 2020 at 8:18 AM William Hubbs > wrote: > >> > >> All, > >> > >> I realize that comrel is a thankless job, but it is an important > one > >> that helps preserve the health of the community. > >> > >> To facilitate this, I think we need to have some changes in the way > comrel > >> operates, so I would like to propose them here to see what other > folks think. > >> > >> Since comrel is a special TLP like QA, I think the comrel lead, > like > >> the qa lead, should be confirmed by the council. > >> > >> When an issue is filed with comrel, the issue should be addressed > >> within a reasonable time frame. As someone who has filed issues, I > have > >> seen them sit for months with no action taken. > >> With all respect to comrel, this is unacceptable. You have a > published > >> policy for how you will process issues, so follow it. If you don't, > it > >> is very upsetting for users/developers who reach out to you for > >> assistance, weakens your credibility, and by extension negatively > affects the > >> reputation of the entire Gentoo community. > >> > >> To promote more transparency with comrel, I would like to > >> require the comrel lead to send a report to the gentoo-project list > monthly > >> containing these statistics for the previous month: > >> > >> - number of bugs received > >> - number of bugs pending (this is for bugs that are currently in > process) > >> - number of bugs resolved by actions (such as talking to > >> developers or disciplinary action) > >> - number of bugs closed without action > >> > >> - number of mediation requests received > >> - number of mediation requests resolved > >> - number of mediation requests escalated to bugs > >> - number of mediation requests dismissed without action > >> > >> The comrel lead should be replaced if this report is not sent for > three > >> consecutive months. > >> > >> What do others think? > > > > > > I'm a little bit concerned that this addresses the symptoms instead > of the problem. Have you shared your concerns with comrel regarding > their lack of timely communication on reported issues? Do they even > share the same goals you enumerated? > > > > My strawperson argument is that: > > - (0) The council will elect some lead. > > - The lead will never write reports (or write them but stop.) > > - The lead will get removed per policy. > > - Council will elect a new lead. > > - GOTO 0 > > > > This isn't to say I dislike the concept of publishing transparency > report (I do like it) but I'm not sure a report completely solves the > problems that comrel actually faces today and I'd be interested to > learn more about > > >=20 > I've discussed it with William (and am a member of ComRel). The hope > is that transparency reports will dissuade ComRel from ignoring > reports. >=20 > I've heard from other ComRel members in favor as well, FWIW. >=20 > I think we're entirely open to suggestions. >=20 >=20 Metrics allow the current state to be measured and compared to=20 future states. They are the first step in gauging the magnatude of=20 a problem, if one exists.=20 Metrics won't help fix any problems though. Fixes require causes to be established and addressed, which in turn requires that the=20 operation of comrel be looked into somehow. --=20 Regards, Roy Bamford (Neddyseagoon) a member of elections gentoo-ops forum-mods arm64= --=-VyaVFopvPZziPCWBx3PX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEsOrcx0gZrrCMwJzo/xJODTqpeT4FAl5MawMACgkQ/xJODTqp eT51RQf/VcwzFEg/9eWK5szZ2M0W5/eAG4qYFoiAAL03w2GxOWhJ3ebZP+9KCZwV E2QAmh6vIigjK6QNahyCw8yhczzUEpuhozdx9VdbKYVqL8mMGKWQYMPST9Ittyc1 FIo9FiEl31TJz8zao/o9bCk1U279ChDxhW7ah8uuug1L/O1+jd5laQcHoWHdpJFb +Frx/oX8VJotE8xYoGu4h6hrAXTW2zHcbhjSEopmx/TdFQXqXBQnqn1WAz+YHU1n uH7EJwsIb3hN29R88FelJ+p4o7zdrnLFJ1oDFfiZjjOfqHd/x5rC0fSDxiIdGJQr t4kbns1N2FF5YMvHAogZ/MR/Fs6fmw== =ceXm -----END PGP SIGNATURE----- --=-VyaVFopvPZziPCWBx3PX--