In the landscape of open source development, collaboration platforms like GitHub, GitLab, and Bitbucket have become synonymous with code hosting. These platforms provide a centralized model: Your repository data lives on their servers, access is controlled through their interfaces, and collaboration features are governed by their terms. Although this model has democratized contribution, it has also consolidated control, created single points of failure, and tied project governance to corporate entities. Radicle is code collaboration stack built on Git that reimagines the workflow by removing central servers. Instead of pushing code to a platform, developers host repositories locally and replicate them directly with peers over a secure, decentralized network. Radicle leverages Git's inherent distributed nature to its fullest, layering on a peer-to-peer replication protocol, a decentralized issue and patch tracking system, and a cryptographically secure social layer, all without relying on intermediaries.

By using a gossip protocol to propagate data, Radicle ensures that repositories are replicated across all interested peers, making the network resilient and transparent. This architecture offers a compelling alternative for communities prioritizing sovereignty, resilience, and openness. This article offers a practical introduction to Radicle. I will begin by elucidating its foundational concepts and contrasting them with the familiar centralized model. I will also guide you through installing the command-line client, initializing your identity, creating a project, and engaging in a full collaboration workflow, from submitting patches to code review. By the end, you will possess a functional understanding of Radicle's workflow and enough knowledge to integrate its decentralized approach into your own development practices.

Architecture and Key Concepts

The first thing to understand about Radicle is how it differs from client-server models. In platforms like GitHub, you interact with a canonical "remote" repository hosted on a central server. In Radicle, every participant maintains a full copy of the repositories they care about, and changes are shared directly among peers. This process is enabled by Radicle's custom networking layer, built on librad, which provides peer-to-peer discovery and replication.

[...]