From: "Bird, Tim" <Tim.Bird@sony.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Thorsten Leemhuis <linux@leemhuis.info>
Cc: Slade Watkins <srw@sladewatkins.net>,
"Artem S. Tashkinov" <aros@gmx.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: RE: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"
Date: Fri, 30 Sep 2022 16:19:56 +0000 [thread overview]
Message-ID: <BYAPR13MB250377AAFCC43AC34E244795FD569@BYAPR13MB2503.namprd13.prod.outlook.com> (raw)
In-Reply-To: <Yzbtuz6L1jlDCf9/@pendragon.ideasonboard.com>
> -----Original Message-----
> From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> Hi Thorsten,
>
> On Fri, Sep 30, 2022 at 11:35:16AM +0200, Thorsten Leemhuis wrote:
> > On 29.09.22 18:42, Laurent Pinchart wrote:
> > > On Thu, Sep 29, 2022 at 10:54:17AM -0400, Slade Watkins wrote:
> > >>> On Sep 29, 2022, at 10:22 AM, Artem S. Tashkinov <aros@gmx.com> wrote:
> > >>>
> > >>> I've mentioned several times already that mailing lists are _even worse_
> > >>> in terms of reporting issues. Developers get emails and simply ignore
> > >>> them (for a multitude of reasons).
> > >>
> > >> It’s 100% true that emails get _buried_ as waves of them come in (LKML
> > >> itself gets hundreds upon hundreds a day, as I’m sure all of you know)
> > >> and it just isn’t something I personally see as viable, especially for
> > >> issues that may or may not be high priority.
> > >
> > > E-mails are not that bad to report issues, but they can't provide the
> > > core feature that any bug tracker oughts to have: tracking. There's no
> > > way, with the tools we have at the moment (including public-inbox, b4
> > > and lei), to track the status of bug reports and fixes.
> >
> > Well, I'd disagree partially with that, as my regression tracking bot
> > "regzbot"
> > (https://urldefense.com/v3/__https://gitlab.com/knurd42/regzbot/-
> /blob/main/docs/getting_started.md__;!!JmoZiZGBv3RvKRSx!7f8O2QaGyWgxASwg1_bxsV53uWPINzzBa_MLMZMooa6qL6jdk8ZBVYrB_
> mypjw0H3yv5IPdNJ2qQThzMLKbrOUQMFMO1x2V2$
> > ; https://urldefense.com/v3/__https://linux-
> regtracking.leemhuis.info/regzbot/mainline/__;!!JmoZiZGBv3RvKRSx!7f8O2QaGyWgxASwg1_bxsV53uWPINzzBa_MLMZMooa6qL6jdk8Z
> BVYrB_mypjw0H3yv5IPdNJ2qQThzMLKbrOUQMFKROzSJY$ ) does
> > exactly does that: tracking, by connect the dots (e.g. monitoring
> > replies to a report as well recording when patches are posted or
> > committed that link to the report using Link: tags), while making sure
> > nothing important is forgotten. But sure, it's still very rough and
> > definitely not a full bug-tracker (my goal is/was to not create yet
> > another one) and needs quite a bit of hand holding from my side. And I
> > only use it for regressions and not for bugs (on purpose).
>
> Patchwork does something similar for patches, and I agree that it would
> be possible to use e-mail to manage and track bug reports with tools on
> top (and don't worry, I'm not asking for regzbot to be turned into a bug
> tracker :-)). It however has to rely on lots of heuristics at the
> moment, as the data we exchange over e-mail is free-formed and lacks
> structure. I've been dreaming of support for structured data in e-mails,
> but that's a pipe dream really.
E-mails sent from a web interface could have as much structure as you'd like.
So one avenue would be to set up a nice interface for bug reporting, that just
delivered the form data in e-mail format to the proposed bug-receiving mail list.
Also, if an e-mail receiver (something automated) gave a quick response on missing fields, I think
you could quickly train users (even first-time bug submitters) to provide required
data, even if they're sending from a free-form e-mail client.
Just my 2 cents.
-- Tim
next prev parent reply other threads:[~2022-09-30 16:20 UTC|newest]
Thread overview: 165+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 11:19 Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" Thorsten Leemhuis
2022-09-29 11:33 ` Thorsten Leemhuis
2022-09-29 12:22 ` Artem S. Tashkinov
2022-09-29 12:52 ` Greg KH
2022-09-29 13:09 ` Artem S. Tashkinov
2022-09-29 13:21 ` Greg KH
2022-09-29 13:23 ` Konstantin Ryabitsev
2022-09-29 13:04 ` Konstantin Ryabitsev
2022-09-29 13:31 ` Artem S. Tashkinov
2022-09-29 13:43 ` Greg KH
2022-09-29 13:53 ` Konstantin Ryabitsev
2022-09-29 14:22 ` Artem S. Tashkinov
2022-09-29 14:54 ` Slade Watkins
2022-09-29 16:42 ` Laurent Pinchart
2022-09-29 19:00 ` Slade Watkins
2022-09-30 9:35 ` Thorsten Leemhuis
2022-09-30 13:23 ` Laurent Pinchart
2022-09-30 16:19 ` Bird, Tim [this message]
2022-09-30 16:34 ` Artem S. Tashkinov
2022-09-30 16:47 ` Laurent Pinchart
2022-10-01 1:18 ` Theodore Ts'o
2022-10-01 2:47 ` Slade Watkins
2022-10-01 7:57 ` Bagas Sanjaya
2022-10-01 13:01 ` Theodore Ts'o
2022-10-03 6:55 ` Christoph Hellwig
2022-09-30 17:36 ` Slade Watkins
2022-09-30 16:36 ` Laurent Pinchart
2022-09-30 17:28 ` Luck, Tony
2022-09-30 17:49 ` Slade Watkins
2022-09-30 20:04 ` Randy Dunlap
2022-09-30 20:29 ` Thorsten Leemhuis
2022-09-29 15:31 ` Konstantin Ryabitsev
2022-09-29 15:39 ` Slade Watkins
2022-09-29 16:06 ` Artem S. Tashkinov
2022-09-29 20:26 ` Slade Watkins
2022-09-30 8:47 ` Thorsten Leemhuis
2022-09-30 9:03 ` Artem S. Tashkinov
2022-09-30 10:37 ` Slade Watkins
2022-09-30 15:32 ` Laurent Pinchart
2022-10-03 11:44 ` Jani Nikula
2022-09-29 15:26 ` James Bottomley
2022-09-30 8:52 ` Artem S. Tashkinov
2022-09-29 13:47 ` Steven Rostedt
2022-09-29 14:02 ` Thorsten Leemhuis
2022-09-29 14:12 ` Steven Rostedt
2022-10-01 10:30 ` Artem S. Tashkinov
2022-10-01 10:39 ` Greg KH
2022-10-01 10:47 ` Artem S. Tashkinov
2022-10-01 10:57 ` Thorsten Leemhuis
2022-10-01 11:21 ` Artem S. Tashkinov
2022-10-01 11:34 ` Thorsten Leemhuis
2022-10-01 13:07 ` Theodore Ts'o
2022-10-01 14:58 ` Artem S. Tashkinov
2022-10-02 12:18 ` Theodore Ts'o
2022-10-02 12:49 ` Artem S. Tashkinov
2022-10-02 14:35 ` Greg KH
2022-10-02 19:27 ` Artem S. Tashkinov
2022-10-02 20:46 ` Linus Torvalds
2022-10-02 20:56 ` Artem S. Tashkinov
2022-10-02 21:07 ` Linus Torvalds
2022-10-02 21:27 ` Artem S. Tashkinov
2022-10-02 21:40 ` Willy Tarreau
2022-10-02 21:57 ` Artem S. Tashkinov
2022-10-02 14:48 ` Slade Watkins
2022-10-02 19:37 ` Artem S. Tashkinov
2022-10-02 21:11 ` Laurent Pinchart
2022-10-02 21:38 ` Artem S. Tashkinov
2022-10-02 15:05 ` Konstantin Ryabitsev
2022-10-02 19:43 ` Artem S. Tashkinov
2022-10-02 20:54 ` Willy Tarreau
2022-10-02 21:07 ` Artem S. Tashkinov
2022-10-02 21:32 ` Willy Tarreau
2022-10-02 21:53 ` Artem S. Tashkinov
2022-10-03 6:37 ` Geert Uytterhoeven
2022-10-03 7:49 ` Artem S. Tashkinov
2022-10-03 10:04 ` Willy Tarreau
2022-10-02 15:56 ` Al Viro
2022-10-02 17:22 ` Slade Watkins
2022-10-02 16:08 ` Geert Uytterhoeven
2022-10-02 16:10 ` Geert Uytterhoeven
2022-10-02 16:32 ` Joe Perches
2022-10-02 18:56 ` Joe Perches
2022-10-02 19:46 ` Artem S. Tashkinov
2022-10-02 17:57 ` Willy Tarreau
2022-10-02 19:55 ` Artem S. Tashkinov
2022-10-02 20:40 ` Willy Tarreau
2022-10-02 18:13 ` Steven Rostedt
2022-10-02 20:14 ` Artem S. Tashkinov
2022-10-02 22:08 ` Steven Rostedt
2022-10-02 22:20 ` Artem S. Tashkinov
2022-10-02 22:28 ` Steven Rostedt
2022-10-02 23:04 ` Al Viro
2022-10-02 23:21 ` Steven Rostedt
2022-10-03 7:41 ` Artem S. Tashkinov
2022-10-03 8:55 ` Mike Rapoport
2022-10-03 9:15 ` David Laight
2022-10-03 9:16 ` Artem S. Tashkinov
2022-10-03 9:26 ` Geert Uytterhoeven
2022-10-03 9:40 ` Artem S. Tashkinov
2022-10-03 10:26 ` Mike Rapoport
2022-10-03 14:20 ` Steven Rostedt
2022-10-03 18:24 ` Al Viro
2022-10-03 19:07 ` Steven Rostedt
2022-10-03 20:28 ` Slade Watkins
2022-10-04 12:16 ` Artem S. Tashkinov
2022-10-04 12:32 ` Geert Uytterhoeven
2022-10-04 22:45 ` Steven Rostedt
2022-10-03 14:22 ` Konstantin Ryabitsev
2022-10-04 12:21 ` Artem S. Tashkinov
2022-10-04 14:20 ` Konstantin Ryabitsev
2022-10-06 10:46 ` Artem S. Tashkinov
2022-10-06 19:29 ` Greg KH
2022-10-03 15:37 ` Konstantin Ryabitsev
2022-10-04 7:37 ` Thorsten Leemhuis
2022-10-04 7:56 ` Conor Dooley
2022-10-04 12:24 ` Artem S. Tashkinov
2022-10-04 14:48 ` Konstantin Ryabitsev
2022-10-02 20:41 ` Slade Watkins
2022-10-02 20:52 ` Slade Watkins
2022-10-02 21:06 ` Laurent Pinchart
2022-10-02 22:18 ` Steven Rostedt
2022-10-02 22:41 ` Laurent Pinchart
2022-10-02 23:59 ` Slade Watkins
2022-10-02 18:17 ` Geert Uytterhoeven
2022-10-02 20:17 ` Artem S. Tashkinov
2022-10-02 20:48 ` Willy Tarreau
2022-10-02 19:59 ` Laurent Pinchart
2022-10-02 20:19 ` Artem S. Tashkinov
2022-10-02 20:26 ` Laurent Pinchart
2022-10-02 13:25 ` Slade Watkins
2022-10-02 9:03 ` Geert Uytterhoeven
2022-10-02 9:06 ` Artem S. Tashkinov
2022-10-02 9:25 ` Geert Uytterhoeven
2022-10-02 7:37 ` Takashi Iwai
2022-10-02 8:23 ` Artem S. Tashkinov
2022-10-02 8:53 ` Geert Uytterhoeven
2022-10-02 9:14 ` Takashi Iwai
2022-10-03 10:10 ` Thorsten Leemhuis
2022-10-03 11:18 ` Slade Watkins
2022-10-03 12:59 ` Thorsten Leemhuis
2022-10-03 15:26 ` Steven Rostedt
2022-10-03 15:44 ` Laurent Pinchart
2022-10-03 15:51 ` Steven Rostedt
2022-10-03 15:59 ` Laurent Pinchart
2022-10-03 16:03 ` Steven Rostedt
2022-10-04 8:41 ` Thorsten Leemhuis
2022-10-04 9:20 ` Geert Uytterhoeven
2022-10-04 10:16 ` Thorsten Leemhuis
2022-10-04 10:45 ` Geert Uytterhoeven
2022-10-04 17:53 ` Konstantin Ryabitsev
2022-10-04 18:02 ` Greg KH
2022-10-04 18:13 ` Konstantin Ryabitsev
2022-10-04 18:03 ` Linus Torvalds
2022-10-04 18:11 ` Konstantin Ryabitsev
2022-10-04 19:21 ` Jani Nikula
2022-10-04 19:24 ` Konstantin Ryabitsev
2022-10-04 20:06 ` Thorsten Leemhuis
2022-10-04 20:25 ` Konstantin Ryabitsev
2022-10-05 9:00 ` Thorsten Leemhuis
2022-10-05 9:57 ` Hans de Goede
2022-10-12 16:12 ` Thorsten Leemhuis
2022-10-06 7:56 ` Artem S. Tashkinov
2022-10-17 13:57 ` Thorsten Leemhuis
2022-10-17 20:47 ` Konstantin Ryabitsev
2022-10-18 16:24 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR13MB250377AAFCC43AC34E244795FD569@BYAPR13MB2503.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=aros@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=srw@sladewatkins.net \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).