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]
Message-ID: <b594681b-6b8c-ffb7-f526-3da847d160a8@gmx.com>
Date:   Sun, 2 Oct 2022 19:43:19 +0000
From:   "Artem S. Tashkinov" <aros@....com>
To:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     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 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 to
> receive (or even be aware) of bug reports. Maintainers want *PATCHES*, not 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 that
> they're being inundated with spam and junk reports, and bug reporters will
> complain that they are being treated rudely (because this is how a senior
> 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-in
>> 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ