When Governance Meets Code: Why Developers Are Reevaluating Their Hosts

The Dutch Ministry of the Interior’s decision to migrate its government source code from GitHub to Forgejo has sparked a debate about the role of proprietary hosting platforms in software development. This story highlights a deeper issue: the tension between governance and autonomy in the digital age.

Developers have long advocated for control over their own code, a principle that underlies open-source software. However, platform-as-a-service (PaaS) providers like GitHub have blurred the lines between ownership and access. When you push code to GitHub, you’re not only hosting your project but also subjecting it to Microsoft’s AI organization.

Recent outages at GitHub were well-documented, but they are a symptom of a larger problem: the platform’s increasing reliance on artificial intelligence (AI) to drive growth. The CTO’s apology and promise to scale capacity 30x provided temporary relief, but did little to address the fundamental issue of ownership.

The Dutch government’s decision to abandon GitHub in favor of Forgejo sends a clear message: developers should have agency over their projects, and proprietary platforms like GitHub no longer meet that requirement. This move is particularly significant because it asserts sovereignty over code, which is essential for digital governance.

For individual developers, opting out of AI-driven features is not enough to ensure autonomy. The recent Copilot Free, Pro, and Pro+ user-interaction data opt-in debacle demonstrates how default settings can have profound implications. By making AI training the default, GitHub has effectively surrendered control over its users’ code to Microsoft’s AI organization.

This development raises critical questions about jurisdictional risks under FISA Section 702 and the CLOUD Act. If a US-based company like Microsoft is storing EU data on its servers, does that data remain vulnerable to silent access by US government agencies? The uncertainty surrounding this issue underscores the importance of developers taking control over their own code.

GitHub’s future path remains uncertain: will it continue down the path of AI-driven growth, sacrificing autonomy for scale, or will it pivot towards a more open and transparent approach, one that prioritizes developer agency over proprietary interests?

As developers, we must be vigilant in our pursuit of digital autonomy. The decision to migrate from GitHub to Forgejo is a crucial step towards reclaiming control over our own code. By choosing open-source alternatives like Forgejo, we’re not only safeguarding our projects but also sending a powerful message about the values that matter most in software development.

This is not just about GitHub or Microsoft; it’s about the future of digital governance. As developers, we have a responsibility to ensure that our code is governed by principles of transparency, accountability, and autonomy. The Dutch government’s decision to abandon GitHub may seem like a small victory, but it’s a crucial step towards building a more sovereign digital landscape.

Forgejo’s emergence as an open-source alternative has sparked a necessary conversation about the role of proprietary platforms in software development. As developers, we must be prepared to challenge the status quo and fight for our right to control our own code. The stakes are high, but so is the reward: a future where developers have agency over their projects, and digital governance is guided by principles of transparency and autonomy.

Ultimately, it’s not about whether GitHub will survive or thrive; it’s about what values we want to uphold in software development. Do we prioritize convenience and scale over ownership and control, or do we stand up for our right to govern our own code? The choice is ours.