| layout | title | nav_order | has_children |
|---|---|---|---|
default |
Contributing |
6 |
true |
{:.no_toc}
RAPIDS can only grow with community support and it is vital to include developers at all levels. Reporting bugs, fixing them, and/or creating new features are all vital for the success of RAPIDS. The following pages outline our approach for contributing to RAPIDS. {: .fs-6 .fw-300 }
Welcome! We are excited you are here! Before you begin, we ask that everyone review the [Code of Conduct]({% link resources/conduct.md %}) before contributing.
- Read the project's README to learn how to setup the development environment
- Find an issue to work on. The best way is to look for the good first issue or help wanted labels
- Comment on the issue saying you are going to work on it
- Code! Make sure to update unit tests!
- All RAPIDS projects are released under the Apache-2.0 license, so also make sure all source files that support comments include a copyright and the Apache-2.0 license text.
- When done, [create your pull request]({% link contributing/prs.md %})
- Verify that CI passes all status checks. Fix if needed
- Wait for other developers to review your code and update code as needed
- Once reviewed and approved, a RAPIDS developer will merge your pull request
Remember, if you are unsure about anything, don't hesitate to comment on issues and ask for clarifications!
Once you have gotten your feet wet and are more comfortable with the code, follow these steps to find prioritized issues.
All RAPIDS projects have project boards for triaging [issues]({% link releases/triage.md %}) and planning [features]({% link releases/planning.md %}).
Review the [Code Contributions]({% link contributing/code.md %}) page.
File an issue here for any unexpected problems encountered or general feedback with any of the information on this site.