Open bubonicfred opened 3 years ago
I've also built something slightly similar, although called do.md
. I built a web frontend that uses isomorphic-git to pull the repo containing the tasks from git. My use case is slightly different, it's a general purpose task manager inspired by todo.txt but with markdown. I'd definitely be open to aligning on a single spec shared between this project and the todo-md project.
@ngduc Is it crazy to aim for interoperability between these projects?
@bubonicfred @chmac Thanks for reaching out! Yes, we should have the same spec, something that users are already familiar with other systems. Just like icons, users don't have to re-learn when they see a Todo markdown syntax.
would love to discuss more to have some common spec.
I would love so much to see a spec for that. It would be a very good way to make bugtracker materials exportable (between github, gitlab, gitea...)
@ngduc Awesome, really happy that you're also open to finding a shared spec that allows for interoperability.
At @GenerousLabs we're working on other projects with git + markdown, and also collaborating with other projects hoping to achieve interoperability in the git + markdown space.
Is it too much to host this shared todo list markdown specification within that context?
If not, I've started a repo and posted an issue to discuss a todos in markdown shared spec.
I am adding https://github.com/HelloLudger/todo.md-Peggy-Grammar to the list of similar projects.
I am not trying to build a third standard, I want to formalize what todo.md
and todo-md
have done.
I am currently building a cli tool for todo.md and was wondering if a merge of the organizations is still wanted? I'm not sure what it would take but surely, this would help the spec immensely and I'm willing to help where possible. For the sake of awareness, I'll post this comment on both (are there more?) issues.
FYI there's a similar project over at https://github.com/todo-md/todo-md/ Idk how compatible it is, but it would be nice to have a single spec.