launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-11-15 10:46 AM, curtis Hovey wrote:
> On 11/15/2011 09:29 AM, Aaron Bentley wrote:
>> On 11-11-15 08:41 AM, curtis Hovey wrote:

>>> As a member of ~launchpad when I visit 
>>> <https://bugs.launchpad.net/launchpad>, I see 3 community
>>> driven bugs and 7 private bugs. When a member of the community
>>> looks at the list, 10 community bugs are shown. One might ask
>>> why isn't ~launchpad working on the ten hottest bugs?
>> 
>> Wouldn't we have the same issue if we were sorting on importance,
>> but all the critical bugs were private?
> 
> No. The 10 hottest bugs implies these are the 10 things that need 
> working on. A listing of all bugs is more forgiving since the users
> can see the bugs that are also competing for attention.

That seems like a good argument against listing only 10, but I don't
see how it relates to ordering by heat.  A listing of the top 10 most
important bugs would also seem to be the 10 things that need working on.

> We also need to consider that bug heat is broken, and we have
> failed to tune it after we thought we finished work with it. I know
> bug heat does not decay as we intended because trivial bug actions
> keep the bug hot. Bugs really cannot fall off the list because they
> cool.

Right, so ideally we'd fix it or ditch it.

I'd prefer to fix it.  I think we should strive to capture user
impact, because that's often disjoint from the importance assigned by
the project.

It would be interesting to feed our bug data into some sort of
computer learning system and see what it predicted would get fixed and
how.

> Privacy's heat scoring is ridiculous, it supposes some
> gestalt-like importance because there is a secret.

Ah, so privacy's effect on heat means that the public list will rarely
match the private one.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7Cl0oACgkQ0F+nu1YWqI0OSgCfZakqdSm/RjwBcCsaeXAYH+7S
mpcAn1RBUDF74t7li5NjT7J6NQZfCrSD
=4GzA
-----END PGP SIGNATURE-----