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;
Message-ID: <b594681b-6b8c-ffb7-f526-3da847d160a8@gmx.com>
Date:   Sun, 2 Oct 2022 19:43:19 +0000
MIME-Version: 1.0
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"
To:     Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc:     Theodore Ts'o <tytso@mit.edu>,
        Thorsten Leemhuis <linux@leemhuis.info>,
        Greg KH <gregkh@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,
        Mario Limonciello <mario.limonciello@amd.com>
References: <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>
 <a676e5cf-c67b-7946-ce73-8fb8d63a5a0a@leemhuis.info>
 <Yzg7pHspc72I7TAb@mit.edu> <e98597e8-9ddb-bbf0-7652-691327186a92@gmx.com>
 <YzmBjgXq9geMnL1B@mit.edu> <79bb605a-dab8-972d-aa4a-a5e5ee49387c@gmx.com>
 <20221002150522.ul4nbtfawqjhnsag@meerkat.local>
From:   "Artem S. Tashkinov" <aros@gmx.com>
In-Reply-To: <20221002150522.ul4nbtfawqjhnsag@meerkat.local>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On 10/2/22 15:05, Konstantin Ryabitsev wrote:
> On Sun, Oct 02, 2022 at 12:49:04PM +0000, Artem S. Tashkinov wrote:
>> I've mentioned it a dozen times already - you're unhappy with emails
>> from bugzilla? Go there and unsubscribe. It takes a minute and we're
>> talking as if it's the actual issue we are dealing with. It's not.
>> Bugzilla maintenance and its up-to-date status are the issues.
>
> I think you're working from the wrong conception that maintainers want t=
o
> receive (or even be aware) of bug reports. Maintainers want *PATCHES*, n=
ot bug
> reports. You're asking senior engineers to do first-line QA.
>
> This is why your suggestion to auto-subscribe maintainers to bug reports=
 is
> the absolutely wrong way to go about it. The maintainers will complain t=
hat
> they're being inundated with spam and junk reports, and bug reporters wi=
ll
> complain that they are being treated rudely (because this is how a senio=
r
> engineer trying to get succinct information comes across). You know that=
 meme
> from Fallout with the words "[Everyone hated that]" on it?

There's no need to exaggerate or say words like "inundated", please
refer to my previous emails about bugzilla stats.

Again, to remind everyone, bugzilla sees around ~20 bug reports
_weekly_. There are hundreds of active of kernel developers. That means
for a single bug report maybe a couple of people will receive maybe a
few emails per week.

Is this really an _issue_?

Why are people are now blowing stuff out of proportion for no reason?
This conversation alone has already seen close to three dozen emails and
no one is complaining.

>
>>> And if we force developers to get Bugzilla spam whether they want it
>>> not, and they said, "absolutely not", is it there right to have the
>>> mailing list gateway disabled --- and if so, what does that do to the
>>> user experience?  Thats basically the situation we have right now.
>>
>> As I've said many times already: bugzilla must be an opt-out, not opt-i=
n
>> experience/option.
>
> Please listen to the actual maintainers telling you that this won't work=
 and
> will just lead to bugzilla being added to everyone's block list (that's =
even
> faster than logging in to bugzilla, finding where to change the default
> assignee, etc).

It feels to me there are no actual maintainers here. Just random people
who oppose to a imaginary torrent of emails they've never actually seen.

At the same time everyone here is OK getting a hundred emails from LKML
_daily_.

Regards,
Artem