Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"
From:   Slade Watkins <srw@sladewatkins.net>
In-Reply-To: <63a8403d-b937-f870-3a9e-f92232d5306c@leemhuis.info>
Date:   Mon, 3 Oct 2022 07:18:46 -0400
Cc:     Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        "Artem S. Tashkinov" <aros@gmx.com>, workflows@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        ksummit@lists.linux.dev
Content-Transfer-Encoding: quoted-printable
Message-Id: <534EB870-3AAE-4986-95F3-0E9AD9FCE45B@sladewatkins.net>
References: <aa876027-1038-3e4a-b16a-c144f674c0b0@leemhuis.info>
 <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info>
 <63a8403d-b937-f870-3a9e-f92232d5306c@leemhuis.info>
To:     Thorsten Leemhuis <linux@leemhuis.info>
Precedence: bulk

Hi Thorsten,

> On Oct 3, 2022, at 6:10 AM, Thorsten Leemhuis <linux@leemhuis.info> =
wrote:
>=20
> Thing is: bugzilla.kernel.org is there and will be for a while, as it
> provides services that some developers rely on. And it has some
> problems, as widely known and outlined in my mail. Reducing those for
> now by performing a few small changes (aka applying some band-aids =
here
> and there) as outlined above IMHO is worth it to reduce the pain. =
There
> was no opposition to that plan from Konstantin or core Linux kernel
> developers afaics (please correct me if I'm wrong), so I'll likely =
start
> working on realizing it later this week, unless I get "no, please
> don't/please wait" from those people.

With the band-aids you outline in place: do you think it would it be =
beneficial to have a liaison holding users=E2=80=99s hands through the =
process, _then_ triaging to developers by contacting them with the =
information they need? (This is something proposed previously on this =
thread[1], and something I=E2=80=99ve already said I=E2=80=99m willing =
to do[2][3].)

IOW, someone to bridge between end users and developers and (at least =
try to) help bring some order to the chaos.

Thanks,
-srw

[1] =
https://lore.kernel.org/lkml/20221002141321.394de676@rorschach.local.home/=

[2] =
https://lore.kernel.org/lkml/DA4EA2D8-0EA0-41FF-B495-68EC9E92CC30@sladewat=
kins.net/
[3] =
https://lore.kernel.org/lkml/B0853C40-C19A-46D0-B151-84C9016745ED@sladewat=
kins.net/