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: <95c3384b-53d0-fd6c-6ec5-a7e03fdeddfc@gmx.com>
Date:   Thu, 29 Sep 2022 10:54:17 -0400
Cc:     Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        Thorsten Leemhuis <linux@leemhuis.info>,
        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: <F300ED64-5E8E-4060-89DC-C98BC5FF08E6@sladewatkins.net>
References: <aa876027-1038-3e4a-b16a-c144f674c0b0@leemhuis.info>
 <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info>
 <93a37d72-9a88-2eec-5125-9db3d67f5b65@gmx.com>
 <20220929130410.hxtmwmoogzkwcey7@meerkat.local>
 <7b427b41-9446-063d-3161-e43eb2e353f9@gmx.com>
 <20220929135325.4riz4ijva2vc7q5p@meerkat.local>
 <95c3384b-53d0-fd6c-6ec5-a7e03fdeddfc@gmx.com>
To:     "Artem S. Tashkinov" <aros@gmx.com>
Precedence: bulk

Hey!

Jumping in here to offer my input...

> On Sep 29, 2022, at 10:22 AM, Artem S. Tashkinov <aros@gmx.com> wrote:
>=20
> That leaves us with Bugzilla that no one wants to touch and some =
people
> actively want to delete altogether. In other words, no central place =
to
> report bugs or keep track of them.

This is the current problem that seems to be appearing here. I get why =
no one wants to touch it, but it doesn=E2=80=99t solve the problem.=20

As you said:

> I've mentioned several times already that mailing lists are _even =
worse_
> in terms of reporting issues. Developers get emails and simply ignore
> them (for a multitude of reasons).

It=E2=80=99s 100% true that emails get _buried_ as waves of them come in =
(LKML itself gets hundreds upon hundreds a day, as I=E2=80=99m sure all =
of you know) and it just isn=E2=80=99t something I personally see as =
viable, especially for issues that may or may not be high priority.

> Getting back to my first message in this discussion,
>=20
> * Let's refresh all the components in Bugzilla
> * Components may not have any people responsible for them at all. Bug
> reporters will have to CC the people they are interested in.
> * Let's subscribe the past six months of developers (using git commit =
logs)
> * Whoever wants to unsubscribe is free to do so.

Not a terrible idea to me, though obviously, that=E2=80=99s up for =
debate.

>=20
> If not for bugzilla, let's use something more modern. I don't know any
> comparable projects however. Trac is truly horrible. You cannot even
> unsubscribe from bug reports. Maybe I've missed something. Discourse?
> Not a bug tracker per se but can certainly work this way.

Discourse probably isn=E2=80=99t the best fit here, in my opinion. Jira =
and YouTrack are the only ones I personally know of that are similar to =
Bugzilla, although as far as I know, they aren=E2=80=99t open source...

Best,
-srw