I've written myself a few scripts to integrate it with IkiWiki, so that I can use it as a combined task manager and sort of mindmap for projects. That is, each project has a wiki page, where I can write notes about the project, add links to useful references, etc. The scripts are used to list the tasks for the project on the project page, by using a few other IkiWiki plugins.
For the GTD system, I use taskwarrior's tags as GTD contexts. So I have tags like "phone", "shop", "home", "code", "internet" etc.
Aside from that, I've divided my tasks into three types, each one with a different alias which uses a different taskrc file. 1. ordinary tasks (no alias, just use "task") 2. writing tasks (aliased to "writing") 3. reading list (aliases to "reading")
The reason I split them is that I realized that I had so many writing projects that it was better to treat them separately, and once I'd set up things for that, I realized that I could also use task to keep track of my reading.
I was already doing a reading list on my site, but I kept on forgetting to keep it up to date. Treading my reading list as a set of tasks with taskwarrior made it a lot easier to keep updated. Buy/borrow a new book -> add a new task. Start reading a book -> mark the task as started. Finish reading a book -> mark the task as done. With the reading list, each book is a project; that allows for re-reading books, which is half the reason for buying them. Then I can see what books I've read by going "reading complete", and what books I've yet to read by just going "reading". Hmmm, I wonder if I should use tags on the reading list to tag books by genre, since there's no point in doing GTD contexts for reading, since they would all have the same context: reading! Yes, I think I'll do that. That will help me look for what book to read next, depending on what mood I'm in. Look, you say? Well, there's 199 tasks on my reading list...
no subject
For the GTD system, I use taskwarrior's tags as GTD contexts. So I have tags like "phone", "shop", "home", "code", "internet" etc.
Aside from that, I've divided my tasks into three types, each one with a different alias which uses a different taskrc file.
1. ordinary tasks (no alias, just use "task")
2. writing tasks (aliased to "writing")
3. reading list (aliases to "reading")
The reason I split them is that I realized that I had so many writing projects that it was better to treat them separately, and once I'd set up things for that, I realized that I could also use task to keep track of my reading.
I was already doing a reading list on my site, but I kept on forgetting to keep it up to date. Treading my reading list as a set of tasks with taskwarrior made it a lot easier to keep updated. Buy/borrow a new book -> add a new task. Start reading a book -> mark the task as started. Finish reading a book -> mark the task as done. With the reading list, each book is a project; that allows for re-reading books, which is half the reason for buying them. Then I can see what books I've read by going "reading complete", and what books I've yet to read by just going "reading". Hmmm, I wonder if I should use tags on the reading list to tag books by genre, since there's no point in doing GTD contexts for reading, since they would all have the same context: reading! Yes, I think I'll do that. That will help me look for what book to read next, depending on what mood I'm in. Look, you say? Well, there's 199 tasks on my reading list...