[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yzfy5wXuU0uxdIqr@debian.me>
Date: Sat, 1 Oct 2022 14:57:27 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Theodore Ts'o <tytso@....edu>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
"Artem S. Tashkinov" <aros@....com>,
"Bird, Tim" <Tim.Bird@...y.com>,
Thorsten Leemhuis <linux@...mhuis.info>,
Slade Watkins <srw@...dewatkins.net>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
"workflows@...r.kernel.org" <workflows@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <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 Fri, Sep 30, 2022 at 09:18:13PM -0400, Theodore Ts'o wrote:
> On Fri, Sep 30, 2022 at 07:47:26PM +0300, Laurent Pinchart wrote:
> > > Debian uses an email based bug tracker and you know what? Most people
> > > avoid it like a plague. It's a hell on earth to use. Ubunutu's Launchpad
> > > which looks and feels like Bugzilla is a hundred times more popular.
> >
> > It would be pretty sad if the only options we could come up with for bug
> > tracking would be either popular with reporters and ignored by
> > maintainers, or the other way around. Ideally we wouldn't have to decide
> > which of those two classes of users to prioritize, but I fear that,
> > given resource starvation, we'll have to make a decision there that will
> > be unpopular with one of the two sides.
>
> Funny thing. I've largely given up on getting any kind of useful bug
> report from Launchpad, so I've largely ignored it. In contast, the
> bug reports I get for e2fsprogs from Debian are generally far more
> actionable, with bug reports that have all of the data so I can
> actually root cause the problem, and help the user.
>
So no matter how the bug tracker interface is, the etiquette is:
Whenever something buggy happens, try to gather all information related
to that event (reproduction steps and reproducer, logs, crash dumps,
etc), then file the polished report. From your experience, it seems like
Debian people knows it.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists