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: <20ddd12f-7277-f343-885d-b39d9ab5c2c3@gmx.com>
Date:   Sun, 2 Oct 2022 19:37:38 +0000
From:   "Artem S. Tashkinov" <aros@....com>
To:     Slade Watkins <srw@...dewatkins.net>
Cc:     Theodore Ts'o <tytso@....edu>,
        Thorsten Leemhuis <linux@...mhuis.info>,
        Greg Kroah-Hartman <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 10/2/22 14:48, Slade Watkins wrote:
> Hi,
>
>> On Oct 2, 2022, at 8:49 AM, Artem S. Tashkinov <aros@....com> wrote:
>> As I've said many times already: bugzilla must be an opt-out, not opt-in
>> experience/option.
>>
>> 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.
>
> I disagree with this in its *entirety* and I really don’t think it has any chance of moving forward.
>
> If this were to happen (and it won’t!) then developers will just send the emails to spam or some other filter because they didn’t _consent_ to being subscribed to it. And in my opinion, they’d be justified in doing that.
>
> -srw
>

It was a proposal from no one, i.e. me.

The other option will be what? To _mass email_ everyone asking them to
subscribe to bugzilla? Do you know what will happen? 2/3 of relevant
people will forget about/neglect this email, they will never sign up
even if they are willing to and we'll end up with a disfunction bugzilla
again.

It feels to me we are back to:

"Users are expected to break their necks finding random mailing lists
and sending their reports to them expecting feedback".

95% of users will just give up.

4.95% of users will not receive any feedback: the developer has been
busy with their work, life, past time, etc - "Sorry, missed your email".

Maybe 0.05% bug reports will be actually dealt with.

Again this does not work for serious collaborations requiring multiple
people over extended periods of time. It absolutely sucks in terms of
filling in the missing details.

I begin to sound like a broken record repeating what we've already
discussed to death a dozen times.

Let's deprecate bugzilla and just say "f it". That's what I hear. Great!

No responsibility, no bug reports, no fixes, welcome regressions.

I concur. This discussion has been a complete waste of time.

Regards,
Artem

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ