To contribute to another user's project, you must first find it on the network. To find a project, you need its Radicle ID. This can be found in the project page under the project name, or in a seed node dashboard such as seedling.radicle.xyz.
Once you have the Radicle ID, copy it into the Upstream search bar. From there, you can follow the project to track it. This will replicate it to your local machine once it's found in your network of connected peers. You won't see the project metadata — such as, the name of the project — until it is verified by the protocol.
To create your own view of a project, you can use the Fork option within the Upstream client. This will clone the project to a specified location on your local machine and publish your version to the Radicle network as a new project.
Forking a project will move it from the Following tab to the Projects
tab. This is because once you fork a project, you create your own view of
it that is unique to your Device ID. You can push changes to this view via
rad remote and publish them to the network. If another person has
added you as a remote (See Tracking & viewing contributions), they will be
able to fetch these changes and merge them into their branches (See Fetching
and merging contributions).
You are able to clone your project with the Checkout option on your project page.
Getting a contribution merged
Once you push changes to a fork of a project and they've been successfully published to the network, they can be replicated by other peers. For another peer (e.g. the maintainer of a project) to see your changes, they need to add you as a remote to their projects. This means that until social coding features are introduced, you'll have to manually communicate your patches to the maintainer of a project by sending them your Device ID. This can be done through email, a developer chat, or social media channel.
If you are a maintainer of a project, it is suggested that you provide a link to a channel for receiving contributor Device IDs.