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 23B1D138350 for ; Tue, 18 Feb 2020 22:06:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E3613E0905; Tue, 18 Feb 2020 22:06:37 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id ABFE5E08F6 for ; Tue, 18 Feb 2020 22:06:37 +0000 (UTC) Received: from mail-il1-f175.google.com (mail-il1-f175.google.com [209.85.166.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id F30AC34ED4A for ; Tue, 18 Feb 2020 22:06:36 +0000 (UTC) Received: by mail-il1-f175.google.com with SMTP id s18so18733027iln.0 for ; Tue, 18 Feb 2020 14:06:36 -0800 (PST) X-Gm-Message-State: APjAAAUgyT0SeA4/C6AF/23iIHeTBgmVYAcwN0m4iYyQaP3WcbQkK/pX 8eB8N9DdEkiNGuCRFVFWdU6XUa/IMTEtwf2DDxs= X-Google-Smtp-Source: APXvYqzfeR2bp9Gvrlmowd79oDJVqCVzn4tfc+CB/mdGhbscRc9i6O4d0g9Wl+qCDWImAX4xr0D9FuC/uHEUAPNcx50= X-Received: by 2002:a92:5cda:: with SMTP id d87mr22016238ilg.100.1582063594943; Tue, 18 Feb 2020 14:06:34 -0800 (PST) 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 References: <20200217161812.GA5969@linux1.home> In-Reply-To: From: Matt Turner Date: Tue, 18 Feb 2020 14:06:23 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-project] rfc: comrel changes To: Gentoo project list Cc: comrel Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: b691dc2a-6b8a-428c-b75d-39a59eef618b X-Archives-Hash: ce8251b4cba412d9ca8618c25640d598 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 > I've discussed it with William (and am a member of ComRel). The hope is that transparency reports will dissuade ComRel from ignoring reports. I've heard from other ComRel members in favor as well, FWIW. I think we're entirely open to suggestions.