Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 3 Apr 2023 17:45:31 -0400
From:   Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To:     workflows@vger.kernel.org, aros@gmx.com,
        linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
        tools@linux.kernel.org, linux@leemhuis.info
Subject: Introducing bugbot
Message-ID: <gmnswy45efztvcyc3xqymm52h7cdfwjz64go2wy3zyeqcqwb76@36fva4hyip4q>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Precedence: bulk

Hi, all:

Per our discussion last fall, I've been working on a bridge between bugzilla
and public-inbox, which went live in the past few days. It's still a very
early release, but it can do the following:

1. Create bugs from mailing list discussions, with full history. For example,
   it is sufficient for someone [1] to say "bugbot on" in a mailing list
   discussion to request bugbot to convert that thread into a new bug. It will
   then continue checking that thread for new messages, creating new comments
   for any added communication. This works both ways -- any comments added on
   bugzilla will be sent as follow-up messages to the original recipients.

   New bugs will be created in the Linux/Kernel component of Bugzilla, but
   they can then be reassigned to any other component. As long as they remain
   open, bugbot will continue tracking threads for new messages until either
   the bug is closed, or it has been over 30 days since any activity on the
   bug.

   [1] At this time, the From address of the person saying "bugbot on" has to
   have an account on bugzilla and be part of the "editbugs" group.

   Here's me using it to turn a thread into a bug:
   https://lore.kernel.org/lkml/CAJfuBxwomDagbdNP-Q6WvzcWsNY0Z2Lu2Yy5aZQ1d9W7Ka1_NQ@mail.gmail.com/

2. Start mailing list threads from pre-triaged bugzilla bugs. This works the
   opposite way and creates mailing list threads based on bug reports filed in
   bugzilla. The useful things here are:

   - bugbot only gets triggered on open bugs in Linux/Kernel that have the
     "bugbot" flag set to "+", which allows pre-triaging a bug before bugbot
     sends it to the mailing list
   - there is a special "cf_subsystem" field added to that component; bugbot
     will match it verbatim to the MAINTAINERS file components and will send
     mail to the M: and L: addresses for that subsystem
   - bugbot will then monitor for any updates to that thread, so any mailing
     list replies will be added as comments to the bug (thus sending a
     bugzilla mail notification to the initial author)
   - if the cf_subsystem is incorrect, it can be changed to a different
     subsystem at any time, triggering a different set of recipients on the
     next update
   - any files added in bugzilla will trigger notification sent to the list
     (but won't attach the actual files, so they don't clog everyone's mailbox
     or list archives)

   Artem, I'm not sure if you're still active with bugzilla.kernel.org, but I
   believe the cf_subsystem functionality is pretty much what you wanted so it
   was possible to bring bugs to the attention of actual subsystem
   maintainers.

   Here is a bug that was turned into a mailing list thread via cf_subsystem:
   https://bugzilla.kernel.org/show_bug.cgi?id=217293

Like I said, bugbot is very young and probably full of bugs, so it will still
see a lot of change and will likely explode a couple of times. The code behind
it is here, woefully lacking any documentation as yet:
https://git.kernel.org/pub/scm/utils/peebz/peebz.git/

At this time, I invite anyone with an account on bugzilla and "editbugs" group
membership can start using bugbot in either direction and to report any bugs
you find to the tools list.

Next features on my todo list are:

- documentation
- tracking repositories and recording when bugs are mentioned in commits
- whatever other feedback I receive

Best regards,
Konstantin