From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bug voting
Date: Tue, 27 Jul 2004 13:17:42 -0500 [thread overview]
Message-ID: <1090952262.1538.67.camel@6-allhosts> (raw)
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
Pardon to those who're on -core, since I fired it off to core when the
thread is in -dev :)
On Tue, 2004-07-27 at 12:04, Ciaran McCreesh wrote:
> On Tue, 27 Jul 2004 12:54:49 -0400 Dylan Carlson <absinthe@gentoo.org>
> wrote:
> | 1. Without bug voting, there's no way to determine what bugs are
most
> | important to the public (or at least to the people using Bugzilla,
> | which is really *our* public, in a working sense).
I'm not sure if users will use it sanely/sparingly, but this does seem
like a decent way to A) gain feedback on actual user priority, B) get
people to stop fooling w/ priorities, and posting semi-demanding
commentary asking asking why it is their their xyz feature they want
hasn't been implemented.
I like the notion of being able to gauge what is important to our users-
this option would likely be worthless for actual bugs, but enhancement
requests it would rock for.
> Well, given that most of our users don't seem to be able to get the
> priority field straight ("Waah! There's a tiny typo in an einfo
> statement! BLOCKER!"), I'd be kind of sceptical about an easily rigged
> popularity contest. I suspect we'd just end up seeing thousands of
votes
> for "add more pictures to bootsplash" and "add this horribly broken
> kernel patch to g-d-s"...
It's a feedback system, just that. What you're pointing out above w/
the priority is tied to a single user incorrectly estimating the level
of borkage, which is kind of odd anyways- the dev looking into the
problem probably is well aware of the severity of the bug.
Personally I've always wondered why general users could fiddle w/
priority settings.
Either way, back to the bug voting issues, keep in mind if we turn this
on, and it ends up being abused/not incredibly useful, we *can* just
turn the dumb thing off. Aside from time involved in setup (and
potentially disabling), there isn't a heck of a lot lost by trying.
Right?
~brian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-07-27 18:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 18:17 Brian Harring [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 16:54 [gentoo-dev] Bug voting Dylan Carlson
2004-07-27 17:04 ` Ciaran McCreesh
2004-07-27 17:21 ` Chris Bainbridge
2004-07-27 17:27 ` Dylan Carlson
2004-07-27 17:39 ` Peter Johanson
2004-07-27 17:54 ` Olivier Crete
2004-07-27 18:20 ` Chris Gianelloni
2004-07-27 18:41 ` Lance Albertson
2004-07-27 17:59 ` Jason Rhinelander
2004-07-27 18:07 ` Ciaran McCreesh
2004-07-27 18:18 ` Dylan Carlson
2004-07-27 18:45 ` Ciaran McCreesh
2004-07-27 19:26 ` Dylan Carlson
2004-07-27 20:09 ` Ciaran McCreesh
2004-07-27 20:23 ` Donnie Berkholz
2004-07-27 20:29 ` Spider
2004-07-27 20:37 ` Dylan Carlson
2004-07-27 21:39 ` Ciaran McCreesh
2004-07-27 22:24 ` Dylan Carlson
2004-07-27 22:59 ` Ciaran McCreesh
2004-07-27 23:12 ` Dylan Carlson
2004-07-28 7:06 ` Tom Wesley
2004-07-27 22:49 ` Tommi Pirinen
2004-07-27 23:07 ` Ciaran McCreesh
2004-07-27 23:46 ` Tommi Pirinen
2004-07-28 6:55 ` Tom Wesley
2004-07-28 7:52 ` Georgi Georgiev
2004-07-27 21:06 ` David Sparks
2004-07-27 23:01 ` Stephen P. Becker
2004-07-28 3:48 ` Kumba
2004-07-27 19:49 ` Kurt Lieber
2004-07-27 19:53 ` Lance Albertson
[not found] ` <4108A16D.9090508@butsugenjitemple.org>
[not found] ` <4108ECA5.1020102@gentoo.org>
[not found] ` <4108F3A5.1000505@butsugenjitemple.org>
2004-07-29 13:11 ` Lance Albertson
2004-08-06 10:09 ` Paul de Vrieze
2004-07-28 2:53 ` Mike Gardiner
2004-07-28 3:11 ` Robin H. Johnson
2004-07-28 6:55 ` Tom Wesley
2004-07-28 14:12 ` Dylan Carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1090952262.1538.67.camel@6-allhosts \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox