@nasser I think email chains would be fine if there were more standard views over top of them TBH.
Why not use https://radicle.dev/ instead of making another standard? 😅
@mauve I'm working on something I think is different and simpler. bottoms out in a crdt file per issue/merge request/ticket that gets stored into the repo and reuses existing hosted repository infrastructure for distribution. ie you should be able to use codeberg while I use source hut and we should be able to collaborate. the tool opens a local server that presents a web interface. it's more like git bug than anything.
radicle as far as I understand had a more involved bespoke p2p protocols with seeder nodes, which isn't what I'm getting at.
@nasser I like that! Whatcha gonna do for access control? are you gonna add a hook to automatically fix confflicts in the crdt file when someone does a pull/merge? Are the forge crdts going to be in their own branch? I'm guessing p2p nuts can just add a p2p remote to pull/push to if they want to sync with others.
@mauve yeah it's the main missing piece. email chains aren't the answer. I'm prototyping something based on automerge that runs locally that I think has some promise.