Last modification on 2022-07-01
This article describes a TODO application or workflow.
It works like this:
The text format I use is this:
[indendations]<symbol><SPACE><item text><NEWLINE>
Most of the time an item is just one line. This format is just a general guideline to keep the items somewhat structured.
Items are prefixed with a symbol.
I use an indendation with a TAB before an item to indicate item dependencies. The items can be nested.
For the prioritization I put the most important items and sections from the top to the bottom. These can be reshuffled as you wish of course.
To delete an item you remove the line. To archive an item you keep the line.
A section is a line which has no symbol. This is like a header to group items.
Checklist for releasing project 0.1:
- Test project with different compilers and check for warnings.
- Documentation:
- Proofread and make sure it matches all program behaviour.
- Run mandoc -Tlint on the man pages.
? Copy useful examples from the README file to the man page?
- Run testsuite and check for failures before release.
project 0.2:
? Investigate if feature mentioned by some user is worth adding.
ssh -t host 'ed TODO'
ssh host
tmux or tmux a
ed TODO
ssh host
tmux or tmux a
ed TODO
git add TODO
git commit -m 'TODO: update'
I hope this is inspirational or something,