- You are required to select a category and 'component' for your report, which
often is difficult (especially if you're not a kernel expert)
- You need to have a bugzilla account (or to create one, if you don't)
- If you want to add an address to the CC list, it must be known to bugzilla
and there's no (obvious) way to check which addresses are known (bugzilla
rejects the report if there's a 'wrong' email address in the list) [IMO this is
really really broken.]
- You are asked to provide many details that need not be relevant and casual
reporters don't know that they can skip this part
- Attaching files is tedious and referring to attachments unintuitive
That depends (please see below).
For _tracking_ bugs, the bugzilla is more-or-less suitable.
For _reporting_ bugs, IMHO, it's not.
And I think they are two _totally_ conceptually different things. You report
a bug to let somebody know that there's a problem and this doesn't necessarily
mean that the problem has to be tracked. It may be very simple and immediately
resolvable, in which case registering it in bugzilla is a loss of time and
resources. If the problem _turns_ _out_ to be difficult, _then_ it'll need to
be tracked, but usually it's not known whether or not this is the case until
someone 'in the know' looks at the initial report.
For this reason there should be a simple means of filing initial bug reports
with someone to look at them and forward them to appropriate people who will
decide if the problem needs to be tracked. If they do, it's time to use
bugzilla. Not earlier.
You are right, email is not suitable for tracking bugs. Still, it works quite
well as a means of sending initial reports.
Greetings,
Rafael
-
