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.
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.