Git itself is already capable of distributed usage, which is better than federated/decentralized.
‘Distributed’ and ‘decentralized’ in this sense:
But in terms of the Git hosting service, with an issue board and all that, which is often called a “git forge”, you’ve got Forgejo working on an implementation, as well as ForgeFed as a general protocol (also work-in-progress).
It’s funny how git was carefully designed to be decentralized and resistant to failure from any single node… and we immediately put all our fault tolerance on the back of one corporate-owned entity. Welp.
Git itself is already capable of distributed usage, which is better than federated/decentralized.
‘Distributed’ and ‘decentralized’ in this sense:
But in terms of the Git hosting service, with an issue board and all that, which is often called a “git forge”, you’ve got Forgejo working on an implementation, as well as ForgeFed as a general protocol (also work-in-progress).
It’s funny how git was carefully designed to be decentralized and resistant to failure from any single node… and we immediately put all our fault tolerance on the back of one corporate-owned entity. Welp.