maproulette / maproulette/maproulette-backend
RFE: Allow priorities to take into account how near tasks are to currently edited tasks
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I want to avoid editor conflicts since, in my experience, an editor will often make a mistake during conflict resolution.
So I'd like to either have a way to "lock" tasks within a certain radius of a task currently being mapped or a way to de-prioritize those tasks (e.g., if no editor working on task within 5 km, then task is high priority, else if editor is working on a task within 5 km but more than 3 km away, then task is medium priority, else if editor is working on a task less than 3 km away, then task is low priority).
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 files or tests are named. Start by locating how task priorities and currently edited tasks are represented, then clarify whether the desired outcome is radius-based locking or priority changes; done should include an agreed behavior and tests for the distance thresholds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100