Infrastructure

Discussed in this QA meeting -> http://nabble.documentfoundation.org/Libreoffice-qa-Fwd-QA-Meeting-Brno-Libreoffice-Conference-Wed-19-00-20-00-UTC-2-tt4192770.html#a4192907

I still do not think this is a good idea. It would require changing the way development is done. It would require developers & their employing companies to buy into this new system of fixing popular bugs.

I would say the first step would thus be: get all the companies on board the new development model where most popular bugs are fixed.

Then the second step would be how to determine the most popular bugs.

Voting could or could not be implemented as a solution based on these steps.

This was discussed in the past here as well: https://bugs.documentfoundation.org/show_bug.cgi?id=37141 and it was closed as RESOLVED WONTFIX

I still do not think this is a good idea. It would require changing the way development is done. It would require developers & their employing companies to buy into this new system of fixing popular bugs.

I don't understand this (and other comments made about this voting feature). This doesn't change any way development is done.
It just gives users a way to say: This issue affects me / is important to me. I find that valuable feedback.

Developers are free to consider that, or ignore it.

It also should prevent some +1/me too comments.

Personally if I have to choose tasks, I like to browse the tasks with most people in CC because I want to see which bugs really bother people. The voting feature would help there for example.

Btw Launchpad has a similiar way for users to say "This bug affects me", see e.g. https://bugs.launchpad.net/ubuntu/trusty/+source/nlpsolver/+bug/910143
If it helps you can rename "Vote for this bug" to "This bug affects me".

Yes, we know about Launchpad etc.

Think of it this way: it gives users the impression that development is dedicated to fixing bugs in the order of popularity. When that obviously does not happen, we get angry users. So we essentially make a promise and then betray them. This will increase the number of comments, not +1, but "why the heck is this not fixed, even though it is so popular??"

You already have other metrics to find most annoying bugs.
The most duplicated ones: https://bugs.documentfoundation.org/duplicates.cgi or https://wiki.documentfoundation.org/QA/Stats/MostDuplicatedBugs
Most CC'd people: https://wiki.documentfoundation.org/QA/Stats/MostCCBugs
Priority high or highest: https://bugs.documentfoundation.org/buglist.cgi?bug_status=NEW&limit=0&list_id=781908&order=priority%2Cbug_severity&priority=highest&priority=high&query_format=advanced&resolution=---

Those already should keep a horde of developers busy for a long time.