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:   Mon, 3 Oct 2022 07:18:46 -0400
From:   Slade Watkins <srw@...dewatkins.net>
To:     Thorsten Leemhuis <linux@...mhuis.info>
Cc:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        "Artem S. Tashkinov" <aros@....com>, workflows@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        ksummit@...ts.linux.dev
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"

Hi Thorsten,

> On Oct 3, 2022, at 6:10 AM, Thorsten Leemhuis <linux@...mhuis.info> wrote:
> 
> Thing is: bugzilla.kernel.org is there and will be for a while, as it
> provides services that some developers rely on. And it has some
> problems, as widely known and outlined in my mail. Reducing those for
> now by performing a few small changes (aka applying some band-aids here
> and there) as outlined above IMHO is worth it to reduce the pain. There
> was no opposition to that plan from Konstantin or core Linux kernel
> developers afaics (please correct me if I'm wrong), so I'll likely start
> working on realizing it later this week, unless I get "no, please
> don't/please wait" from those people.

With the band-aids you outline in place: do you think it would it be beneficial to have a liaison holding users’s hands through the process, _then_ triaging to developers by contacting them with the information they need? (This is something proposed previously on this thread[1], and something I’ve already said I’m willing to do[2][3].)

IOW, someone to bridge between end users and developers and (at least try to) help bring some order to the chaos.

Thanks,
-srw

[1] https://lore.kernel.org/lkml/20221002141321.394de676@rorschach.local.home/
[2] https://lore.kernel.org/lkml/DA4EA2D8-0EA0-41FF-B495-68EC9E92CC30@sladewatkins.net/
[3] https://lore.kernel.org/lkml/B0853C40-C19A-46D0-B151-84C9016745ED@sladewatkins.net/