Suddenly pondering whether tracking my todo list in fossil is a reasonable thing to do, or just too danged geeky... I could see it being useful for documenting those tasks that don't go as planned (e.g. every #$%&* house project).

@cstanhope That was a consideration for me, among others, as I am phasing out my GitLab instance, but wanted to do something useful, if not trendy, for tracking tasks.

But stepping back and just needing a todo list, I started using taskwarrior (documented at, and it does everything I wanted from anything. I am currently committed to using it on the one computer. I am getting things done. ^_^

@maiki Yeah, I've used task warrior in the past with some success. I'm a sucker for a good CLI. I even went to the trouble of creating some helper scripts that made it easier for me to use taskwarrior as a bug tracker for some personal projects. I placed separate taskwarrior directories in each repo. Maybe I should go back to using it. 🤔

@maiki I just ran "task" for the first time in a while. I apparently stopped using it about 4 years ago (according to the date on some of the tasks). That's right around the time certain important things happened in my life. It's weird to find reminders to events in my own life scattered around in my personal metadata that I stir up occasionally.

@cstanhope @maiki What made you unhappy with the fossil strategy out of curiosity?

Largely because I currently use todo.txt / had looked a bit at taskwarrior and was thinking of migrating to a fossil repo.

@cstanhope Sorry I mostly meant you. I get why @maiki left his GitLab instance.

@trashHeap After playing with my old taskwarrior list this morning, I think I will try fossil for my use case. [I had stepped away from fossil a while back in order to force myself to learn git, which is why I had (ab)used taskwarrior as a bug tracker.]

I think the issue system combined with the wiki might be a good combination. I might even be able to share the list with my spouse. But first thing first. :)

I have most recently been using org-mode, so we'll see how this goes.

Update: Using fossil this way is kind of working. The fossil ticket workflow is not really optimized for this use, of course. But the database system is flexible enough that I've been able to customize the schema into something workable for TODOs. I guess I'll have to use it for a while to see how it holds up.

And now I realize fossil is available under termux, and it is recent (2.7) unlike the version in Fedora (2.2). The web ui will be a bit awkward, but it is usable. Now I can feel the pressure of my ever growing todo list no matter where I go! How useful!

Sign in to participate in the conversation is a a coop-run corner of the fediverse, a cooperative and transparent approach to operating a social platform. We are currently closed to new memberships while we improve our internal processes and policies, and plan to re-open to new folks when that work is complete. [9/2/2018]