but seriously, we need project management features that are decentralized: issue tracking, kanban, code reviews w/ comments, and ways to extend functionality without relying on a git forge.
You could create a git branch with an unrelated history to store this type of data; either as plaintext, md or something more sophisticated for dedicated tools. The biggest hurdle would probably be to define and agree on a standardized format
The last thing I want is merge conflicts in my issue tracker. The git data model is simply not right for conversational histories.
ActivityPub is the obvious solution to decentralize public communication. We’re using it right now and AFAIK Forgejo is working to implement it for their issue tracker.
but seriously, we need project management features that are decentralized: issue tracking, kanban, code reviews w/ comments, and ways to extend functionality without relying on a git forge.
For issues tracking there’s the venerable git-bug, although development has sadly slowed way down in the last years.
And I am always jealous of the way fossil repositories just have a complete front-end and wiki baked in, would love something like that for git.
Would be cool to see those as extensions to Git. Surely they could just be more Git objects?
I wonder how exactly Forgejo’s planned federation will work…
Oh god kanban
You could create a git branch with an unrelated history to store this type of data; either as plaintext, md or something more sophisticated for dedicated tools. The biggest hurdle would probably be to define and agree on a standardized format
The last thing I want is merge conflicts in my issue tracker. The git data model is simply not right for conversational histories.
ActivityPub is the obvious solution to decentralize public communication. We’re using it right now and AFAIK Forgejo is working to implement it for their issue tracker.
Snd with relying on cloudflare