maproulette / maproulette/maproulette-frontend

Voting for new tasks/challenges before they get online

Open
#2,564 3 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion enhancement
Dominant language
JavaScript
Stars
167
Forks
39
Avg merge
16h 34m
Merged PRs (30d)
11

Description

Is your feature request related to a problem? Please describe.

There is currently a very lifely discussion in the OSM forum about the quality of some MapRoulette challenges and how it could be possible to improve them before they go live. Some challenges are poorly designed, leading to incorrect edits or frustration among contributors.

Describe the solution you'd like

A potential solution would be to require new tasks/challenges to receive positive feedback before they are published. However, there are some challenges to consider:

  • What happens if a challenge is well-designed but does not attract enough reviewers, leading to a lack of votes?
  • Should MapRoulette have an internal voting/review system, or could an external system, such as OpenStreetMap Discourse voting, be leveraged for this purpose?
  • This could be integrated with https://github.com/maproulette/maproulette3/issues/2563, where new challenges must be discussed in a forum thread. The process could require a simple yes/no poll to be open for X days, with the challenge only going live if negative votes stay below a certain percentage (e.g., Y%). Not sure if that even possible to request from the discourse forum.
  • How should cases be handled where a challenge initially receives significant negative feedback but is later improved based on discussions and changes?

Describe alternatives you've considered
There could be some ranking system, but i personally don't like this because OSM itself does not have any kind of "ranking". There could also be a checklist that needs to be checked, but i'm not sure

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by clarifying whether voting belongs in MapRoulette or OpenStreetMap Discourse, then define the review period, approval threshold, and handling of revised challenges. Done means an agreed, implementable workflow with clear publication rules.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.