srid
NOW and FUTURE
Gist of the idea
Chronicle records moments over time. But we need to model the following as well:
- Working memory (aka. NOW) – what is currently going on
- Upcoming things (aka. FUTURE) – what are the things to be done in near future
I have a note file called "working memory" where I dump a short list of things I'm currently working through, be they projects, ideas or scratch notes. This can be modelled as NOW.
Likewise, FUTURE should represent the list of tasks, ideas to pick from when populating the NOW.
NOW and FUTURE, along with moments, ultimately affect the memories (and stories) ... hence there relevance to Chronicle.
NIH
Don't reinvent things, like GTD. For NOW support 'source plugins' - such as currently assigned issues in GitHub. Likewise, FUTURE would display unassigned issues in GitHub. Custom notes may also be added, possibly integrating with OneNote. Reminders are managed in Google Calendar.
Managing news and emails
News and email come briefly into NOW, and then get delegated into FUTURE. How do we model this?
...
Moreover should I do this? Or keep Chronicle simple?
