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 19:57:40 +0200
From:   Willy Tarreau <w@....eu>
To:     "Artem S. Tashkinov" <aros@....com>
Cc:     "Theodore Ts'o" <tytso@....edu>,
        Thorsten Leemhuis <linux@...mhuis.info>,
        Greg KH <gregkh@...uxfoundation.org>,
        Konstantin Ryabitsev <konstantin@...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 Sun, Oct 02, 2022 at 12:49:04PM +0000, Artem S. Tashkinov wrote:
> The current ill-maintained semi-functional bugzilla has proven to be a
> ton more useful than random mailing lists no sane person can keep track
> of. Bug "reports", i.e. random emails are neglected and forgotten. LKML
> is the worst of them probably.

You seem to completely miss the point. There's no need for *someone* to
keep track of the whole mailing lists, these mailing lists are used daily
by thousands of people. It's a *collective* effort. What matters is that
there exists someone among these people who will deal with your request.
Do patches fall through the cracks ? Sure! And so what ? The important
ones are eventually noticed or resent, and there's no harm in sending a
"ping" once in a while. Actually I find bug trackers worse for this,
because they give the reporter the impression that their report is being
handled while many times there's noone reading at the other end due to
the amount of stuff that has to be triaged. With mailing lists, a sender
who gets no response starts to wonder whether anything wrong happened and
is more naturally going to ask if the message was properly received, thus
reviving it. It's extremely rare that nobody responds to a retry on a first
message.

> As I've said many times already: bugzilla must be an opt-out, not opt-in
> experience/option.

That's the best way to make sure those who feel annoyed by this spam will
just redirect the bug tracker's address to /dev/null and will never ever
receive any message from it anymore. That's quite a common pattern, I'm
surprised that it's even still proposed as a solution...

> Let's subscribe the past six months of developers using git commits and
> if someone doesn't like getting emails they go to the website and
> unsubscribe _once_ which takes a minute. This is a non-issue I've no
> clue why we're dwelling on it.

Maybe because you have not yourself been spammed by bots that each
require a different way to unsubscribe/unregister/reconfigure options ?

> Let's operate with some examples:
> 
> Bugzilla gets around two dozen bug reports weekly which encompass at
> most thirty emails, which equals to four emails daily on average.

That's roughly what I was getting from github when I disabled all
notifications.

> LKML alone sees up to a hundred emails _daily_.

With a difference that these ones are not necessarily *read*, they're
*scanned* by many of us before being archived via a single- or two-key
shortcut, with a particular focus only on some messages or series
(hence the importance of a good subject).

Willy