Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"

["Theodore Ts'o" <tytso@mit.edu>]

On Sat, Oct 01, 2022 at 02:57:27PM +0700, Bagas Sanjaya wrote:
> > 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.

Another critical part of the bug tracker etiquette is when in doubt,
always file a separate bug report.  More than once, both with
Launchpad or Kernel Bugzilla, users will do a web search for "my file
system lost data" or "EXT4-fs error" and assume it's the same problem
as what they are seeing.

In some cases, for a bug report that is years old and already closed.
That's actually less damaging, because it's obviously noise, and it
can be ignored.  The more annoying one is when the bug is actively
being worked, and people dog-pile onto that bug, and the bugs might be
caused by hardware issues (more often than not, a "bug report" is
really due to someone with a failing hard drive, or a USB stick which
is sticking out of the laptop, and gets jostled).  Even it's a real
software bug, if there are two bugs whose bug reports are getting
jumbled together into a single bug tracker web page, it can get
horribly confusing for the poor maintainer being asked to work the
issue, and the two users who start aguing amongst themselves about
their pet theory.

(Another bug reporter etiquette: clearly differenciate between *facts*
that you are reporting, and your pet theories about what might be
going wrong.  If you're so smart that you think you know the problem,
express your theory in the form of a patch.  Otherwise, putting
theories into a bug report which is not backed up by facts is worse
than useless.)

Of course, all of this can happy with bug reports filed by e-mail, or
via the Debian BTS.  However, it seems that people who are smart
enough to figure out how to send e-mail to a vger.kernel.org mailing
list, or how to use Debian's command-line interface "reportbug"
script, generally have enough experience that they can file a decent
bug report.  Whereas people who can only fill in a web page.... tend
not to have that (minimal) filter applied.

					- Ted