All code and comments must be written in plain english and should avoid cross language inclusions. This is needed for better portability and, eventually, showcasing in the case of public projects or snippets.
All python code should conform to the pep8 style guide.
Naming of variables, objects, functions, and class methods should be underscore separated lowercase e.g.: test_variable = 0, def partition_function(), self.method(), class_instance = Class_Name().
Class naming should be underscore separated camelcase e.g.: class Class_Name(object). If the class name includes acronyms those should be all uppercase, e.g.: class IR_Camera(object), class UAV_Controller(object)
C++ code should follow the same functions and classes naming conventions of the python coded and also the style described in the google c++ style guide.
The only exception is the naming of private and protected class methods and attributes which should have a leading underscore instead of a trailing one, e.g.: void _private_method(), int _protected_getter() instead of void private_method_(), int protected_getter_(), this enhances the readability of the code and makes it easier to distinguish private methods from the public ones.
Every python project should include a "requirements.txt" file in order to automatically install all the dependencies using pip install -r requirements.txt
Include a README.md file in the root directory of every project. The readme should include at least a "Quick Start" section with instructions on how to run the project on a new machine. Public projects must also include a LICENSE.md file, you can use the MIT license included in this repository.
Measurement units must follow the SI standard as defined in nist guide for the use of the international system of units