RE: https://metalhead.club/@thomas/116301990188175266

2010: Let's make GitHub the new SourceForge! The default place for FLOSS code.  

2026: Let's make GitHub the new SourceForge! The awkward outdated cringe code hosting has-been.  

(but this time, ideally, we end up with many federated forges, one could hope!)

#FLOSS

@rysiek I read it as "move everything to Codeberg so we do the same error of centralizing everything, once more"
@bortzmeyer
I remember a story about some Forge, jo, and they wanted to federate.
Even GitLab reopened their ActivityPub issue, but progress is slow and the actual need for ForgeFed-edarion seems to be not so pressing, after all?
@rysiek
@yala @rysiek All my code is at Framagit and by far rhe most common complain I hear from people who wanted to contribute (bug report, pull requests, etc) is "I don't want to create yet another account and to have to use yet another forge".
So, yes, federation is very important.
@bortzmeyer git over email is so underrated...
And yet, it is federated by design, and sometimes even more efficient than some forges...
@yala @rysiek

@x_cli it's not just about git, it's often more about issues and other project management stuff.

@bortzmeyer @yala

@x_cli @bortzmeyer @yala @rysiek counterpoint: the last thing I want is more emails

@cinebox I'm pretty sure the issue is not with the medium and has more to do with the senders and the content xD

Now I would agree that receiving vibe-coded pull requests would certainly feel like receiving spam.

@bortzmeyer @yala @rysiek

The Disconnected Git Workflow

The Disconnected Git Workflow par Ploum - Lionel Dricot.

@ploum @x_cli @bortzmeyer @yala @rysiek And then you try to plug automation to it... And the entire thing falls apart.

This is why most freedesktop.org projects switched away from emails. Patchwork-fdo tried super to provide a consistent view of patch series to review + associated CI results, but emails are too unstructured to work reliably (not including the fact that many email providers tamper with patches).

But worse than this, there cannot be collaboration on a shared global state for the project: no shared list of open issues, no integrated CI,... People just have to read the every email and build a mental image of the whole project. This doesn't scale, and Linux proves it...

I am all for decentralisation and offline operations, but basing it on emails just doesn't work. When all you have is a hammer, everything looks like a nail I guess...

Signed, a Freedesktop.org admin who has been spending 5 years on bringing the i915 driver quality up (https://intel-gfx-ci.01.org/, https://patchwork.freedesktop.org/), then 5 years doing the same in userspace using gitlab. The former is a joke compared to Mesa CI.

Intel GFX CI

@x_cli

I disagree on one point : I am unable to manage git branches with git-sendmail.

@bortzmeyer @yala @rysiek

@tanavit Could you please explain in more details what you mean by "managing git branches"?

@x_cli

Suppose the main manager of a git repository proposes two branches (e.g. main and dev).
If I worked on the dev branch, the patch I will send does not have information about the branch I was working on, nor information about the official commit it applies to.

I may be wrong.

@tanavit It could be easily added to the cover letter, but AFAIK, you are correct that a "patch" (format-patch) won't contain that info by default.
git-request-pull is probably more suited for this?
@bortzmeyer @yala @rysiek Worse than having to create an account on some random GitLab instance is being asked to do it again because the one you had was deleted for not being used often enough.
@bortzmeyer
I know of two projects working on a federated git repos solution, one of them is @radicle.
Not tested though.
@yala @rysiek

@yala
I wanted to contribute to #garage S3 and they self host a forgejoe. It was a bit annoying having to create an account. It probably cost me two days before I opened an issue and my PR. It is just friction we need to solve.
@bortzmeyer @rysiek

Wrt codeberg and forgejoe, I'm wondering how actual development and independent feature contributions are compared to gitea.

@bortzmeyer that's another thing. Yes, we should absolutely avoid making the same mistake.
@rysiek it's a matter of time until the downloads on the releases page have a 15-second interstitial shilling Copilot for Business
@rysiek Self hosting is the only way forward nowadays. I always said it's a stupid, stupid, stupid, stupid idea to host anything like own repos in online service. You will never be able to guarantee it wont go the way of github. Same with cloud, helped quite a few small and medium businesses move away from cloud hosting after MS jacked up prices. AI is just another fecking helping of shite on top of that mess.
@rysiek but also "let's donate to @codeberg when we move there, because servers don't run on thoughts and prayers" 💶
@rysiek I think of it as "enshittifying themselves into oblivion"
SourceForge: copilot-cli

The world's largest development and download repository of Open Source code and applications