#Godot is a big project hosted at Microsoft. If there is anything to the argument that smaller projects have to stick with Github to not lose contributors - doesn't that mean Godot has more freedom to leave?

Or, maybe ALL projects (big and small) just HAVE TO stay with Microsoft 🤷‍♂️ – somebody needs to tell Blender… they clearly didn't get that memo.

#GitHubIsMicrosoft #LeaveGithubAlready

@mray what is the course of action that you suggest? What are some examples of projects that do things better way?
I am aware of @openmw using GitLab as a primary repo, and just mirroring the commits to the GitHUb repo.
Even more standalone examples are KDE and Gnome, which host their own GitLab instances for their projects.
But that means you need to create multiple accounts in order to contribute to all of them.
#ForgeFed ( @forgejo being prime example?) is still being worked on.
@testman @openmw @forgejo Blender has its Gitea/or Forgejo? instance for example. I don't mind creating new accounts too much – if that means stuff isn't hosted in a Microsoft walled garden. There are alternatives to Github even today (ForgeFed will rock, too, of course). Not having to manage multiple accounts is a really bad reason to just go and tank the worst choice in my opinion. Unless you actually love depending on and supporting Microsoft.
@mray also I believe that the most popular #tag for this topic is #GiveUpGithub
https://sfconservancy.org/GiveUpGitHub/
Give Up GitHub - Software Freedom Conservancy

The Software Freedom Conservancy provides a non-profit home and services to Free, Libre and Open Source Software (FLOSS) projects.

@mray
is there already a solid version (out of concept state) of a federated git? like matrix or fediverse for git?

For me the most annoying thing is the identity problem at the moment, for example I would try to report bugs in vlc and gnome if I wouldn't need to create another account for each custom gitlab instance, sure most support sign in with gitlab/github, but that's still relying on these centralised organisations.

#git #federation #future #development #foss

@treefit https://forgefed.org/ is the attempt on a protocol level, and there is work under way to have a client that supports it: https://pad.nixnet.services/zrD-k_IASx2FSzG5yl1hxQ?view=#, also some people at gitea/forgejo seem to look into supporting the protocol in the future.
ForgeFed

About the Friendly Forge Format (F3)

The Friendly Forge Format (abbreviated F3) is an Open File Format for storing the information from a forge such as issues, pull/merge requests, milestones, release assets, etc. as well as the associated VCS (Git, Mercurial, etc.). Description F3 is designed to exchange the state of a software project between GitHub, GitLab, Gitea, etc. for backup, mirroring or federation. F3 is essential for a forge to provide key requirements: Portability: the entire state of a software project can be dum...

forgefriends