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;
MIME-Version: 1.0
References: <aa876027-1038-3e4a-b16a-c144f674c0b0@leemhuis.info>
 <05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info> <9a2fdff8-d0d3-ebba-d344-3c1016237fe5@gmx.com>
 <YzgY9X/DM9t/ZuJe@kroah.com> <f8cbb12c-590b-28a3-e3e9-d3fb0d7e3c90@gmx.com>
 <d7798453-3105-7adf-a9a6-76e8cfe4d012@leemhuis.info> <83f6dd2b-784a-e6d3-ebaf-6ad9cfe4eefe@gmx.com>
In-Reply-To: <83f6dd2b-784a-e6d3-ebaf-6ad9cfe4eefe@gmx.com>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Sun, 2 Oct 2022 11:03:08 +0200
Message-ID: <CAMuHMdUWontzcX=ww8HbVWc2j418SdyzoPyKa4HHFsxzijbVSw@mail.gmail.com>
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"
To:     "Artem S. Tashkinov" <aros@gmx.com>
Cc:     Thorsten Leemhuis <linux@leemhuis.info>,
        Greg KH <gregkh@linuxfoundation.org>,
        Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        workflows@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        ksummit@lists.linux.dev
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Precedence: bulk

Hi Artem,

On Sat, Oct 1, 2022 at 1:21 PM Artem S. Tashkinov <aros@gmx.com> wrote:
> On 10/1/22 10:57, Thorsten Leemhuis wrote:
> > On 01.10.22 12:47, Artem S. Tashkinov wrote:
> >> On 10/1/22 10:39, Greg KH wrote:
> >>> On Sat, Oct 01, 2022 at 10:30:22AM +0000, Artem S. Tashkinov wrote:
> >
> >>>> I have a 20+ years experience in IT and some kernel issues are just
> >>>> baffling in terms of trying to understand what to do about them.
> >>>>
> >>>> Here's an example: https://bugzilla.kernel.org/show_bug.cgi?id=216274
> >>>>
> >>>> What should I do about that? Who's responsible for this? Who should I
> >>>> CC?
> >>>
> >>> Input subsystem.
> >>
> >> It's great you've replied immediately, what about hundreds or even
> >> thousands of other bug reports where people have no clue who has to be
> >> CC'ed?
> >
> > Quoting from https://docs.kernel.org/admin-guide/reporting-issues.html:
> >
> > "[...] try your best guess which kernel part might be causing the issue.
> > Check the MAINTAINERS file [...] In case tricks like these don’t bring
> > you any further, try to search the internet on how to narrow down the
> > driver or subsystem in question. And if you are unsure which it is: just
> > try your best guess, somebody will help you if you guessed poorly. [...]"
> >
> > HTH, Ciao, Thorsten
>
> Absolute most people:
>
> * Will never read this document
> * Will not be able to "search the internet on how to narrow down the
> driver or subsystem in question"

So how did these people arrive at "bugzilla" in the first place? ;-)

Or is this a case of "if all you have is a hammer...", so you
actively start looking for a bugzilla?
I.e. people who are used to bugzilla/discourse/slack/irc/trac/... will
look for how to use bugzilla/discourse/slack/irc/trac/... to interact
with the developer and/or maintainer.

The definitive guide is the MAINTAINERS file.  If there is a (rare)
corresponding "B" entry, you can use that.  Else fall back to the
"M" and "L" entries.  "C" might be good for an initial query, but not
for the actual reporting, as there's even less traceability than with
mailing lists (the latter are archived by lore).

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds