Skip to content

Latest commit

 

History

History
81 lines (80 loc) · 3.86 KB

TODO.md

File metadata and controls

81 lines (80 loc) · 3.86 KB
Raw

TODO. A backlog of ideas

  • No need for editable habit lines
    • A journal suffices for that and doesn't have any shenanigans
    • Implement a migration and then remove it altogether
  • Observation-Event migration
    • Migrate observations to have their own ObservationMade/ObservationClosed events
    • Remove date_closed on observations
    • Fix event_stream_id on habittracked
      • Implement signals event_stream_id saving on change etc for JournalAdded, HabitTracked...
    • Drop closed observations (migration + replace view in code)
    • Add event_stream_id page showing for example, past observations
    • Check if migrations are really reversible
  • Bring back tasks view
  • Quick notes
    • Can add via mobile (URL: /q, for example)
    • Removed after 24 hours
      • Add autoreload for celery
      • Use standard Python images for celery
      • Celery does not need to wait on PostgreSQL
    • Can be put into a journal comment as list of points quote before comment section
  • Move tools from random-tools to tasks-collector-tools
  • Bug: Habits tracked on journal save have no event set to published of the journal
  • Add taskadd Inbox
    • Add ability to go to /todo/#board=board
  • Allow for archiving (leave delete)
  • Oftentimes, tasks are not loaded, when working on multiple tabs
    • use window.onfocus to reload tasks
  • Add a special symbol in journal to add a line to a reflection
    • Symbols: [x] [~] [^]
    • How about [ ] for Plan?
      • Need to rethink that / possible to use other input method
  • Add a Journal archive view set
    • Add an event archive view set
    • Remove add_published from templatetags
    • Check #253 – is ObservationMade done here?
  • a weekly report could list out count and a summary of all items as email (for example)
    • Add ell and personality cores to summary
  • Add journal to the today view
  • Add tasks-collector.ini to the project and set it up with a dummy password for development (done in https://github.com/dragonee/tasks-collector-tools)
  • add pub_date to events and allow for setting different day (yesterday) than now for events affecting a specific date (e.g. HabitsTracked)
  • Add post-it boards for ideas
    • Use the tasks backend
    • Add another view (with two components – a "shelf" and a "board")
    • Put things from shelf to board
      • Coordinates update
    • Put things back from board to shelf
      • Coordinates remove
    • ability to move board around
  • Observation Closed History View
    • Merge View
    • Event timeline component
    • Better styling
  • Habit summaries
    • Quick summary - since / from
    • Lines (days)
    • Calendar
  • Remove empty plans/reflections (these should not save)
  • Dump database before automatic migration / deployment
  • Quests: merge them with journals
    • (draft) Use journal for journalling, and quest object as a side to it
      • JournalQuestMeta: quest_id, journal_id, stage
      • where to differentiate logic for stage: Null?
  • Ability to create a task on Google Tasks API from the board
  • Implement $ on tasks, so that only part of information is shown on the task list, all can be edited
  • Make events out of reflections and plans
    • A single event suffices?
    • Add autocommit mechanism
      • Remove on autocommit?
    • Add manual commit
  • Habits – shift around
    • Add slug field
    • Define a list of habits I'd like to track
    • Possible integrations:
      • Internal with events
      • External with GH API
  • Add Expectation model to Habit to track redline/greenline, goal, etc.
  • Add a description to Habit