maproulette / maproulette/maproulette-frontend
Idea: Moderation tools
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Description
Twice now I've found that someone had opened up one of my "quick-fix" challenges and hit "yes" a few hundred times without reading the instructions. I know it's partly my fault for making a challenge so easy to mess up, but it would still be nice to have better ways to repair or prevent the damage. For example:
- Allow an admin to mark tasks for review, even if the user didn't request it (see also #1068)
- Include the quick-fix changeset in the export CSV
- Button to revert the quick-fix changeset from task review
- Go to a user's profile from Task History, and to their OSM profile from their MR profile
Filter task list by user or completion timejust noticed I can do this with "configure columns"- Require a minimum editing time
- Revoke points or otherwise penalize bad edits
- Ban users from participating in a challenge (have not needed this yet)
Related issues: #791, #454
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 reading related issues #1068, #791, and #454, then inspect the existing task review, export, and history flows. The issue lists several possible moderation capabilities rather than naming one scope; work would need a selected capability, defined acceptance criteria, and verification that the corresponding user flow is complete.
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