My pace has been a bit slow due to some away-from-keyboard priorities, but work is happening!
I'm fixing the development builds in Vervis to allow people to build locally and work on UI.
Comment and ticket-opening federation is successful so far. The next thing I'll bring to the spec draft (and implement) is VCS commit notifications. Then, patches and merge requests.
@fr33domlover my coding skills are extremely limited, but I guess the first step would be to do a side-by-side comparison if which protocols #ForgeFed and Sr.ht are using for what, and how. Some elements of the aporoaches may already be compatible (like those using in-built #Git protocols), so it would be helpful to identify which ones are, and brainstorm some possible approaches to bridging those that aren't.
@strypey There's a lot to do before the actual coding part :) The very first step would be to *define* what it means to bridge the 2 systems, and write some use cases (e.g. Alice, who uses Sourcehut, wants to open an issue on Bob's repo, hosted in the ForgeFed fediverse, etc. etc.). Then, indeed we can compare how the systems work and figure out the technical details.
By the way, what is your motivation to build a bridge between ForgeFed and Sourcehut? And are you a user of the latter? Or any other forge? Just curious :)
@fr33domlover currently a user of various #GitLab instances (including the flagship), and occasional filer of bugs, feature requests etc on other forges. Interest in Sourcehut compatibility is motivated by a general desire to reduce fragmentation, and increase the #NetworkEffect of decentralized replacements for corporate #datafarms (in this case GH).
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!