Change Details

in 2022-01 there is a possibility to bring proposals and vote on them in the community wishlist survey: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey . to make a proposal is ok, but anyway kind of heavy, standard ticketing is not used. more serious is how the voting happens. look through proposals and vote on them can be time consuming and therefor not so attracting. a simple A vs B ranking might be much more attracting to "standard young internet users", or, even standard wikipedia editors. the source can be wiki pages of propsals, as we have nowadays, as well it could be phabricator pages?

**feature:** provide a voting application doing ranked pairs, or similar: https://en.wikipedia.org/wiki/Ranked_pairs **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:** to take out the use case of voting for entires in the community wishlist survey: 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.

in 2022-01 there is a possibility to bring proposals and vote on them**feature:** provide a voting application doing ranked pairs, or similar: https://en.wikipedia.org/wiki/Ranked_pairs **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:** to take out the use case of voting for entires in the community wishlist survey: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey . to make avoting on such proposals is ok,heavyweight. but anyway kind of heavy,there is no easy link out of the wikipedia main page which attracts users to participate. standard ticketing is not useda user needs to wade through a lot of text and the chances to give up are high. more serious is how the voting happens.while presenting a pair and preference is easy, look through proposals and vote onsorting them can be time consuming and therefor not so attracting preference is easy and quick. a simple A vs B rankingwe might be much more attracting to "standard young internetget only one click per users", or,but it is good enough. even a "i do not care / i do not understandard wikipedia editors." should just ignore the comparison, the source can be wiki pages ofand store it like this as information for the ones who made the propsalsosal and statistics. the entries can be url's, as we have nowadayslike wiki pages, as well it could be phabricator 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.