After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 390454 - Voting on features
Voting on features
Status: RESOLVED WONTFIX
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: Reports
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
: 568627 629161 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-28 19:33 UTC by Maciej (Matthew) Piechotka
Modified: 2015-02-11 02:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Maciej (Matthew) Piechotka 2006-12-28 19:33:09 UTC
Sometimes I'd like to say 'This feature is important for me as well'.
However:
- Comments, in my opinion, should be for developers solving the problem (not before solve)
- Duplicates are not welcome.
Comment 1 Olav Vitters 2006-12-28 20:05:33 UTC
The best way to get some feature implemented:
1. Write a patch
2. Get someone else to write a patch
50. CC yourself (that already shows provides insight in how much interest there is)

I will only enable voting if developers will actually *only* use the number of votes when making decisions which feature to implement first. However, due to limited time and developers having other priorities just than votes, I do not see this happening.

Without developers actually using only votes to prioritize features, votes will give an empty promise to the people voting. Meaning.. that voting makes a difference (it does not). The result (often seen on Mozilla's Bugzilla) is people complaining that some feature is not implemented while it has >XX votes and was filed X years ago.

Voting would have the same result as cc'ing. So I'm wontfixing this.
Comment 2 Maciej (Matthew) Piechotka 2006-12-28 20:33:58 UTC
Ok. Thanks I'll CC
Comment 3 Susana 2009-01-24 11:27:28 UTC
*** Bug 568627 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2010-09-09 13:55:00 UTC
*** Bug 629161 has been marked as a duplicate of this bug. ***
Comment 5 Felipe Contreras (banned) 2011-09-08 23:30:26 UTC
(In reply to comment #1)
> Without developers actually using only votes to prioritize features, votes will
> give an empty promise to the people voting. Meaning.. that voting makes a
> difference (it does not). The result (often seen on Mozilla's Bugzilla) is
> people complaining that some feature is not implemented while it has >XX votes
> and was filed X years ago.

Wrong.

I have never seen people thinking that a bug with a high number of votes *must* automatically mean it has high priority. That's a wrong assumption from your part.

However, a committed developer should take this into consideration while deciding the priority a bug must have, and (s)he so decides, explain clearly why a bug with a high number of votes gets low priority.

Or (s)he can just ignore the votes if (s)he so desires.

It's completely up to the developer, and you can see from bug #629161. There's already some GNOME developers that would use this feature.

> Voting would have the same result as cc'ing. So I'm wontfixing this.

No, it won't.
Comment 6 André Klapper 2015-02-11 02:45:31 UTC
*** Bug 629161 has been marked as a duplicate of this bug. ***