Introduction
In June 2025, GNU Guix took a significant leap by migrating to Codeberg for source code hosting, issue tracking, and pull requests. This transition, far from trivial, profoundly altered the contribution dynamics for a project with more than 400 active contributors each year. After over a decade on Savannah, the choice of Codeberg sparked debates and expectations. One year later, what lessons have been learned from this migration?
Why Codeberg?
Choosing Codeberg over more popular platforms like GitHub or GitLab was not an obvious decision. As a free forge, Codeberg offered an attractive alternative for those prioritizing open source and transparency. Moreover, the respect for privacy and the absence of user tracking were compelling arguments for the Guix community.
Another decisive factor was the desire to reduce dependency on proprietary and centralized solutions. With Codeberg, Guix found a balance between modernity and ethics, a crucial aspect for its members.
Challenges of the Migration
The transition to Codeberg was not without challenges. One of the main obstacles was adapting contributors accustomed to an email-based workflow. This workflow, although considered archaic by some, offered formidable efficiency thanks to customized tools like Emacs.
The collective decision-making process, adopted in 2024 with the Guix Consensus Document (GCD), played a vital role. This process allowed for the collection and synthesis of community opinions, thus avoiding unilateral decisions.
One Year Later: Assessment and Perspectives
One year later, the assessment is generally positive. Codeberg has enabled better integration of new contributors, familiar with pull requests and a user-friendly web interface. The results of the January 2025 user survey, conducted with 900 participants, confirmed that the new workflow was perceived as more accessible.
However, some still miss the flexibility of the previous system. The community continues to refine its tools to maximize the benefits of Codeberg while preserving what worked before.
Conclusion
The migration to Codeberg was a bold but necessary gamble for Guix. It demonstrates how a project can evolve while remaining true to its values. The Guix experience might inspire other open-source projects considering a similar transition.
Let's discuss your project in 15 minutes.