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: <d1f99826-2a66-c2d5-c9cd-d2fadd35eca4@gmx.com>
Date:   Sun, 2 Oct 2022 21:07:13 +0000
MIME-Version: 1.0
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"
To:     Willy Tarreau <w@1wt.eu>
Cc:     Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
        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: <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>
 <b594681b-6b8c-ffb7-f526-3da847d160a8@gmx.com>
 <20221002205430.GC22129@1wt.eu>
From:   "Artem S. Tashkinov" <aros@gmx.com>
In-Reply-To: <20221002205430.GC22129@1wt.eu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On 10/2/22 20:54, Willy Tarreau wrote:
> On Sun, Oct 02, 2022 at 07:43:19PM +0000, Artem S. Tashkinov wrote:
>> 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?
>
> Because the approach is wrong. As I explained it gives a false sense to
> the reporter that their issue is being handled while the simple fact tha=
t
> a message was sent to a person is in no way an engagement to do anything
> about it. LKML is a broadcast area. Everyone hopes someone else will
> respond and that eventually happens. When the reports are targetted, it

No, it doesn't happen. Should I open LKML and send you a hundred of
unreplied emails over the past year alone?

> puts pressure on the few developers receiving the message who know that
> it's unlikely anyone else will deal with that report.

"Pressure", "spam", I've completely lost you.

My first proposal was to let people _unsubscribe_ which takes a _minute_
if they hate this kind of workflow. And then I calculated how many
emails a particular developer may receive. In the worst case scenario
fewer than five in a week.

What a drama.


Just before I GTFO I will leave this bug report here (already posted it
here but maybe I need to do it again and again):

https://bugzilla.kernel.org/show_bug.cgi?id=3D204807

Tell me honestly how ~255 comments, and a ton of collaboration over the
span of 2.5 years can be managed using email.

>
>> This conversation alone has already seen close to three dozen emails an=
d
>> no one is complaining.
>
> Because it's easy to ignore. Try to setup this conversation in your
> favorite bug tracker and you'll feel alone discussing with yourself.
> This is a great indication that participation is much more powerful
> in the mailing list model than in the bug tracker model.

OK, let's kill the damn thing.

Let's have random emails with duplicated issues over 50+ mailing lists
no one sees, maybe some of them are replied to. Maybe 1% of them are
actually dealt with.

After all, it's all for fun despite > 95% of kernel contributions coming
from people who are really well paid working for major corporations such
as Intel and AMD.

Regards,
Artem