@virtualpierogi @sri @jsalvador @ben @michiel @nlnet

Yes, I've noticed that in #FOSS realms there's a rapid change to the development processes that are followed. Where projects no longer allow people to just contribute PR's.

In many github projects for instance you should first start a Discussion and get dev team's consent to create an Issue, which you may then create a PR for. Any other direct contributions are either disallowed or immediately closed.

There was also this Vouch reputation system that got popularity real quick. And there'll be more changes like that I think.

https://github.com/mitchellh/vouch

https://news.ycombinator.com/item?id=46930961

I've been looking at #ForgeFed and how it is set up. Currently it models very much the application model of what constitutes a typical "Code forge", but this is restrictive and going from lowest common denominator between forges. There's opportunity here to focus on the domain of "Software development" and the (social) coding processes between all stakeholders.

@virtualpierogi @sri @jsalvador @ben @nlnet

When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.

If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.

And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.

@thisismissem @eyeinthesky

I just responded in the other thread about #ForgeFed way of dealing with Issues and PR's, emphasizing the actor model in the #ActivityPub specs.

Guess it depends on the nature of your extension and its desired functionality how you model things, but ForgeFed chose to have a dedicated actor, a TicketTracker, to manage the collection. Big advantage is that it become a truly encapsulated service with its own business logic, fronted by an AP actor for interoperable network communication.

https://social.coop/@smallcircles/116096769625606025

@thisismissem @deadsuperhero

I was looking at #ForgeFed which is a very sizable #ActivityPub extension (constituting the "Code forge" app domain in app-centric view, but arguably "Software development" top-level business domain in a service-oriented fedi).

The way that things are modeled here adheres more to the actor model where there's a Factory actor, which in turn creates resource actors that expose various sub-domains. For instance for the management of Issues and PR's there's a TicketTracker actor to obtain via a Factory actor on a forge instance. Though I'm not sure whether I'd modeled that in similar fashion, it is a fascinating direction where we focus much more on good protocol extension design.

All in all AS/AP offers a very granular foundation that allows for very interesting architectures, if only we dare explore them and do not dogmatically stick to some engrained notion how "social media" ought to be. I see #SocialMedia as but a small subset of #SocialNetworking.

Another Microsoft #GitHub outage, another reminder that over half of the projects I use / contribute to are hosted on and exclusively available on this proprietary forge.
It's time to factor this into decisions whether to use software, points-- for GitHub.

Stuff I tried accessing today:
#NixOS nixpkgs repo (can't update my computer)
#Flathub manifests
#Niri wayland compositor
#Tauon music player

Would love to see more migrations to free forges, and excited for #ForgeFed to make this easier!

Are there any #forgefed people at #fosdem today? I’d like to pick your brains!

It seems like @forgefed's grant funding ran out and the entire project has just been left hanging, unfinished. This is a potentially important project, so this is really frustrating.

But really, anything important enough to get grant funding probably ought to keep going after the grant funding ends. Maybe grant-making orgs could provide some kind of support for projects transitioning out of funded work sprints, back into volunteer-driven coordination?

#ForgeFederation #ForgeFed #GrantMaking

稍微的探索了一下，发现现在的这个情况还不是特别明朗。

首先是这个#tangled 基于 at protocol，它分多部分组成，包括一个个人信息数据服务PDS，一个界面比如说bluesky或者tangled。其实自己最想host的部分其实就是自己的数据，包括发送的帖子，保存的图片等等。而如何利用PDS的数据库去展示一些信息，则是由这个界面控制的。所以如果想试试at protocol，最先建议入手的是自建PDS。

然后也稍微了解了一下基于activitypub的代码仓库。现在有一个activitypub协议的扩展叫#forgefed (https://forgefed.org/)，但是大家的开发都不是特别积极。其中#gitea 似乎完全没管，#forgejo 正在开发两年了，现在依然遥遥无期。偶然还了解到了gitea和forgejo的故事，原来是gitea在几年前想要开始搞商业化恰饭，导致一群人出走，fork了gitea创建了forgejo。有点像前一阵子alist和openlist的事情了。

还有另一个去中心化的git合作项目叫 #gitworkshop (https://gitworkshop.dev/)基于#nostr ，它似乎不负责托管代码，只是给不同的代码托管平台共享一些信息，比如说issue的讨论，pr等等。

了解了那么多，确实有点惊讶git如此一个去中心化设计的系统居然没有一个去中心化/联邦的平台activitypub的实现，目前也只有一个at protocol的tangled。

So much for the federated merge requests via #ActivityPub.

https://gitlab.com/groups/gitlab-org/-/epics/260#note_2910231358

When I called in https://lwn.net/Articles/963427/ @sir position as the pragmatic one, I was called disingenuous.

(And, BTW, https://codeberg.org/forgejo/forgejo/issues/9225 doesn’t seem to be finished either).

#GitLab #ForgeFed #SourceHut #Forgejo #Radicale

GitLab is dropping plans to pursue federation features like distributed merge requests. Sad, but not very surprising to me.

https://gitlab.com/groups/gitlab-org/-/epics/260#note_2910231358

However, @forgefed and related specifications are still a thing and @forgejo is still working on supporting that, see https://codeberg.org/forgejo-contrib/federation and https://forgefed.org/!

#forgefed #ForgeFederation #gitlab #forgejo #federatedGit #git

So, to my knowledge, there's nothing that does this yet, but it'll be solved in a very fediversey way soonish:

https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md#federated-repo-search-discovery

#forgefed #forgejo #forgejofederation

#Forgejo federation can't come fast enough for you? Have you ever wished to help out, but specifications are too scary and you don't know where to start?

In that case, I have the perfect task for you (yes, you!): https://codeberg.org/forgejo/forgejo/issues/9282

#ForgeFed #federation #Codeberg

Die @meissa erklärt und zeigt mal, was bei #forgejo in Sachen #federation schon so alles geht. Voll spannend für die Zukunft :blobcathearteyes: :fediverse:
https://media.ccc.de/v/froscon2025-3275-foderiertes_forgejo

#froscon2025 #codeberg #github #gitlab #gitea #go #git #forgefed #activitypub #fediverse

The reason why I keep a mirror of xtream on #GitHub is because I suspect their users won't bother creating an account on #Codeberg in order to open an issue, so they have that option.

So the #ForgeFed project working on a federated #Forgejo is a nice thing that could solve that. I'm not sure if GitHub would ever federate, though...

Forgejo Federation (#ForgeFed):

« It's a bit like e-mail, except the data sent is JSON objects (i.e. structured computer-readable data), and not only humans have inboxes where they can be contacted, but also repositories and issue trackers have inboxes through which they can be remotely and safely interacted with. »

https://forgefed.org
6/4

@forgejo My personal highlight of this release: You can now use your #fediverse handle in #markdown documents and it will be marked up as a link to your user profile (or group, etc.).
https://forgejo.org/2025-07-release-v12-0/#redirecting-fediverse-handles
I'm excited about the future, when mentioning fediverse handles will actually be federated and will send notifications everywhere!
#Forgejo #Federation #forgefed

okies, decided, today's the day... gonna start moving my repositories to codeberg... notabug.org's too consistently inconsistently available. n_n a little sad. mmmmmmuch fondness for notabug.org. ... i wonder, if i leave the repository off the end of the url in codeberg's migration tool... does it allow migrating everything in one go? :3

or should i skip codeberg, and go full forgejo? :)

#git #githosting #gitforge #notabug #codeberg #forgejo #forgefed

Crisis averted, #GitLab reopened the epic on #ActivityPub / #ForgeFed implementation. :)

They made it clear, though, that they're not going to do it themselves in any foreseeable future, their "current focus isn't in this area", so it's up to the community to implement it. As I mentioned in the issue, I won't be able to come back to it until I'm done bootstraping the business I'm working on, so anyone who wants to see it done faster should feel free to jump in.

https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2603598572

press F to pay respects for #ForgeFed federation in #GitLab

https://gitlab.com/gitlab-org/gitlab/-/issues/30672#note_2597293301