Carl, I'm sorry, I didn't make myself clear enough. For sure it
should be more generic than for coding! The "steps" I gave
examples to (with design, code,test) was just that, an example.
The idea is that for each project, you would define the steps that
your tasks must undergo. For a coding project, you would define
the tasks design, code, test, but any other steps could be
defined for other types of projects. This definition of steps has to
be part of the web interface and data model, no SQL hacking.
The idea behind the "steps" idea is to be able to make a
2-dimensional table that shows tasks and steps, instead of
infinitely nested tasks.
