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]

Message-ID: <63a8403d-b937-f870-3a9e-f92232d5306c@leemhuis.info>
Date:   Mon, 3 Oct 2022 12:10:09 +0200
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     "Artem S. Tashkinov" <aros@....com>, workflows@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Greg KH <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"

On 29.09.22 13:33, Thorsten Leemhuis wrote:
> On 29.09.22 13:19, Thorsten Leemhuis wrote:
>>
>> TLDR: Core Linux kernel developers are unhappy with the state of
>> bugzilla.kernel.org; to improve things I plan to change a few important
>> aspects of its configuration, unless somebody comes up with better ideas
>> to tackle current problems: (1) Create a catch-all product making it
>> totally obvious to submitters that likely nobody will look into the
>> ticket. (2) Remove or hide all products & components where the subsystem
>> didn't fully commit to look into newly submitted reports. (3) Change the
>> text on the front page to make it clear that most kernel bug reports
>> need to be sent by mail.

Well, there are lots of interesting things discussed in this thread for
a time when a bugzilla replacement needs to be found. But one thing
afaics is pretty clear for the time being: we as the kernel development
community are not going to double down on bugzilla now.

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.

Ciao, Thorsten