KeepATaskLog (KATL). The idea is that the same fragment files that record you did something could be used for tasks.
Yet another "files in git is the database pattern"
This would be free because it is just static files that act as a GH client via PAT (and someday OAUTH), i.e. self hosting is hosting some static files.
https://matthewdeanmartin.github.io/keepachangelog-manager/board
Sort of like PEP350's code tags (TODO comments), but instead of quirky schema and "database is structured DSL in python comments", it is language neutral and piggybacks off the success of KACL (keepachangelog) as a semistandard.
♡ 0 ↻ 0I figure it would work well for handwritten code on side projects, works well with LLMs because it is yet another Markdown format.
If I were to ever make money with it, it would be to create a server component for $200 a month per n repos or something, because the ticket writer (a PM, PO or BA) doesn't want to deal with git. Also, without a server component, polyrepos are going to make project management feel scattered.
♡ 0 ↻ 0