[gnome-todo.wiki] Add more stuff

[Georges Basile Stavracas Neto <gbsneto src gnome org>]

commit 3af4ff921a9e52409a3a04408727f1a5bd096738
Author: Georges Basile Stavracas Neto <georges stavracas gmail com>
Date:   Wed Feb 24 22:07:49 2021 -0300

    Add more stuff

 Brainstorm.md | 14 ++++++++++
 Workflow.md   | 85 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 99 insertions(+)
---
diff --git a/Brainstorm.md b/Brainstorm.md
new file mode 100644
index 0000000..2022c4e
--- /dev/null
+++ b/Brainstorm.md
@@ -0,0 +1,14 @@
+Random ideas for GNOME To Do. There are absolutely no guarantees that any idea
+listed here will be implemented.
+
+### Data storage
+
+Evolution-Data-Server has served us well, but it feels dated and limiting. Seems
+a new backend made specially for GNOME To Do will be a better direction.
+
+Remove integration with external services (Google Tasks, NextCloud tasks, etc)
+in favour of importing tasks from these services, and online backups.
+
+### Local network synchronization
+
+Sharing data between devices in the local network sounds like a good idea.
diff --git a/Workflow.md b/Workflow.md
new file mode 100644
index 0000000..b340f1b
--- /dev/null
+++ b/Workflow.md
@@ -0,0 +1,85 @@
+Task management is extremely personal, and no method works for everyone. The
+same individual can even change their task management habits over time.
+
+As a personal task management application, GNOME To Do has a default workflow,
+but allows some degree of fine tuning.
+
+# Task lifecycle
+
+Tasks follow a lifecycle that consists of 3 phases:
+
+ * Capture
+ * Processing
+ * Execution
+
+Each phase changes the state of the task, starting from the uncaptured state,
+leading up to the task completion. The goal of GNOME To Do is cover all 3
+phases, and offer tools for people to process and execute tasks easily.
+
+## Phase 1: Capture
+
+Capturing a task is the act of storing the task in a permanent storage - your
+hard drive. Effective task capturing must be seamless and effortless.
+
+Traditionally, capturing is implemented as an entry that you input your task
+name and save it. I believe this is an innefficient way to capture tasks,
+because it requires you to switch to that application or browser tab, go to
+the entry, add the task, and switch back.
+
+Ideally, capturing a task shouldn't require switching apps, and should basically
+be instantaneous.
+
+One way to implement this ideal capturing is through a GNOME Shell extension
+that pops up a system dialog when a certain keyboard shortcut is pressed. ¹
+
+Captured tasks go to the inbox, which is the list of unprocessed tasks.
+
+
+## Phase 2: Processing
+
+Processing a task consists of moving it to an appropriate task list, or doing it
+right away if it's a trivial task, or even throwing it in the wastebasket if you
+don't plan on doing it.
+
+Optionally, adding more description, setting an end date, and marking it as
+important are done in this step.
+
+There's a variety of methods to process and organize tasks:
+
+ * Eisenhower matrix (urgent × important)
+ * Kanban board
+ * Tagging
+ * Gantt
+ * Dynamic lists
+ * …
+
+Ideally, GNOME To Do would offer many of these methods.
+
+
+## Phase 3: Executing
+
+Executing a task is what leads the task to its conclusion.
+
+GNOME To Do cannot control the task execution itself, but it can help easing
+execution in a variety of ways:
+
+ * Timers and time management tools 
+ * Reminders
+ * Automatic startup
+ * Neutral encouragement
+ * …
+
+Again, ideally, GNOME To Do would offer many of these methods.
+
+
+# High level planning
+
+TODO
+
+
+---
+
+¹ - A more ellegant solution would be negotiating a gloabl hotkey with the
+compositor that, when triggered, would open GNOME To Do in a minified mode with
+only the task capturing entry, and the window would hide after adding the task.
+However, this is not yet possible on Wayland compositors.