Bug 390302 - Voting for bugs
Summary: Voting for bugs
Status: RESOLVED INTENTIONAL
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDE sysadmins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-12 03:47 UTC by Andrew Crouthamel
Modified: 2018-02-12 19:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Crouthamel 2018-02-12 03:47:59 UTC
I believe it would be a great benefit to the KDE community to enable bug voting on all products. KDE has shown year after year how open and accepting they are to community feedback, and this would be a natural extension of that. Allowing the community to add their vote to an issue or feature request could be greatly beneficial to developers. It would provide an opportunity to focus on community-desired bugs and features continuing to improve the great goodwill KDE has, and make each KDE release even more impactful and news-worthy.
Comment 1 Ben Cooksley 2018-02-12 07:26:38 UTC
Are there any products you are referring to specifically here?
Most products should have it enabled.
Comment 2 Andrew Crouthamel 2018-02-12 13:48:09 UTC
I noticed it in Discover, plasmashell, and KScreen so far. It's supposed to show as (vote) next to Importance, right? Also, is there a way to show vote counts when browsing bugs? It would be helpful to see that.
Comment 3 Christoph Feck 2018-02-12 18:52:50 UTC
You can adjust the visible columns in bugzilla. Plasma developers decided to disable voting, because having more people needing a feature does not automatically create code. We need more people writing it.
Comment 4 Andrew Crouthamel 2018-02-12 19:02:07 UTC
(In reply to Christoph Feck from comment #3)
> You can adjust the visible columns in bugzilla. Plasma developers decided to
> disable voting, because having more people needing a feature does not
> automatically create code. We need more people writing it.

It would help understand which ones impact the most people, or is most requested. How would you determine that otherwise?
Comment 5 Christoph Feck 2018-02-12 19:04:14 UTC
What would you do with this information?
Comment 6 Andrew Crouthamel 2018-02-12 19:09:18 UTC
(In reply to Christoph Feck from comment #5)
> What would you do with this information?

Besides the obvious critical issues such as crashes or data loss, it would help developers (whom I hope to join as one soon) to prioritize what to work on. I know personally, I'd rather work on an issue or request that affects or is desired by a larger population of KDE uses, than a smaller one, first. Looking at Bugzilla, I don't see an easy way of determining that. Number of comments is an option, but that could just be a few people having a discussion back and forth.
Comment 7 Christoph Feck 2018-02-12 19:34:40 UTC
There are severity and priority fields, but I suggest to discuss it on the plasma-devel list or on #plasma IRC.

On a more personal advice, I suggest to start with tickets that are interesting to _you_.