This project is developed entirely in the open, on public mailing lists and with public code reviews. To participate in development discussions, please subscribe to the automotive-eg-rvi mailing list, or join the #automotive channel on Freenode. Code is reviewed on gerrit. Development is planned and issues are tracked in JIRA.

All code contributed to this project must be licensed under the MPL v2 license, a copy of which you can find in this repository. Documentation must be licensed under the CC BY 4.0 license.

Secure Development Process

This project is developed with a special focus on secure engineering. During development, any interaction between components—​that is, anything that crosses a boundary in one of the context diagrams--must undergo a security review. Any new potential threats and their attendant mitigations will be added to the security model, and once it passes review, the interaction will be added to the whitelist.

Features need to come from the project requirements, and will be tracked on JIRA. (Check back later for a process for submitting requests for new requirements.)


We don’t want to settle for just making sure RVI SOTA is a great piece of software; we want it to be something that people are interesting in using, understanding, and contributing to. To that end, we strive to make these docs as clear, up-to-date, and comprehensive as possible. So if there’s anything you’re having trouble with, please don’t hesitate to engage with us on the automotive-eg-rvi mailing list. Or if you want to contribute to the documentation directly, you’ll find the sources for the documentation site in rvi_sota_server/docs. The docs are written in Asciidoc format (complete syntax reference here, but if you’re familiar with Markdown you’ll feel right at home), and rendered using Jekyll and Asciidoctor.