[master issue] Task Lifecycle and Task Statuses

[mvexel]

The goal of this ticket is to

1. Collect relevant previous issues that talk about the MapRoulette task lifecycle, the different task statuses and their transitions, and what we consider "final" task statuses.
2. Gather feedback that will inform any changes we may make to the task lifecycle in the next major MapRoulette version (4.0)

Why

The Task Lifecycle is really at the core of how MapRoulette works for mappers. A task is created (new), then the mapper takes some action on it, and eventually it arrives at an end state: fixed or in some way not fixable. We have attempted to keep this flow as simple as possible, but questions and feedback about the task lifecycle keep coming up, as new users and use cases emerge.

Status Quo

This diagram captures the current task lifecycle, with user actions and the resulting transitions in blue, and the possible task states in black boxes:

What next?

We will edit this description with a list of relevant (open and closed) issues about this topic and welcome a broad discussion about this topic. This will inform any changes we may make to the task lifecycle for v4.

Thanks for your participation and interest in the future of MapRoulette!

[mvexel]

Here's an idea for the record: in addition to too hard / can't fix the mapper could select ask a local mapper as a status. This could connect to on-the-ground mapping tools like Vespucci, GoMap!! and StreetComplete (see also #1737)