#Trends

Software Freedom Conservancy Launches 'Give Up GitHub' Campaign

Trends Reporter
3 min read

The Software Freedom Conservancy has launched a campaign encouraging FOSS developers to abandon GitHub due to Microsoft's proprietary practices, Copilot's unlicensed training data, ICE contracts, and GitHub's vendor lock-in effects on the open source community.

The Software Freedom Conservancy has launched a campaign called "Give Up GitHub" that encourages Free and Open Source Software (FOSS) developers to abandon GitHub as their primary development platform. The campaign, which began in June 2022, highlights growing concerns about GitHub's transformation from a development tool into a proprietary ecosystem that contradicts the principles of software freedom.

The campaign argues that GitHub has created a powerful vendor lock-in effect, convincing developers that it's the only viable platform for FOSS development. This perception is particularly problematic because GitHub itself is proprietary, trade-secret software owned by Microsoft. The Conservancy points out that this creates a fundamental contradiction: developers who champion FOSS principles are building their projects on a platform that embodies the opposite values.

One of the central criticisms focuses on GitHub Copilot, Microsoft's AI-powered code completion tool. The Conservancy alleges that Copilot was trained on code from GitHub repositories, including projects licensed under copyleft licenses like the GNU General Public License. According to the campaign, Microsoft and GitHub have ignored the license requirements of these projects, including proper attribution and copyleft compliance. The campaign notes that GitHub's former CEO made statements claiming that the legal status of using licensed code for AI training is "settled," despite ongoing legal uncertainty about this practice.

Beyond the Copilot controversy, the campaign cites several other reasons for developers to consider alternatives. These include GitHub's contract with U.S. Immigration and Customs Enforcement (ICE), which has drawn criticism from activists and some GitHub employees. The Conservancy also points to GitHub's historical stance against copyleft licensing, noting that various GitHub executives have spoken negatively about copyleft and the GPL over the years.

The campaign acknowledges that leaving GitHub is difficult for many developers. GitHub has become deeply embedded in the software development ecosystem, serving as a discovery platform, portfolio showcase, and even a requirement in some Computer Science programs. The platform's network effects create a powerful gravitational pull that makes alternatives seem less viable.

To address these challenges, the Conservancy is taking a phased approach. They're calling on privileged developers—project leaders, hiring managers, and those with secure employment—to lead by example and move their projects to alternative platforms first. This "collective action" approach aims to create momentum that will make it easier for others to follow.

For those ready to make the transition, the campaign recommends several alternatives. For self-hosting, they suggest Forgejo, a community-driven fork of Gitea. For hosted services, they recommend Codeberg, which is built on Forgejo and operated as a non-profit. Other alternatives mentioned include SourceHut and GitLab Community Edition, though the campaign notes that GitLab's Enterprise Edition shares similar proprietary concerns to GitHub.

The campaign provides practical resources for developers at different stages of readiness. Those who aren't ready to leave GitHub entirely are encouraged to add informational sections to their README files explaining their concerns about the platform. The campaign also suggests asking project maintainers if they can provide alternative contribution methods before contributing to projects on GitHub.

To build community support, the Conservancy is promoting the campaign through social media using the hashtag #GiveUpGitHub and maintaining a mailing list for developers to share their experiences and challenges with leaving GitHub. They're also developing a growing list of resources to help developers navigate the transition.

The "Give Up GitHub" campaign represents a significant challenge to the current state of open source development infrastructure. While GitHub has become synonymous with open source collaboration for many developers, this campaign highlights the tension between using proprietary platforms for FOSS development and the philosophical principles that underpin the open source movement. Whether the campaign gains significant traction remains to be seen, but it has already sparked important conversations about the centralization of open source development and the long-term implications of relying on proprietary platforms for community-driven software projects.

The full campaign details and resources are available at GiveUpGitHub.org.

Comments

Loading comments...