Broaden scope.

This is a very impressive module, and aside from a few niggling issues (in other bug reports), looks like it would work really well for what it's designed for, which appears to be software/website development, or related activities. This is just my take on it, so feel free to take it or leave it.

At the moment, I probably won't use it because of that last point. Some of the specific problems include the categories for projects and tasks, and the topics for the "knowledge base". I'm looking for generic project management software that's easy for newbies to use, and storm is almost there, but these limitations would make it extremely confusing for most of my users. Some examples of organisations that could use decent generic project management software include advocacy organisations, consultancy firms, and even more physical work, like a printing shop.

Of course, these few limitations could be easily remedied, and I could then use storm well enough, but I may have missed things, and if the focus of storm stays on web/software development, then future decisions will also be limited. If you broaden your scope, you potentially get many more users, who can bug hunt, and help improve the project.

If you decide that storm should stay limited to software development, that's a fine decision, but it would be good to state on the module page that "Storm is aimed at..." or something like that.