We follow the Github flow development model.
First fork and clone the project project.
Always branch off main for new features.
git checkout -b mydescriptivebranchname
The developer guide explains how to set up the development environment on Mac OS, Linux or Windows. Please take note of our coding style when editing files.
Always write descriptive commit messages and add a fixes or relates note to them with an issue number (Github will link these then conveniently)
Example:
Change how the attitude controller works
- Fixes rate feed forward
- Allows a local body rate override
Fixes issue #123
Since we care about safety, we will regularly ask you for test results. Best is to do a test flight (or bench test where it applies) and upload the logfile from it (on the microSD card in the logs directory) to Google Drive or Dropbox and share the link.
Push changes to your repo and send a pull request.
Make sure to provide some testing feedback and if possible the link to a flight log file. Upload flight log files to Flight Review and link the resulting report.