Updated Code contribution rules (markdown)

Code-contribution-rules.md

@@ -19,6 +19,14 @@ It's important for everyone, be it contributors or reviewers, to have a clear co
 * Each new functionality should have it's own PR, don't put too much files/commits into a single PR. When it's too much commits, one can make a new branch and report only the modified files in a single commit, to make the review easier
 * Merging of any PR is up to the maintainers good will
 
+# naming scheme
+* Use English
+* var_and_func_example (snake_case)
+* _private_member_of_class_example (_snake_case)
+* namespaceexample
+* ClassNameExample (CamelCase)
+* objectNameExample (camelCase)
+
 # which license of code is safe to use   
  - MIT: It's safe to copy MIT license, as long as you keep original copyright info.   
  - MPL: It's safe to copy MPL license, as long as you follow Mozilla's agreement.