Comment by keyle

Let's call it pretty open... I couldn't find one either, years ago, so I kind of went with what works for me.

Note that plan files aren't exactly a micro-blogging platform like some people seem to refer it to as. To me anyway, it's a way to capture work and todos in a simple digital journal.

This is the standard I followed for myself...

   This is a rolling plan file where things get moved on completion against a specific date (no backtracking, sliding tasks)

   - is todo
   * is done (for grepping)

   bugs are tagged [bug]
   other tags can be use as [tag]
   ~~is a cancelled~~ task or bug
   // is a comment or thought
   @next is upcoming work
   @later is backlog

   if it is not done, it's in next, later or ~~cancelled~~

   date is YYYY-MM-DDD followed by a rough recorded timesheet
   :0000-0000-XXm as in :start-end military time -minus XX mins of AFK.
   timesheet that is parsable by another program to get time spent /week /month /total

For example...

   ### 2021-01-10-sun :0900-2100-50m

   * ditched ~~passport~~ [wtf]
   * auth via bcrypt and jwt tokens
   * new vue app, trying water.css - nice [noteworthy]
   * JSDoc is awesome, makes typescript a lot less needed [noteworthy]
   * sign in with email / pass against db
   * register against db (not in vue yet)
   * validating jwt tokens properly
   * clean up package.json

Note that none of this is a replacement for actually doing the work ;)

http://programming-motherfucker.com