maproulette / maproulette/maproulette-backend
Clarify the difference between Skipped and Too hard to fix
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Follow up of https://github.com/osmlab/maproulette/issues/377 sorry having posted it in the wrong repo.
From what I understand:
- skipped tasks are showed again to other contributors and are still in the remaining tasks
- too hard to fix are not showed again and are not in the remaining tasks
If it's correct, then it should be clear that marking as "Too hard to fix" won't let the chance to anyone else to try the task. I fear that it might be used too much instead of "Skip"
For example, we could at least have a confirmation saying:
Are you sure it's too hard to fix? If you think another contributor could fix it, then skip the task.
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
No file, test, or entry point is named. Start by locating the backend handling for the Skip and Too hard to fix task states, then trace how those states affect remaining tasks and contributor visibility. Done means the distinction is clearly communicated and the proposed confirmation behavior is implemented and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100