We are always happy to meet new people in the project. For details on the onboarding process, see below.
We appreciate help in testing on various OSes and hardware, and highly depend on feedback from users. If you wish to test, you can look for tutorials on publications page.
If you’ve built Roc for a niche OS or hardware, or tweaked settings to make it work better for your needs, or used it in your project, we’d love if you share your experience with the community. If you wrote a post, you can send it to us to be added to the publications page.
First of all, thank you for your interest! We welcome and appreciate all help. Many important features were submitted by numerous contributors, and we are really grateful for that.
In case of any questions, welcome to join our chat and mailing list.
The guide bellow will help you to prepare your first patch.
Step 1: Checkout and build project
Build instructions can be found here:
Step 2: Get introduced to project internals
Take a look at documentation of project internals.
There is also Doxygen-generated documentation for internal modules.
Step 3: Learn coding guidelines
Please refer to this page: Coding guidelines.
Step 4: Choose a task
Tasks needing assistance are marked with “help wanted” label. These tasks usually come with detailed explanations and are suitable for newcomers.
Some of these tasks are also labeled as “easy hacks”. It indicates that the solution is expected to be pretty straightforward, making them a good entry point to the project.
Extra labels make it easier to find various kinds of problems, like “tests,” “refactoring,” “algorithms,” “networking,” and so on.
When you pick a task, please leave a comment to let others know so that we don’t end up with multiple people doing the same thing. If a task hasn’t been assigned, it usually means no one is currently working on it.
Step 5: Create pull request!
See Development workflow page for rules of pull request creation and its life-cycle.
Please remember that pull requests should be always based on
Before submitting PR, don’t forget to run code formatting, as described in coding guidelines. After submitting, ensure that all CI checks pass on your PR and fix them if needed.