For OpenLMIS v3+
The technical committee has decided to adopt Google's Java Style guide with a general preference to adopt mature style guides rather than create our own.
For OpenLMIS v1-v2:
Please see CONTRIBUTING.MD and STYLE-GUIDE.MD in the source code.
Per the 2015 Community Meeting, the Techincal Committee will establish and enforce standards for code quality. Some of the high level decisions:
- As much as possible, code standards are tracked automatically by Sonar
- With regards to legacy code: once standards are established, the "don't make things worse" principle will apply. New code must adhere to standards. If legacy code files are touched, newly added code should adhere to standards. Legacy code is opportunistically updated - if a contributor is working in an older file, it is the contributor's discretion whether to bring the source file up to standards.