Apache OpenOffice (AOO) Bugzilla – Issue 69811
Allow more votes per component
Last modified: 2013-02-07 22:35:55 UTC
I think allowing more votes per component should be considered, at least for the five main components for the final user: Database, Drawing, Presentation, Spreadsheet and Word Processor. As their complexity and funtionality grows and the userbase also grows, there will be more and more bugs that people would like to nominate through voting. Mi suggestion is to go from 5 votes to 10 or even 15.
In the same way that developer resources are scare, so should be votes. I suggest not increasing the limit except maybe for people who are QA volunteers, developers, so perhaps "points" can earn votes. At Gnome's http://bugs.gnome.org , they use a point system http://bugzilla.gnome.org/page.cgi?id=points.html . In any case, I do not see much of a correlation between votes and allocation of efforts.
+2! ;-) I try and do my bit for QA, and the voting system is useful not just for developers to track demand, but also for those who do QA to track Issues of interest (a quick bookmarking method). I would love to see 10 votes (vs 5), since I never have enough! Earning them might be handy, but IMHO not worth the developer effort. Give people ten votes- what's the worst that could happen? Regards, Andrew
I vote for this, because I keep finding new issues. There might be also restriction to use 2 votes only once, if possible.
I vote for this, because I keep finding new issues and then delete more important ones hoping that they will be fixed anyway. But, I can't track them any longer. There might be also restriction to use 2 votes only once, if possible.
I sometimes would like to vote for new issues, but often the older ones, I voted for, aren't still fixed. Now I come in conflict with the restriction to 5 votes per component. I don't want to delete my votes for the older issues but I can't put new votes... Maybe a restriction to not set more than n votes in one month or in one year or something like that could be useful instead.
Reset QA Contact to new default