I’m pleased to say that the project has now fully migrated management of all repositories
from GitHub to Codeberg. The main BookStack project repository now lives here:
It’s an improvement but I hate that we’re trading one centralized singlepoint of failure to another. It’s fine for people to be fleeing there temporarily as refugees from github, but I’m afraid that if it becomes “the one and only destination” it’s going to end up getting way too comfortable really fast. What we really need is a federated architecture, where it doesn’t matter who’s actually hosting the repository as long as they support the proper standards and protocols as part of the same federated universe where your own user or self-hosted instance exists, you can still be granted access to other people’s repos, report issues, send PRs to it, without needing dozens of accounts on dozens of self-hosted Forgejos for each individual project. They’re working on those features with Forgejo, and that’s awesome. But if everyone just moves straight to Codeberg, the incentive for that largely goes away, and even if they do end up implementing it, the incentive to improve and maintain it goes away, and there’s no reason we can’t end up with Codeberg being the new Github people are trying to escape from in 5, 10, 20 years.
So “getting bought” or having to “please investors” seems less likely.
We need federation and open standards, 100% agree. GitHub, GitLab, Bitbucket, etc are on the opposite side of that mission. SourceHut’s answer to federation is email… which I think most people will not like.
I’d love to hear about a source forge that is:
non-commercial, non-VC backed to avoid enshittification
FLOSS, self-hostable
has federation today (or is even open to working on federation)
doesn’t have awkward federation UX (like email)
No, really, I’d like to know. Codeberg is the only I know that approximates that list.
Waffling on moving to Codeberg because it’s not 100% perfect means supporting GitHub and drops the possibility of federated forges to 0%. Moving to Codeberg makes the future of federated forges go up to greater than 0%.
Waffling on moving to Codeberg because it’s not 100% perfect means supporting GitHub and drops the possibility of federated forges to 0%. Moving to Codeberg makes the future of federated forges go up to greater than 0%.
Fair, but there’s a third path that exists: spin up your own instance. Yeah, it’s more administration work, yeah it’s significantly more painful for contributors to contribute for now. But the more stand-alone, non-federated, community-operated forges are out there, the more appealing the federation glue needed to connect them all together becomes.
It’s an improvement but I hate that we’re trading one centralized singlepoint of failure to another. It’s fine for people to be fleeing there temporarily as refugees from github, but I’m afraid that if it becomes “the one and only destination” it’s going to end up getting way too comfortable really fast. What we really need is a federated architecture, where it doesn’t matter who’s actually hosting the repository as long as they support the proper standards and protocols as part of the same federated universe where your own user or self-hosted instance exists, you can still be granted access to other people’s repos, report issues, send PRs to it, without needing dozens of accounts on dozens of self-hosted Forgejos for each individual project. They’re working on those features with Forgejo, and that’s awesome. But if everyone just moves straight to Codeberg, the incentive for that largely goes away, and even if they do end up implementing it, the incentive to improve and maintain it goes away, and there’s no reason we can’t end up with Codeberg being the new Github people are trying to escape from in 5, 10, 20 years.
Yeah, 100% agree.
While not the ideal right now, I think Codeberg shows promise.
They’re working on federation: https://codeberg.org/forgejo-contrib/federation
Although, sure, it doesn’t seem to be their #1 priority. However, compared to GitHub this is a great step.
Also, again compared to GitHub or GitLab, Codeberg gives me more confidence because they don’t seem to be a commercial organization: https://docs.codeberg.org/getting-started/what-is-codeberg/#what-is-codeberg-e.v.?
So “getting bought” or having to “please investors” seems less likely.
We need federation and open standards, 100% agree. GitHub, GitLab, Bitbucket, etc are on the opposite side of that mission. SourceHut’s answer to federation is email… which I think most people will not like.
I’d love to hear about a source forge that is:
No, really, I’d like to know. Codeberg is the only I know that approximates that list.
Waffling on moving to Codeberg because it’s not 100% perfect means supporting GitHub and drops the possibility of federated forges to 0%. Moving to Codeberg makes the future of federated forges go up to greater than 0%.
Fair, but there’s a third path that exists: spin up your own instance. Yeah, it’s more administration work, yeah it’s significantly more painful for contributors to contribute for now. But the more stand-alone, non-federated, community-operated forges are out there, the more appealing the federation glue needed to connect them all together becomes.
Exactly, it’s only an improvement until they’re bought and we’re all in the same boat again. We need a federated forge and open standards.
Codeberg is operated by a German registered chairty foundation - the can’t legally be bought at all.
Radicle exists.