Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>
Clone
HTTPS:
git clone https://vervis.peers.community/repos/yEzqv
SSH:
git clone USERNAME@vervis.peers.community:yEzqv
Branches
Tags
possible-features.mdwn
- A context is a situation (condition) in which a task can be worked on. For example, a certain place (e.g. home) or a certain time of day (e.g. morning) or week (e.g. sunday). There are various context types (e.g. location, time) and contexts can be combined using OR and AND operators to form new contexts.
- The possibility to work on a task is also affected by dependencies. Tasks can depend on other tasks.
- Tasks can have a start time (when can start working on them) and a due time (when they must be already finished).
- Tasks can be considered automatic. An automatic task is just a combination of its dependencies, and it’s automatically closed/opened according to their completion status.
- Tasks can have a completion status that isn’t just binary open/closed. It can be a meter expression completion percentage. For automatic tasks, it can be computed automatically, but the contribution of each task to the percentage can be set. For manual tasks, it can be set manually. In addition to the meter, tasks can be canceled (plans changed, I won’t be doing this) and frozen (pretend it’s complete for now to hide from the list until I have time to work on it).
- Tasks can have an expected time needed to finish them. It can change / be changed in real time. It can be used to compute good work plans that have a short critical path.
- People can share tasks, send them to each other, have tasks depending on other people’s tasks. This is probably a complicated feature so I’ll go into details later if needed.
- A task has a short identifier code, a short title, a description and time of creation. Events are logged too: Time it became possible to work on (due to dependencies being finished etc.), time of completion, time of freeze and so on.