** Description changed: - The Ubuntu Bug Reporting system uses a heat metric to identify which bugs are gaining the most attention. - By default 6 individuals appear to be sent notifications about any bug. - The system marks all bugs with 6 or more reads(?) with a flaming icon, meaning 'hot'. - That means every bug filed is hot. + The Ubuntu Bug Reporting system uses a heat metric to identify which + bugs are gaining the most attention. - That is silly. + It seems every bug is given the flaming hot icon. + That seems unhelpful to me, though perhaps its the metric not the icon that counts. - Please reconsider how the 'hot' icon and metric is used. + I suggest a bit more sophistication in how this is managed. + + Shooting from the hip, I'd say the flaming hot icon should only appear + next to bug that are receiving a fair amount of attention from either + the community at large, the developers, or Canonical management. + + Possible contributors to the heat metric: + + Areas Affecting Bug Heat: + - Community Engagement + - # of repeat bugs filed (already done) + - # of affected users reported (already done) + - # of alert subscribers from community (already done) + - comments made by separate community members + + - Developer Engagement + - # of separate developers submitting comments to a bug + - # of alert subscribers from development community + - # of developers assigned + - Importance (Severity + Priority) + - Sensitivity: is bug marked private (already done) + + - Canonical Management Engagement + (limited scope: metric additions visible to developers only?) + + - some ability for management to affect bug heat + - this might annoy development community [heh] but it would raise management engagement in the bug process. Is it worth it? [shrug] + + A single icon could still be used, but I think having multiple colors + could be helpful. A smoldering bit of kindling for bugs with limited + heat would be amusing, too. + + Increased calculations for this bug heat metric could add considerable + effectiveness to bugs relative visibility, making the development + community more efficient & productive. Increasing management engagement + MIGHT be helpful across a few plains. Currently, sorting by bug heat + gives a list that seems only meaningful for the bugs with the greatest + heat metric.
** Description changed: The Ubuntu Bug Reporting system uses a heat metric to identify which bugs are gaining the most attention. It seems every bug is given the flaming hot icon. That seems unhelpful to me, though perhaps its the metric not the icon that counts. I suggest a bit more sophistication in how this is managed. Shooting from the hip, I'd say the flaming hot icon should only appear next to bug that are receiving a fair amount of attention from either the community at large, the developers, or Canonical management. Possible contributors to the heat metric: Areas Affecting Bug Heat: - Community Engagement - - # of repeat bugs filed (already done) - - # of affected users reported (already done) - - # of alert subscribers from community (already done) - - comments made by separate community members + - # of repeat bugs filed (already done) + - # of affected users reported (already done) + - # of alert subscribers from community (already done) + - comments made by separate community members - - Developer Engagement - - # of separate developers submitting comments to a bug - - # of alert subscribers from development community - - # of developers assigned - - Importance (Severity + Priority) - - Sensitivity: is bug marked private (already done) + - Developer Engagement + - # of separate developers submitting comments to a bug + - # of alert subscribers from development community + - # of developers assigned + - Importance (Severity + Priority) + - Sensitivity: is bug marked private (already done) - - Canonical Management Engagement + - Canonical Management Engagement (limited scope: metric additions visible to developers only?) - - some ability for management to affect bug heat - - this might annoy development community [heh] but it would raise management engagement in the bug process. Is it worth it? [shrug] + - some ability for management to affect bug heat + - this might annoy development community [heh] but it would raise management engagement in the bug process. Is it worth it? [shrug] A single icon could still be used, but I think having multiple colors could be helpful. A smoldering bit of kindling for bugs with limited - heat would be amusing, too. + heat would be amusing, too. Just no icon at all probably makes more + sense. Increased calculations for this bug heat metric could add considerable effectiveness to bugs relative visibility, making the development community more efficient & productive. Increasing management engagement MIGHT be helpful across a few plains. Currently, sorting by bug heat gives a list that seems only meaningful for the bugs with the greatest heat metric. ** Summary changed: - Ubuntu Bug Reporting 'heat' metric is flawed + Ubuntu Bug Reporting 'heat' metric is arguably too simplistic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167135 Title: Ubuntu Bug Reporting 'heat' metric is arguably too simplistic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2167135/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
