diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000000000000000000000000000000000000..47640c05880819a3157372d7ae810e115f198872
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,76 @@
+# How to contribute
+
+## Report issues
+
+A great way to contribute to the project is to send a detailed report when you encounter an issue. We always appreciate a well-written, thorough bug report and feature propose, and will appreciate you for it!
+
+### Issues format
+
+When reporting issues, refer to this format:
+
+- Is this a BUG REPORT or FEATURE REQUEST?
+- What happened?
+- What you expected to happen?
+- What happened?
+- How to reproduce it (as minimally and precisely as possible)
+- Anything else we need to know?
+- Environment
+
+See more about [ISSUE_TEMPLATE](.gitee/ISSUE_TEMPLATE.en.md).
+
+## Submit pull requests
+
+If you are a beginner and expect this project as the gate to open source world, this tutorial is one of the best choices for you. Just follow the guidance and you will find the pleasure to become a contributor.
+
+### Step 1: Fork repository
+
+Before making modifications of this project, you need to make sure that this project have been forked to your own
+repository. It means that there will be parallel development between this repo and your own repo, so be careful
+to avoid the inconsistency between these two repos.
+
+### Step 2: Clone the remote repository
+
+If you want to download the code to the local machine, ```git``` is the best way:
+```
+git clone https://your_repo_url/community.git
+```
+
+### Step 3: Develop code locally
+
+To avoid inconsistency between multiple branches, we SUGGEST checking out to a new branch:
+```
+git checkout -b new_branch_name origin/master
+```
+Then you can change the code arbitrarily.
+
+### Step 4: Push the code to the remote repository
+
+After updating the code, you should push the update in the formal way:
+```
+git add .
+git status (Check the update status)
+git commit -m "Your commit description"
+git commit --amend (Add the concrete description of your commit)
+git push origin new_branch_name
+```
+
+### Step 5: Pull a request to repository
+
+In the last step, your need to pull a compare request between your new branch and development branch. After
+finishing the pull request, the CI will be automatically set up for building test.
+
+### Pull requests format
+
+When submitting pull requests, refer to this format:
+
+- What this PR does / why we need it?
+- Which issue this PR fixes?
+- Special notes for your reviewer
+- Release note
+
+See more about [PULL_REQUEST_TEMPLATE](.gitee/PULL_REQUEST_TEMPLATE.en.md).
+
+### Code style
+
+```TO BE DEFINED```
+