<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 9/2/2012 9:17 AM, Ludovic Hirlimann wrote:<br>
<blockquote cite="mid:5043867F.3000409@mozilla.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<h1> Going Forward</h1>
<ol>
<ul>
</ul>
</ol>
<h2>I Bugzilla</h2>
<p>We need to find a process that works for both developers and
people involved in QA so that bugs get fixed.<br>
We need to fix old bugs ...<br>
</p>
</blockquote>
+1<br>
<br>
<blockquote cite="mid:5043867F.3000409@mozilla.com" type="cite">
<p>Here is the easy list of criteria we should use for bubbling up
bugs :<br>
</p>
<ol>
<li>Number of people affected (we'll probably need some input
from support for this)</li>
<li>Is it because of a new feature ?</li>
<li>Is it a main feature of the product (eg an edge case of
printing)</li>
</ol>
<p>Then we'll need a way to expose those bugs/ issues to devs and
devs will need a way to look/assign and fix these. I'm thinking
about sending a summary email on a know occurence (eg once a
month, a week , every 15 days) ?<br>
</p>
I think that once we've got a list of criteria that both devs and
contributors to quality agree , we'll just need to have more
people helping in bugzilla. <br>
<br>
Right now there are between 0 and 7 people helping at various
levels in bugzilla (some searching for duplicates, some moving to
the proper component, some asking question and trying to get more
information from our users, some closing bugs that we can't do
much with - because of lack of precise information). While I've
been trying over the last few years to grow the number of
contributors in bugzilla - I've never managed to have it grow.
People come , stay and leave except a few exceptions. So if you
have ideas on how we could manage to grow the number of people
caring with bugzilla please chime in.<br>
</blockquote>
<br>
I see a number of people who seem to engage at some level with
bugzilla and do some great work trying to narrow down issues. What I
don't frequently see is that the work they do ever gets translated
into developers actually taking on an issue and solving it - unless
the problem is associated with a new feature, or is a regression.
Old familiar bugs get no traction. I've never understood how the
existing people who do try to manage BMO keep motivated when the
result of their work is so often duping to an old, ignored problem.<br>
<br>
What I've always wanted to see is some way of empowering the BMO
managers to have some actual authority to get particular bugs
addressed. That of course is going to be even more difficult in a
volunteer-driven future.<br>
<br>
:rkent<br>
</body>
</html>