I started using sr.ht recently and a few ideas I would like to see have already been reported. I would like to upvote on such tickets to indicate that it's something I would like to see as well, without necessarily having to comment - as it adds to more notifications.
I'm not sayingnoyet... but this is a deliberate omission. I don't know of any maintainers who actually use votes to govern their priorities, they're usually just a placebo that preventsme tooing.
I think the more we allow people to publicly display interest in a ticket without them having to spend effort, the less likely they're going to be to actually try their hand at addressing the problem. Instead, maybe a better alternative is to use someUX trickeryon todo (and other services) to make it more convenient for interested parties to actually contribute to the issue at hand instead of simply showing superficial interest in it. Like how Github has theForklink at the top of pretty much every page in a repo, maybe we could do something similar, like adding links to the related git repo/mailing list(s) when we know that they're related (maybe this could be added alongside the metadata fields at the left ascontext?).
As a developer, I like theme toobutton. The question comes down to, would you rather the ego boost from closing 20 issues, or get a counter of number of users who've bothered enough to click theI can duplicate this bugbutton?
Github has the reaction system, which helps reduce noise but no meaningful way to sort by how many users are actually having the issue.
I don't know of any maintainers who actually use votes to govern their priorities, they're usually just a placebo that prevents me tooing.
Perhaps we could have aI am affected by this bugbutton? That should be slightly more useful to maintainers.
Honestly, preventingme too-ing seems like it may be a desirable goal in itself. There's a few different ways one could achieve this though.
Outside of this ticket,me too-ing seems to be pretty rare on sr.ht right now :)
I swear searched (probably for voting instead of vote) before opening my duplicate. +1 for this feature itself.
I don't know of any maintainers who actually use votes to govern their priorities […]
Lodash does something like this. All feature requests are closed and remain that way until they get picked up, while soliciting +1 reactions. A URL to a filtered issue list is provided where people can see all the pending requests sorted by number of +1s. Presumably this is the list the maintainers will use to decide what features to pick up as well.
I know at least one project that has copied this strategy.