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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <591ab7d4-b283-32bf-13d8-419a5b91c365@gmx.com>
Date:   Thu, 29 Sep 2022 16:06:50 +0000
From:   "Artem S. Tashkinov" <aros@....com>
To:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     Thorsten Leemhuis <linux@...mhuis.info>, 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 9/29/22 15:31, Konstantin Ryabitsev wrote:
> On Thu, Sep 29, 2022 at 02:22:10PM +0000, Artem S. Tashkinov wrote:
>> * Delete all the components.
>> * Leave a catch-all one.
>> * Let bug reports rot because no one will ever see them. Almost just
>> like now. Don't remind me of mailing lists.
>
> This is my proposal, except also:
>
> 1. post all new bugs and comments to a public-inbox feed that people can query
>     via lore.kernel.org and tooling like lei.
>
>> Sarcasm and pain aside, Linus Torvalds himself _via Bugzilla_ has helped
>> me resolve critical issues on several occasions while my messages to
>> LKML were simply _ignored_. Think about that.
>
> In fact, he probably did this by replying to emails, not via the web
> interface.

Nope, I CC'ed him.

>
>> Mailing lists will not work for such a huge project. Period. In the
>> early 90s they worked, but we are 25 years later with millions more
>> users. With a ton more of a ton more complicated hardware.
>
> We've recognized this a while ago, which is why our efforts have been targeted
> at query-based message feeds. Hence, tools like lore.kernel.org and lei. It's
> a work in progress, for sure, but it doesn't require any "everyone must switch
> workflows today" kind of coordination, and avoids introducing single points of
> failure by making it easy to replicate everything to mirrored systems.
>
> -K