How to organize work?

We need some way to organize tasks to be done (tiddlywiki, testsuite, …?)

Discussed in the March.2008 developer meeting.
We decided to use a TiddlyWiki for now until this is further worked out

What shall I say, just Whew! 😖

For context, I can recall that Cehteh had a very pronounced aversion against bugtrackers (and especially Bugzilla), because they are just plain confusing, filled with obsolete information and last but not least, they create spurious work without being helpful for the developer. Wouldn’t it be much better to put everything into the code or close to the code (as markup in comments)? Git would propagate this information to the community of other contributors, which would decide about what is viable, just simply by merging or not merging — and some clever tool could watch the resulting commit stream and extract the minimum necessary accounting to supply the developers with that amount of information they need to be actually productive….

Lumiera is quite another kind of project today. There is a Bugtracker, and I need all kinds of meta-tickets, tags, overview lists, the content in documentation pages plus my own personal notes in several mindmaps just to cope with the sheer amount of information and not to forget about matters already decided and settled.

All this meta-work takes a considerable amount of effort, for sure.
Yet the question remains, how can I “keep track” without keeping track? How can I judge and decide, without actually performing the judgement to arrive at a decision? Would it make any difference to this dilemma, if “someone else” were to perform that work??

Can this kind of immaterial mental work be conditioned and commodified into an industrial process, so that the individual person might side-step the effort, yet sill remain a sovereign?

I do not know the answer to this question.

Back to Lumiera Design Process overview