summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTobias Brox <tobias@redpill-linpro.com>2016-05-04 11:04:55 +0200
committerTobias Brox <tobias@redpill-linpro.com>2016-05-04 11:04:55 +0200
commita3699e7b8b7abbfbfa681e903946b138a9c04074 (patch)
tree9231953e0c8a2216f5ef3a59a8c88c1f5b81c60b
parent2b3fc35696843b83af5963125d0918ad9c492f2c (diff)
downloadcalendar-cli-a3699e7b8b7abbfbfa681e903946b138a9c04074.zip
revisited the task management document, based on practical experiences
-rw-r--r--TASK_MANAGEMENT.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/TASK_MANAGEMENT.md b/TASK_MANAGEMENT.md
index 4cd5b4b..d5c2e30 100644
--- a/TASK_MANAGEMENT.md
+++ b/TASK_MANAGEMENT.md
@@ -96,7 +96,7 @@ dtstart vs due vs duration
I my opinion, dtstart is the earliest time you expect to start working with the vtodo, or maybe the earliest time it's possible to start. Passing the dtstart doesn't mean you need to drop everything else and start working on the task immediately. You'd want to postpone the dtstart just to unclutter the todo-list.
-Due is the time/date when the task has to be completed, come hell or high water. It should probably not be postponed.
+Due is the time/date when the task has to be completed, come hell or high water. It should probably not be postponed. Due dates should probably be set very far in the future or not set at all. You really don't want the list of tasks that are soon due or even overdue to be cluttered up with stuff that can be procrastinated even further.
Different task list implementations may behave differently, most of them is probably only concerned with the due date.