2020-01-18 02:22:00 +08:00
# How to contribute
2023-12-13 09:27:42 +08:00
Our software is open source so you can solve your own problems without needing help from others. And if you solve a problem and are so kind, you can upstream it for the rest of the world to use. Check out our [post about externalization ](https://blog.comma.ai/a-2020-theme-externalization/ ). Development activity is coordinated through our GitHub Issues, [GitHub Discussions ](https://github.com/commaai/openpilot/discussions ), and [Discord ](https://discord.comma.ai ).
2020-01-18 02:22:00 +08:00
2021-12-14 12:30:24 +08:00
### Getting Started
2020-01-18 02:22:00 +08:00
2023-12-13 09:27:42 +08:00
* Setup your [development environment ](../tools/ )
* Read about the [development workflow ](WORKFLOW.md )
* Join our [Discord ](https://discord.comma.ai )
* Docs are at https://docs.comma.ai and https://blog.comma.ai
2023-12-15 03:25:09 +08:00
## What contributions are we looking for?
2023-12-13 09:27:42 +08:00
**openpilot's priorities are [safety ](SAFETY.md ), stability, quality, and features, in that order.** openpilot is part of comma's mission to *solve self-driving cars while delivering shippable intermediaries* , and all developoment is towards that goal.
2023-12-15 03:25:09 +08:00
### What gets merged?
2023-12-13 09:27:42 +08:00
The probability of a pull request being merged is a function of its value to the project and the effort it will take us to get it merged.
If a PR offers *some* value but will take lots of time to get merged, it will be closed.
Simple, well-tested bug fixes are the easiest to merge, and new features are the hardest to get merged.
All of these are examples of good PRs:
* typo fix: https://github.com/commaai/openpilot/pull/30678
* removing unused code: https://github.com/commaai/openpilot/pull/30573
* simple car model port: https://github.com/commaai/openpilot/pull/30245
* car brand port: https://github.com/commaai/openpilot/pull/23331
### What doesn't get merged?
* arbitrary style changes
* PRs without a clear goal
* 500+ line PRs: it should be either cleaned up, broken up into smaller PRs, or both
2020-01-18 02:22:00 +08:00
2022-01-03 07:14:22 +08:00
### First contribution
2023-12-13 09:27:42 +08:00
Check out any [good first issue ](https://github.com/commaai/openpilot/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 ) to get started.
### What do I need to contribute?
A lot of openpilot work requires only a PC, and some requires a comma device.
Most car-related contributions require access to that car, plus a comma device installed in the car.
2022-01-03 07:14:22 +08:00
2021-12-14 12:30:24 +08:00
## Pull Requests
2020-01-18 02:22:00 +08:00
2023-12-13 09:27:42 +08:00
Pull requests should be against the master branch. If you're unsure about a contribution, feel free to open a discussion, issue, or draft PR to discuss the problem you're trying to solve.
2020-01-18 02:22:00 +08:00
2021-12-14 12:30:24 +08:00
A good pull request has all of the following:
* a clearly stated purpose
* every line changed directly contributes to the stated purpose
* verification, i.e. how did you test your PR?
* justification
* if you've optimized something, post benchmarks to prove it's better
* if you've improved your car's tuning, post before and after plots
* passes the CI tests
2020-01-18 02:22:00 +08:00
2023-12-13 09:27:42 +08:00
## Contributing without Code
2021-12-14 12:30:24 +08:00
2023-12-13 09:27:42 +08:00
* Report bugs in GitHub issues.
* Report driving issues in the `#driving-feedback` Discord channel.
* Consider opting into driver camera uploads to improve the driver monitoring model.
* Connect your device to Wi-Fi regularly, so that we can pull data for training better driving models.
* Run the `nightly` branch and report issues. This branch is like `master` but it's built just like a release.
2023-12-15 02:42:43 +08:00
* Annotate images in the [comma10k dateset ](https://github.com/commaai/comma10k ).
