Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Mon, Jun 03, 2019 at 11:25:51AM -0600, Shuah Khan wrote:
>>>I'm interested in this topic for not just syzbot but other bug 
>>>trackers
>>>as well. Fedora gets a steady flow of bugs filed and the three official
>>>maintainers do their best to review but sometimes things slip through,
>>>especially if we hit a time when several of us are out or traveling.
>>>The kernel.org bugzilla also gets a number of bug reports that sometimes
>>>get lost. I'd love to see if there's a process that could work for syzbot
>>>and other high volume kernel trackers.
>>
>>Maybe the solution here is to standardize bug reporting bots? A
>>bugs@kernel.org mailing list which our various bots could report to with
>>a standard format that'll allow users/maintainers to easily filter it to
>>get only bugs they care about?
>>
>
>Easy to filter and manage is important for usability. I mentioned in my
>response Kees that I am finding it hard to update syzbot bug status to
>mark them as duplicate and/or fixed. The email interface is nice for
>individual bugs, but not very easy when it comes to other actions.

May I recommend using a project like git-bug [1] instead of a mailing 
list? I am increasingly worried that with mail services being 
increasingly centralized across 4-5 major providers we'll soon find it 
quite difficult to continue using mailing lists and have them reliably 
deliver mail to all participants. Heck, I've been battling with Gmail 
over the weekend due to it arbitrarily deciding that Robert Richter is 
receiving way too much mail.

Git-bug, on the other hand, is a great internal bug tracker for 
automatically generated bug reports -- it already provides the necessary 
structured platform, is decentralized, easily clonable and offline-able, 
and does not suffer from some mail provider arbitrarily deciding 
throttle its traffic for no obvious reason.

.. [1] https://github.com/MichaelMure/git-bug

-K