From acad792d508f220a76a8447b1336dfbcc222beaf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=CA=8E=CA=9Es=CA=8Co=CA=9E=E1=B4=89=C9=90=C9=A5=C9=94?=
 =?UTF-8?q?=EA=93=95=20=C9=B9=CA=87o=CA=8E=EA=93=92?= <zxkmm@hotmail.com>
Date: Sun, 4 Feb 2024 12:37:27 +0800
Subject: [PATCH] Updated Code contribution rules (markdown)

---
 Code-contribution-rules.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Code-contribution-rules.md b/Code-contribution-rules.md
index 637a706..0faeb62 100644
--- a/Code-contribution-rules.md
+++ b/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.