And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic. I think we should be grateful that the core underlying protocol for the most important data has the distributed properties we want. It's a lot more than we can say vs. lots of other platforms out there.

As a GitHub user myself, I don’t disagree with your point. However I’d like to say that this isn’t quiet as different a problem to solve as it might first appear:

The issue tracking can be a branch and then you just need a compatible UI. In fact some git front ends do exactly this.

CI/CD does already exist in git via githooks. And you’re already better off using make/just/yarn/whatever for your scripts and rely as little on YAML as possible. It’s just a pity that githooks require users to set up each time so many people simply don’t bother.

> And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic.

That's how we started out.

Maybe that's the reason everything tends to get centralized.

It's an emergent phenomenon, it requires less energy expenditure overall. It's also the way of the Dodo.

By storing issues etc in the repo itself. A git repo is just a generic object graph, after all, and objects don't necessarily describe files.

There are several such solutions already. The problem is that neither of them is popular enough to become a de facto standard. And, of course, centralized git providers like GitHub have a vested interest in keeping in this way, so they are unlikely to support any such solution even if it does become popular enough.

Wouldn’t it make economic sense for a git host to emerge that just did things this way and collect big pay for it? Gits been around forever and you’re idea sounds simple enough that a market of people would probably choose it on principle. There must be something more fundamental at play here.

Right, but distributed git As Torvalds Intended™ doesn't solve those problems, so it's not related.

For the actual event we are commenting on, they have disabled all features other than code hosting and PRs.

It's impossible to disable PRs on GitHub, sadly. See https://github.com/dear-github/dear-github/issues/84

Interestingly mozilla has effectively done this here, by using a GitHub action that automatically closes any PR with a message explaining that PRs are not to be used.

It's very silly they have to do this, but at least they can I suppose.

GitHub is about the community. There are others alternatives, more in line with what Mozilla claim to be their view (I'm thinking to GitLab, for instance), but nothing gives you visibility like GitHub.

Sad to see that Mozilla is becoming less and less what they promised to be once Google funding are depleting.

GitHub has a fairly extensive API without too many limits AFAIK. You can definitely migrate all your data to $something_else if you want to.

I managed to move to codeberg all my projects. There's everything except the secret deals with pypi to directly publish from github. Which is massively insecure anyway.

Sure, but then we are no longer talking about git.