Right now my "default" is to go to GitHub, and then maybe GitLab and Codeberg...but that leaves out all the other hosts out there. Once #ForgeFed happens we'll need it even more :fedi:
(By the way, I say "git" because that's where most code is, but if other kinds of repos are supported, even better! 🔍 )
I added some basic #activitypub support to humungus based on the #forgefed vocabulary. Repository, Commit, etc. And of course updated #honk as well. So now you can follow the honk repo from within honk itself and see all the commits fly by. Still a work in progress, but it’s live now. Probably do a longer write up next week.
There is now an (intermediate) option for setting federated repos via UI.
Based on that we are currently developing the sending of activities to distribute stars to the federated repos.
We also noticed that there are some things to consider, regarding activity sending. Feel invited to share your thoughts on this. 🙂
Gitlab has a backlog item for enabling #ActivityPub support.
There isn't a lot of consistency in this stuff yet, don't know if they'll conform to what #ForgeFed is designing, or just aim for "can subscribe in Mastodon"
#mastodon#fediverse implementation question: would it be possible to use the protocol for carrying issue tracking & discussion, e.g. to make #distributed version of #github or #gitlab issue trackers?
I thought that technically these aren't that different from the usual discussion threads here, except maybe for some governance steps like deciding if the issue is closed etc... Perhaps someone already investigated?
@ChrSt@exa Yup, we're working on it! (I'm not a GitLab employee, but I'm the main contributor for it). Right now we're implementing following project releases from the Fediverse (subscribe to your favorite repos in your Mastodon interface, get notified when that project makes a new release). Cross-instance discussions, merge requests are the ultimate goal. It will take quite some time to get there, though. 😅
@forgejo is also working on it, hopefully both will be interoperable through #forgeFed (not entirely my call to make, but so far there has been no objection formulated)
ForgeFed nails the current dilemma in open source:
> Without federation, we end up having to choose between:
>
> * Centralizing into huge profit-oriented websites, where we're powerless
> * Hosting our code on a small website where we're in control and freedom but isolated from the community
Serious now. #Github is becoming a one-stop-shop for #development, that uses#FOSS to expand its dominant position. Gradually locking people in, with rich feature sets. Good #CodeForge alternatives exist, and can soon integrate with the #Fediverse via #ForgeFed protocol.
Weigh in on the discussion, add upvotes, emoji and feedback to:
This is an intriguing project. Reminds me of an idea I made some notes on a few years ago for using Git as the back-end for a decentralised policy collaboration platform.
Are you familiar with the #ForgeFed extensions to AP, for federating software forges?
@b0rk we mean, we don't think we should support the workflows of github.
specifically because it's github.
we should support competing workflows that don't revolve around the kernel either, and force github to adapt. ideally we should support federated workflows directly in the CLI and promote efforts such as #ForgeFed that way.
@xgqt@drj yeah, and #forgejo too. the #ForgeFed (https://forgefed.org/) stuff looks really interesting too: it makes sense to me that for distributed vcs, the quality of life features like bug tracking, code review and web interface should be distributed too. the dominance of gh in particular removes one of the main reasons git (and mercurial, bazaar, fossil, darcs, et al) chose to move away from the design of cvs/subversion
Not the "Build software better, together. Powerful collaboration, code review, and code management for open source and private projects." we signed up for years ago. (github's main page from webarchive).
A few weeks ago I asked about Fediverse apps that are as unlike as Mastodon as possible. People pointed me to some quite interesting ones, like playing chess over ActivityPub or public transport delay announcements https://social.coop/@J12t/110843539252937792
A slight correction: not for Forgejo. They are a project committed to implementing #ForgeFed, but @forgefed is intended to be an open standard for any software forge platform, including Gitlab.
@erlend Even better move would be to participate in forgefed.org/. I didn't see any mention within their issues. Looks like #GitLab is trying to build ActivityPub support where it can't fulfill the need. Even while there already are efforts to build upon it and extend for a forge based protocol #ForgeFed. Leading to still isolated software instead of distributed where I don't need additional wrapper and efforts.
I repeat: The way SourceHut supports participation via email is the best kind of federated implementation. Git & Email are already decentralized by design, so you already can participate even without an account on SourceHut. #ForgeFed
@fasterthanlime@refi64 This is a friendly reminder that there are alternatives to Github, which is free to apply whatever policy feels right for their business. Lookup #forgefed. Like @Codeberg for example.