maproulette / maproulette/maproulette-frontend

Require certain number of tasks solved to gain "reputation" before you can create challenges

Open
#1,853 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I would like to raise the bar a little bit for creating MapRoulette challenges. Reason for this is I want to ensure when you create a challenge you have a decent amount of familiarity with the MapRoulette application and "flow".

This could take two forms that I see:

  1. Lock "Create and Manage" until you have completed (fixed) at least N tasks.
  2. Don't lock the functionality but don't allow a challenge to be made public until at least N tasks in it are fixed.

This is a tricky one, because I really don't want to create the incentive to game the system by marking tasks as fixed when the user has done nothing to fix them, but on the other hand I do want to continue to improve MR to ensure higher quality tasks.

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

Start by reviewing the proposed Create and Manage restriction and the alternative of delaying challenge publication. Clarify the required task threshold and how to avoid incentivizing users to mark tasks fixed without doing the work; done means an agreed policy is implemented for challenge creation or publication.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.