Allow voting on issues
David Lesieur - December 24, 2005 - 04:54
| Project: | Drupal.org infrastructure |
| Component: | Drupal.org module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Currently, when one finds that an issue is already filed, if he wishes to raise the importance of the issue, he has to post a comment saying "+1"...
Maybe votes could be helpful when prioritizing tasks. This could be in the simple form "1 member <=> 1 vote". Bugzilla allows this.
#1
I have doubts regarding this voting idea, but by limiting the total number of votes allowed per user, each user would be able to vote only for his most important issues. If votes had such "cost", it could really mean something when an issue gets a lot of votes.
Maybe such mechanism could help sorting the high number of issues.
OpenOffice's Issue Tracker uses this, as explained here.
But I guess a motivated evil user could still create himself additional accounts to be able to put in more votes than allowed...
#2
still a good idea
#3
yeah, I've been thinking of this to. The notorious reasons for "spam" on the issue tracker are:
1) +1
2) Subscribing
Where a issue should have a subscribe button and +1/-1
#4
Moving to the right queue. Also, see the (now duplicate) #218877: Provide a "Vote for your favorite" feature request for a little additional information.
#5
See the Project Issue Voting module.
#6
Indeed, Project issue voting solves this need. However, I wouldn't quite call this "fixed", since there's now the question of deploying the functionality on d.o itself. That would introduce a dependence on VotingAPI, so that might be a source of contention. Also, I'm going to be AFK until Sept 1st, so I doubt this is going to happen before then (although perhaps hunmonk is interested in helping see this through). So, I'm moving this into the right queue for further discussion, to get approval of the new dependency, and to coordinate getting this live.
#7
The issue has come up before, and it has indeed been a source of concern. In the past, Dries has said that he didn't want VotingAPI on d.o., as it would be another unacceptable dependency. Performance issues are also a concern. While the Drupal 6 version of VotingAPI has quite a few performance enhancements, the original API used in the D5 version tends to choke when huge numbers of votes are cast on huge numbers of items.
If we're talking D6, though, and Views is already part of the equation, I don't think there should be too much concern.
In the past, upgrading votingapi from one version of Drupal to the next has been cake; it's almost entirely "API" and thus doesn't require much refactoring unless real opportunities for enhancements are discovered. The D6 version was actually ready for testing only a month or two after the D6 beta came out.
#8
+1
I feel the need to add "+1" along with some 'non spam'!
Dreamhost does this as well, for suggestions to add new features. Every user gets a set of "points" and each issue gets a number set 1-5 (depending on how hard it is to implement). Users can then "suggest" from a list set by Dreamhost. Seems to work rather well to find customer needs and requests.
#9
#10
I've posted a first review of the module at #328648: Module review, and have to disagree: issue voting can be handled independently from d.o redesign.
#11
+1 for the original proposal to turn "+1" and "subscribing" into simple counters that will help prioritize issues. IMHO this is crucial for onward efficiency of the whole Drupal project.