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, 17 Oct 2022 16:47:31 -0400
From:   Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To:     Thorsten Leemhuis <linux@...mhuis.info>
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" <ksummit@...ts.linux.dev>
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"

On Mon, Oct 17, 2022 at 03:57:17PM +0200, Thorsten Leemhuis wrote:
> > Here's my counter-plan, which builds on top of yours.
> 
> Is this the agreed on path forward by silent agreement? And if so: who
> will actually shepherd this? I just wonder, as it sounded to me that
> Konstantin would be happy to take care of the bot-related stuff, but
> leave the rest to somebody else.

Indeed, I need to do most of the preliminary legwork. I will start by creating
a public-inbox feed of all bugzilla comments, which is something I was
planning to do for a while anyway. Once that is in place, I can build on top
of that to add a two-way bridge to replace bugzilla's native (and rather
limited, in my experience) email bridge implementation.

Once I have this in place, we can consider what next steps should be taken.

-K