linux-kernel - Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 2 Oct 2022 21:07:13 +0000
From:   "Artem S. Tashkinov" <aros@....com>
To:     Willy Tarreau <w@....eu>
Cc:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        Theodore Ts'o <tytso@....edu>,
        Thorsten Leemhuis <linux@...mhuis.info>,
        Greg KH <gregkh@...uxfoundation.org>,
        workflows@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        ksummit@...ts.linux.dev,
        Mario Limonciello <mario.limonciello@....com>
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"

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 that
> 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=204807

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 and
>> 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