Overview · docs

How do I collaborate on Radicle?

Radicle is designed for bazaar-style development. This means that there is no single canonical view (e.g. master) of any project, but multiple upstreams maintained by maintainers and contributors that exchange patches with each other.

Within the same project, two people will have subjective (and often diverging views), but your view of the project becomes the sum of all other views of the project. Conceptually, the project becomes decentralized among the many views of it's maintainers and contributors, instead of being confined to the control of a small group of people with read/write access.

In practice, this means that to fetch and receive changes from contributors, you have to add other people as remotes to your project. Adding someone as a remote automatically tracks them, giving you a way to continuously subscribe to the updates they make to your project (i.e. new commits).

You may be used to the concept of setting up an origin remote for a project when pushing to a centrally hosted platform like GitHub. This allows you to fetch and push changes from the server that hosts your project. In Radicle, remotes of other peers point to the Git monorepo on your machine that stores all of your Radicle data. These remotes allow you to fetch changes from your peers and publish your changes to the Radicle network. This means that fetching and pushing to remotes are local first actions. To read more about how Radicle is built on Git see our How it Works section.

The introduction of social coding features like bug reporting, patches, and code review will improve the process of finding and fetching changes between people on the network by making it easier to know those changes exist in the first place.

To help make this collaboration model easier to understand, here are some guides for answering some common questions we get on how to use Radicle:

For more help on using Radicle, be sure to join our community channels.