maproulette / maproulette/maproulette-frontend
Up and Down Voting for challenges (once they are online)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Description
What would you like to see?
An up or down vote for challenges.
Ideally with optional detailed feedback categories, such as:
- Instructions are clear
- Challenge is interesting
- Imagery is suitable
Maybe also other aspects that are not so much good/bad, but informative to other users
- It takes me 1/5/15/30/more minutes to solve
- It's easy/challenging
Why is this useful?
-
Users can find high quality challenges more easily
-
Challenge creators get feedback on (which aspect) of their challenge is liked/disliked
Additional context
a few related concepts:
- users can favorite a challenge - need to make sure to not confuse users between favorite vs up/down vote, but I think like vs subscribe is a pattern that users are used to on many platforms
- I see that some challenges are marked as "popular" so it seems there is some existing scoring algorithm, maybe based on participation? Or maybe on number of users making it a favorite? Assuming the user voting would turn into the single most prominent score then the existing popularity score could be moved into the list of detailed scores
- There is an issue about voting before going live https://github.com/maproulette/maproulette3/issues/2564 I thought it makes sense to have a separate discussion about the merits of voting after go live, in order not to muddy the discussion. However, maybe it would be useful if the actual implementation of voting would cover both use cases (... or maybe not?!)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing favorite and popular-challenge experiences, then compare the post-launch voting proposal with related issue #2564. Clarify whether voting should include the listed feedback categories and time or difficulty information, and define how it differs from favorites and existing popularity scoring before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100