Very cool. I looked at Tracks at one point but, not yet being rails savvy, I never implemented it. I've always wanted to try it, so I will email you for an account. Thanks!

I'm a GTD wannabe since I really really like the principles, have read the book and kinda get it, but I have yet to work out something that serves me as a trusted system. And without that, it all falls apart. To that end, I've tried several other GTD systems in the past year or so.

My first attempt was to install the open source phpGTD on my server. I used it only a little since I never much liked the interface, finding it missing key components of Allen's system.

I've also tried several variations of a GTD wiki on a USB stick, but again never found that it actually fit with how I work.

Then, after that, I discovered iCommit, a German hosted GTD service which is the closest thing to a complete system I had used. I used it off and on over this summer but there were nagging omissions that made it hard for me to keep me, um, committed to it. It was originally developed in php but the author has moved it over to rails. The author hasn't released the code, which is kind of too bad since it is almost the right approach.

http://gtdv2.icommitonrails.de/

Most recently, I started using Listigator, which is a collaborative to-do list. It isn't really a GTD system at all although, because you can create as many separate lists as you need, you could create one for each context you work in. What is shines at is to coordinate and track project goals in teams.

http://listigator.com/

Lastly, I found, but have yet to try, Thinking Rock, a java application that is the first complete GTD system. It looks like a winner in its feature set and the paradigm seems to match Allen's system the best of any I've seen. TidBITs wrote about it in October, but there was, around that time, some issues with the server and then with the download itself, so I never got around to actually downloading a copy of it. It still sounds like a winner.

http://www.thinkingrock.com.au/
http://db.tidbits.com/article/8703

Behind the scenes, Thinking Rock maintains an XML file - a choice that I very much appreciate, since in an emergency any text processor can access your data. This file effectively describes a lightweight relational database, so it has the dimensionality necessary to implement a GTD list. ...

In the first screen (Collect Thoughts), you enter things you want to do ("thoughts") as they occur to you. The idea, though, is that this screen should never have contents for very long - no point hanging around the doorway! In the second screen (Process Thoughts), you categorize each thought, one at a time, and when you do, it automatically disappears from the list of thoughts in the first screen. That's because a processed thought is no longer a thought. It is now something else (an action or a project, or else a future item or an information item ...

Here's how you categorize a thought in the Process Thoughts screen (and observe that your options are remarkably faithful to the GTD Workflow paradigm):

• If you decide that a thought is actionable (it is a "thing to do," as it were), you describe the thought's outcome, so that you know what "completion" would mean; you give the thought a description; and you decide whether it can performed in a single step. If so, the thought becomes an "action;" if not, the thought becomes a "project." (So, an action is a doable thing; a project is a sequence of actions, and can contain sub-projects.) In the latter case, you'll eventually need to give the project some actions - cleverly, Thinking Rock creates an initial action reminding you to do this! Finally, you choose how to dispose of your action: postpone it ("Inactive"), mark it to be done as soon as possible ("ASAP"), assign it a due date, or delegate it to someone else. If you delegate, you can create an email message to ask the person to do it, and you can provide a date on which you should follow up to check whether it's been done.
• If you decide that a thought is not actionable, you can either delete it or postpone it into one of two categories, a "future item" or an "information item." Future items and information items can be revisited at any time in screens of their own; they appear as simple lists, and if at some point you decide that such an item is now actionable, you can move it back to the "process thoughts" wizard and reprocess it. This approach - which is one of unabashed procrastination - is in line with the GTD philosophy, where (as "bsag" has well expressed it) "[you] capture everything you have on your mind in a safe place, and thus stop subconsciously worrying about it [even if it] might not come into play until some time later."

The rest is pretty typical to the other GTD systems I have tried out or read about, but the process that Thinking Rock uses for capturing thoughts, to clear them from your mind, is what sold me when I read about it. I really have to get this set up on my laptop.

Thank for the links to other GTD scripts in this script. I'm working on a GTD type of project my self and I need to know as much as I can about others. I already downloaded Tracks and seem super fast and nice.

Thanx
Andrei O.