On Tue, Jan 12, 2010 at 11:49 PM, Martin Pool <[email protected]> wrote: > 2010/1/13 Jonathan Lange <[email protected]>: >> Are you suggesting not implementing bug heat then, or are you >> suggesting having an even simpler algorithm than the one already >> given? > > Not implementing it for now. > > I think the currently specified algorithm is so greatly reduced from > the ubuntu gravity algorithm (for good reasons) that we might as well > go all the way and just make it be the unified-affects-count. That > avoids having a distinction-without-a-difference in the UI, and > perhaps would free up resources to work on affects-count bugs, which > we know would be popular with users. > > I say 'we might as well go all the way' because I'm not convinced that > having 4 dupes with one user each is meaningfully different to one bug > with 4 affected users or 4 subscribed users. > > Making the process of marking 'affects me' more rewarding, for > instance by having a list of bugs that affect me, would create better > input data. > > If the point of the general heat concept is to help you assess your > new/untriaged bugs, there are things we could do to address that head > on: for instance a directly linked page of new bugs by affected-count. > > Later on perhaps Launchpad could add per-project tag-based scoring tools. > > I think many of us would like to see Launchpad get existing features > more polished before adding new ones and this is a chance to do that. > > I am aware that bug heat has been a hot concept for years, and that > there have been offline discussions about it that I haven't seen. > Also that there is a roadmap saying this will be done and those things > have a certain inertia. Ultimately the bugs team must do what they > judge serves their users best. This is just how it seems to me.
Hi, Martin. I don't think its necessarily an either/or question -- i.e. either do bug heat, or fix these affects count bugs. See the story-bug-heat tag, which is a list of bugs we need to fix to consider bug heat finished. https://bugs.edge.launchpad.net/malone/+bugs?field.tag=story-bug-heat We are trying to do both. The affects count bugs were originally part of the Bug Q&A story, but since they've become more relevant with work on bug heat and bug Q&A is on hold until we can ensure reliable bug syncing, we've pulled over some of the affects bugs to the bug heat story tag. I've just now added the bug for having a personal affects page because you mentioned it here and it fits in nicely. Also, the hope is that bug heat will be more than just a cumulative affected users count. If it turns out to be only affected users, then we've done something wrong. The heat number will change over time, which is one difference. Also, I think subscribers and affected users are different and should be considered as such. And keep in mind, we're going with the simplest calculation possible as a first pass. We may very likely factor in status/importance or recent bug activity or any other factors as we see what the initial heat numbers look like and get feedback from users. I do think we are trying to do what serves our users best, but the bugs app has a wide range of users, often with competing interests. Cheers, deryck -- Deryck Hodge https://launchpad.net/~deryck http://www.devurandom.org/ _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
