Skip to content
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
This repository was archived by the owner on Nov 18, 2021. It is now read-only.

Show net +1 - -1 votes on issue index #605

Open

Description

@cirosantilli

i.e. at https://github.com/isaacs/github/issues

Like the GitLab thumbs up at: https://gitlab.com/gitlab-org/gitlab-ce/issues

This is an extension of #527 to consider downvotes as well.

Activity

  1. glen-84 commented on Apr 2, 2016

    @glen-84

    I don't think that negative values should be displayed, at least not until the negative value is significant (-5, -10, or some % of the average vote count).

    If one random user is the first to vote, and down vote, the issue could easily become less visible, and influence other users.

  2. cirosantilli commented on Apr 2, 2016

    @cirosantilli
    CollaboratorAuthor

    @glen-84 the same could be said for upvotes no? One user with no experience could do the upvote and give too much importance to something that should not have.

    Maybe what you propose is a possibility. But the only real "solution" is more complicated algorithms, like a page rank / Reddit front page (considers time as well).

  3. glen-84 commented on Apr 3, 2016

    @glen-84

    Maybe, but I think that down votes are more damaging than up votes.

    Perhaps there could be a minimum number of votes in either direction, before display.

  4. TPS commented on Apr 3, 2016

    @TPS
    Collaborator

    It'd perhaps be more important to get the issue implemented first, & then suggest incremental improvements. It's much less likely we'll receive improvements if we require huge effort on the front end.

  5. lamont-granquist commented on Apr 3, 2016

    @lamont-granquist

    👍 on general idea and 👍 on only counting upvotes and not the net upvote-minus-downvote count (although it looks like configurability would be good -- but all I would want is upvotes and not downvotes).

    and my rationale is that typically user downvotes aren't very high quality and are often biased based on some axe they want to grind or some philosophy they're afflicted with. maintainers who typically have better quality 'negative' opinions that take into account the whole project and its technical limitations and goals already have the ability to close and lock threads for truly bad ideas. on the other hand, a surplus of upvotes in some issues can be useful to inform maintainers of some pain point in their software that was in their blind spot.

    clearly YMMV.

  6. ElectricRCAircraftGuy commented on Apr 23, 2020

    @ElectricRCAircraftGuy

    Taking it one step further, perhaps this should even be done by net positive/negative reactions.

    Ex: 👍 (positive reaction) + ❤️ (positive reaction) = +2, and 👎 (negative reaction) + ☹️ (negative reaction) = -2

    So something like 🎉 + 👍 + ❤️ + ☹️ + 👎 = net +1

    This means all reactions need to be bucketed into "positive", "negative", and "neutral" categories, which would support implementing #1782 as well.

  7. added a commit that references this issue on Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions