Page MenuHomePhabricator

ranking features as simple A vs B
Closed, InvalidPublicFeature

Description

feature:
provide a voting application doing ranked pairs, or similar: https://en.wikipedia.org/wiki/Ranked_pairs. the input is a list of URLs. the voting can be presented at any entry point, like wikipedia main page. a window would pop up and display 2 options where a user can choose one, or skip the comparison. an optional comment why the comparison was skipped can be given.

use cases:
arbitrary events where simple voting on many entries should order a list, like:

  • vote for entries in community wishlist surveys and comparable.
  • vote for entries in wiki loves monuments.

benefits:
lets take the use case of voting for entires in the community wishlist survey to describe the benefit: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey . voting on such proposals is heavyweight. there is no easy link out of the wikipedia main page which attracts users to participate. a user needs to wade through a lot of text and the chances to give up are high. while presenting a pair and preference is easy, and sorting the preference is easy and quick. we might get only one click per user, but it is good enough. a "i do not care / i do not understand" should just ignore the comparison, and store it like this as information for the ones who made the proposal and statistics.

the entries can be url's, like wiki pages, wikidata entries, phabricator tickets where information can be extracted like when hovering over a link in wikipedia and a small pop up appears as a summary.

multiple ordered lists can be produced as well. as log in is possible to vote, we know if the person reads, or edits, and how many edits the person makes, etc. like "long term contributors with less than 10 edits a year prefer, while anonymous voters prefer ..."

Event Timeline

Aklapper changed the task status from Open to Stalled.Jan 29 2022, 8:06 PM

@ThurnerRupert: I unfortunately have no idea what exactly this ticket is asking for about which part of the software stack and why it was created here. Please use the feature request form (linked from the top of the task creation page) to create feature requests:

Feature summary (what you would like to be able to do and where):

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

Benefits (why should this be implemented?):

@Aklapper let me rewrite it. i now found how this is called. ordering via ranked pairs, or schulze method or whatever lets you sort a list via comparing 2 pairs, or a low number of entries.

re-reading your 2nd remark, you mean a proposal to improve the voting for wishlist survey should be posted to wishlist survey? how ironic :) for this year it is too late, and for next year i will have already have forgotten about the proposal until voting pops up on the main page.

is it possible to tag this so it automatically goes as proposal in the 2023 round of wishlist survey, in case you think it needs to be part of such a run?

re-reading your 2nd remark, you mean a proposal to improve the voting for wishlist survey should be posted to wishlist survey? how ironic :)

Heh, no :) - I meant it should be posted on the talk page about the community wishlist survey.

  NODES
COMMUNITY 5
Idea 1
idea 1
Note 1
USERS 1