maproulette / maproulette/maproulette-backend
Where to go with Surveys
Open
Nobody has claimed this yet.
BACKLOG
needs-discussion
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Right now Surveys are the least used / tested part of the system. We haven't really decided how to handle the results and how to have the Survey challenge owner define the dynamics.
Let's use this ticket to share some ideas and converge on a development path.
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
The issue names no files, tests, or entry points. Start by reviewing the existing Surveys implementation and API, then read the discussion to identify an agreed development path. Done requires a decided scope and implementation plan before coding can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100