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 53921138350 for ; Tue, 18 Feb 2020 20:13:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E237AE0878; Tue, 18 Feb 2020 20:13:11 +0000 (UTC) Received: from mail-yw1-xc36.google.com (mail-yw1-xc36.google.com [IPv6:2607:f8b0:4864:20::c36]) (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 B7D73E0872 for ; Tue, 18 Feb 2020 20:13:11 +0000 (UTC) Received: by mail-yw1-xc36.google.com with SMTP id 10so9998901ywv.5 for ; Tue, 18 Feb 2020 12:13:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gentoo-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XdmME04QMM9bZj867eEWoB4p0CBGEpIk/7g1kqkXHgM=; b=e1tmgBys0bJxhnXt6ZXKkoqb1uEEeXwe2gj9jR2tsWXgNMSiE75QlGQ0X+KczcARkk Ua3J/TOoJJY+DIxazBG4kAZbnHgJ5mgsAVlUNznOHHIm5K4lKzh9WlLnUkgweyMcrSw/ 2TXhRPbnbGBsgt1FB3EDWsQNhvtmtRPc4IEQNf9NVu/7taHDH7u9HDzp+DC01I9D+7M0 98uOOiK/FK80JgRsrQ35ACfuIMyBSkk4r5YNWH3qVTVZnWqtOQ8qPhMKDrcBhn5m5/un WwdHr3CHwJGbOomjpt2gWITNLMLLqsXEMSGMD/S49DHVaD7ohr2U73cYi2Pwvkw2ixZW +NHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=XdmME04QMM9bZj867eEWoB4p0CBGEpIk/7g1kqkXHgM=; b=REGSAjHz6M8+U0H+i1NCHpUhAj0xFY9u0HTDkX/puyy/TZpI+cZcm5DvSbC2eDAOiI cJ7mm1qiwy6NQn3Pfg+azyOjjk1gtWl3H912roK/gx5dV8BslBhYdN6I3KUC4XT7GMir +93UKPDVvxkyw1eXqJxWijgpZiZrCVMdyb/zdRbydRG2zNCF4CQrS9Yab1zToOfm4+RA IUy3wB4T3F2Tg4vbsvvxLO6vKPmxdBNQVtmQ/uknCqu+FmeLTE3FFxyw0KYNh3O/znIl PNZHMHXQyT3eRAWVL3fXpApQKZkHJy/YF/Kz5r1pHHPKeJP3HuWc2AJBXV3xhk+h8p/E W2Lg== X-Gm-Message-State: APjAAAV03PbwfkyT7Is4UGhD37nvyMhO/LhBT98H9c38FAQeUsMEUf78 POPKE2GacYmZ7aGpwq+uTXXnrjds/JDYxsDySKSQpQTO X-Google-Smtp-Source: APXvYqzaNg4wBCK8yVeiWjoJYuG/+TYzwaeLSgpYdF5e8wmF5CHsRL3AGw6qsLdHIoFAsUHZBF3cNJYpgYUaY00BHBw= X-Received: by 2002:a0d:d84b:: with SMTP id a72mr18174587ywe.33.1582056790407; Tue, 18 Feb 2020 12:13:10 -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: <20200217161812.GA5969@linux1.home> From: Alec Warner Date: Tue, 18 Feb 2020 12:12:59 -0800 Message-ID: Subject: Re: [gentoo-project] rfc: comrel changes To: gentoo-project , comrel Content-Type: multipart/alternative; boundary="00000000000001d4b8059edf4d1c" X-Archives-Salt: 83788aa2-2afc-4cfa-bba4-36ba65a4e938 X-Archives-Hash: 255c509980c837975725d91616d79705 --00000000000001d4b8059edf4d1c Content-Type: text/plain; charset="UTF-8" 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 -A > > Thanks, > > William > > --00000000000001d4b8059edf4d1c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Feb 17, 2020 at 8:18 AM Willi= am Hubbs <williamh@gentoo.org= > 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<= br> operates, so I would like to propose them here to see what other folks thin= k.

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<= br> is very upsetting for users/developers who reach out to you for
assistance, weakens your credibility, and by extension negatively affects t= he
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
=C2=A0 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 commun= ication on reported issues? Do they even share the same goals you enumerate= d?

My strawperson argument is that:
=C2= =A0- (0) The council will elect some lead.
=C2=A0- The lead will = never write reports (or write them but stop.)
=C2=A0- The lead wi= ll get removed per policy.
=C2=A0- Council will elect a new lead.=
=C2=A0- GOTO 0

This isn't to say I = dislike the concept of publishing transparency report (I do like it) but I&= #39;m not sure a report completely solves the problems that comrel actually= faces today and I'd be interested to learn more about=C2=A0
=
-A
=C2=A0

Thanks,

William

--00000000000001d4b8059edf4d1c--