BookStack completed its migration to Codeberg after a staged readiness plan, driven by GitHub’s AI pivot, Microsoft ownership concerns, and LFS access issues.
Key Takeaways
The migration was phased: secondary repos moved first to Codeberg, GitHub originals archived with redirect links, then the main repo followed.
Core concerns: GitHub’s consumption of public code for AI training without opt-in, UX degraded in favor of AI features, and GitHub rebranding itself as “The AI-powered developer platform.”
Concrete friction included LFS bandwidth limits being temporarily revoked on public repos with no apparent user control.
GitHub dependencies catalogued before migration: 6 active repos, GitHub Actions CI, GitHub Sponsors income, Crowdin and Codeclimate integrations, Composer package resolution, and community watchers using GitHub release hooks.
GitHub Sponsors represented significant maintainer income, making the financial decoupling a real cost, not just a hosting swap.
Hacker News Comment Review
The dominant skeptical take: BookStack had no major concrete incident with GitHub, and moving to a less-trafficked forge like Codeberg reduces discoverability and contributor surface area.
Commenters questioned the news value of individual project migrations, suggesting the story is only meaningful if it signals a broader OSS forge shift rather than one maintainer’s preference.
One commenter framed the split as ideological camp-sorting rather than a technical or governance decision, pointing to social platform choice as the clearest signal.
Notable Comments
@calpaterson: argues no concrete GitHub harm occurred and reduced forge visibility is the real cost; “I probably would not have gone with it if it had not be hosted on Github.”
@ursuscamp: “OSS is increasingly bisecting into two camps” based on whether developers use X or Mastodon/Bluesky.
