From: Tommi Pirinen <tommi.pirinen@kolumbus.fi>
To: Ciaran McCreesh <ciaranm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bug voting
Date: Wed, 28 Jul 2004 01:49:39 +0300 [thread overview]
Message-ID: <4106DC03.8080104@kolumbus.fi> (raw)
In-Reply-To: <20040727223904.524c952f@snowdrop.home>
Ciaran McCreesh wrote:
>No, subtle as in "this bug will cause people various really strange
>problems, but they won't realise what's causing it". Don't forget, the
>package maintainers quite often know a lot more about the package and
>the way it interacts with the system than the bug submitters and voters.
>
>
>
IMHO situation like this, when developer knows more than bug reporters,
should be handled by marking the bug invalid, wontfix or later with an
explanation. The current situation often seems that developers decide to
"know more" without saying it to anyone, and from user/bug reporter
point of view it seems as if he hasn't been heard or no one cares about
the issue.
The main deal with this whole discussion to me as end user seems that
gentoo's bugzilla has gotten very much of the reputation that bugs just
sit there without no one noticing. As you might have noticed this
concern comes up a lot in the user fora and granted, the reason might be
the stupidity of users, but I'm sure it won't go away soon. Most of the
people complaining about it do report at other projects as well, and
from my and their experience other projects do have quite a lot better
response times from bugzilla than gentoo does. Of course this bug voting
wouldn't be much of help to the actual problem, more than just slowdown
for the most eager bug reporters.
>Good example: the automagic link detection before DHCP feature that
>people keep on wanting in baselayout. Looks nice on the surface, lots of
>people saying "yes please", but suddenly when it's implemented we get
>thousands of users with broken networking because it turns out that that
>nifty link detection feature isn't universally reliable.
>
>
>
So it's users' fault that someone implemented and released broken
feature? I know that job of developers isn't easy either, but I think
this example isn't very good argumentation against anything. And if the
developer here knew more, he could've just said it's not reliable enough
to implement.
>Well, either the voting affects developers, in which case it's a serious
>problem because it'll detract from the bugs which are *actually*
>important, or it won't affect developers, in which case your claims
>above are effectively meaningless.
>
>
>
Or the voting keeps users doing something that seems important to them ;-)
--
Flammie, generally nobody from nowhere in the internet.
Uninteresting generic profile at
<URL: http://cs.joensuu.fi/%7Etpirinen>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-27 22:49 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
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 19:31 ` [gentoo-dev] " Duncan
2004-07-27 18:07 ` [gentoo-dev] " 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 [this message]
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 23:26 ` [gentoo-dev] " Gabriel Ebner
2004-07-27 23:41 ` Gabriel Ebner
2004-07-27 23:48 ` Gabriel Ebner
2004-07-27 23:52 ` Gabriel Ebner
2004-07-28 0:02 ` Ciaran McCreesh
2004-07-28 0:08 ` Mike Frysinger
2004-07-28 0:10 ` Gabriel Ebner
2004-07-28 0:08 ` Jon Portnoy
2004-07-28 0:14 ` Gabriel Ebner
2004-07-28 0:09 ` Dylan Carlson
2004-07-28 0:21 ` Gabriel Ebner
2004-07-28 0:30 ` Gabriel Ebner
2004-07-27 21:06 ` [gentoo-dev] " 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-07-29 15:14 ` [gentoo-dev] " Duncan
2004-07-29 17:50 ` Dylan Carlson
2004-07-30 2:41 ` Ciaran McCreesh
2004-07-30 4:00 ` Dylan Carlson
2004-07-30 11:05 ` [gentoo-dev] " Duncan
2004-08-06 10:09 ` [gentoo-dev] " Paul de Vrieze
2004-07-27 20:09 ` [gentoo-dev] Bug voting++ Frank van de Pol
2004-07-27 21:09 ` Dylan Carlson
2004-07-28 0:26 ` [gentoo-dev] Re: Bug voting Joel Konkle-Parker
2004-07-28 2:53 ` [gentoo-dev] " Mike Gardiner
2004-07-28 3:11 ` Robin H. Johnson
2004-07-28 6:55 ` Tom Wesley
2004-07-28 14:12 ` Dylan Carlson
2004-07-28 23:58 ` [gentoo-dev] " Joel Konkle-Parker
2004-07-29 0:38 ` Dylan Carlson
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 18:17 [gentoo-dev] " Brian Harring
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=4106DC03.8080104@kolumbus.fi \
--to=tommi.pirinen@kolumbus.fi \
--cc=ciaranm@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