[Tracker-discuss] Tracker for web-related issues

["Martin v. Löwis"]

> * It seems the real complexities are in the workflow, which is mostly
>   defined by the set of status enumerators, together with the detectors
>   that enforce constraints on possible state changes.

I disagree. The notion of workflow is overrated: it assumes that there
is work to flow. In many cases, this is not the case. People want the
tracker just to not forget things.

>   I believe it to be easier to start with a clone of the python-dev
>   tracker and removing unwanted stuff, instead of starting over with
>   a new vanilla tracker and trying to make it look like a python tracker.

I would say that the admin of the tracker should decide (and he should
fully understand that any such decision will have wide-reaching
consequences in time, i.e. that it will be very difficult to change
and that changes to it will be infrequent).

Regards,
Martin