[Doc] Add contribution.md and code_of_conduct.md (#167)

* Create contribution.md
* Create code_of_conduct.md

doc/code_of_conduct.md

+## Code of Conduct 
+
+Second State follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). 
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Second State team via contact@secondstatae.io.
+
+As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. 
+
+We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. 
+
+Examples of unacceptable behavior by participants include: 
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing others' private information, such as physical or electronic addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. 
+
+This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. 
+

doc/contribution.md

+# Contributing to SSVM 
+
+
+## Welcome 
+
+[**SSVM**](https://github.com/second-state/SSVM) is a high performance and enterprise-ready WebAssembly (WASM) Virtual Machine for cloud, AI, and Blockchain applications. 
+
+SSVM is developed in the open, and is constantly being improved by our **users, contributors, and maintainers**. It is because of you that we can bring great software to the community. 
+
+This guide provides information on filing issues and guidelines for open source contributors. **Please leave comments / suggestions if you find something is missing or incorrect.**
+
+
+
+## Getting Started 
+
+
+### Fork Repository 
+
+Fork the SSVM repository on GitHub to your personal account. 
+
+
+```
+$ git clone git@github.com:second-state/SSVM.git
+$ cd SSVM
+$ git checkout 0.7.3
+```
+
+Notes: Note the SSVM team builds lots of extensions of Server-side WebAssembly, see [TensorFlow](https://github.com/second-state/ssvm-tensorflow), [Storage](https://github.com/second-state/ssvm-storage), [Command interface](https://github.com/second-state/ssvm_process_interface), [Ethereum](https://github.com/second-state/ssvm-evmc), [Substrate](https://github.com/second-state/substrate-ssvm-node). If you want to contribue the extensions, please go to those repositories. 
+
+
+### Setup Development Environment 
+
+The SSVM is developed on Ubuntu 20.04 to take advantage of advanced LLVM features for the AOT compiler. The SSVM team also builds and releases statically linked SSVM binaries for older Linux distributions. 
+
+Our development environment requires libLLVM-10 and >=GLIBCXX_3.4.26. 
+
+If you are using the older operating system than Ubuntu 20.04, please use our special docker image to build SSVM. If you are looking for the pre-built binaries for the older operatoring system, we also provide several pre-built binaries based on manylinux* distribution. 
+
+
+
+
+### Docker image 
+
+
+
+```
+$ docker pull secondstate/ssvm
+```
+
+
+
+### Setup the environment manually 
+
+```
+# Tools and libraries
+$ sudo apt install -y \
+        software-properties-common \
+        cmake \
+        libboost-all-dev
+# And you will need to install llvm for ssvmc tool
+$ sudo apt install -y \
+        llvm-dev \
+        liblld-10-dev
+# SSVM supports both clang++ and g++ compilers# You can choose one of them for building this project
+$ sudo apt install -y gcc g++
+$ sudo apt install -y clang
+```
+
+
+
+## Contribute Workflow 
+
+PR are always welcome, even if they only contain small fixes like typos or a few lines of code. If there will be a significant effort, please document it as an issue and get a discussion going before starting to work on it. 
+
+
+Please submit a PR broken down into small changes bit by bit. A PR consisting of a lot features and code changes may be hard to review. It is recommended to submit PRs in an incremental fashion. 
+
+
+Note: If you split your pull request to small changes, please make sure any of the changes goes to master will not break anything. Otherwise, it can not be merged until this feature is complete. 
+
+
+### Fork and clone 
+
+Fork [the SSVM repository](https://github.com/second-state/SSVM) and clone the code to your local workspace 
+
+
+### Branch 
+
+Changes should be made on your own fork in a new branch. The branch should be named XXX-description where XXX is the number of the issue. PR should be rebased on top of master without multiple branches mixed into the PR. If your PR do not merge cleanly, use commands listed below to get it up to date. 
+
+
+
+### Develop, Build and Test 
+
+Write code on the new branch in your fork. 
+
+
+```
+# After pulling our ssvm docker image
+$ docker run -it --rm \
+    -v <path/to/your/ssvm/source/folder>:/root/ssvm \
+    secondstate/ssvm:latest
+(docker)$ cd /root/ssvm
+(docker)$ mkdir -p build && cd build
+(docker)$ cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=ON .. && make -j
+```
+
+**Run tests**
+The following built-in tests are only available when the build flag BUILD_TESTS sets to ON. 
+You can use these tests to verify the correctness of SSVM binaries. 
+
+
+```
+$ cd <path/to/ssvm/build_folder>
+$ ctest
+```
+
+
+
+### Push and Create PR 
+
+When ready for review, push your branch to your fork repository on github.com. 
+
+Then visit your fork at https://github.com/$user/SSVM and click the Compare & Pull Request button next to your branch to create a new pull request (PR). Description of a pull request should refer to all the issues that it addresses. Remember to put a reference to issues (such as Closes #XXX and Fixes #XXX) in commits so that the issues can be closed when the PR is merged. 
+
+Once your pull request has been opened it will be assigned to one or more reviewers. Those reviewers will do a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and style. 
+
+Commit changes made in response to review comments to the same branch on your fork. 
+
+
+
+## Reporting issues 
+
+It is a great way to contribute to SSVM by reporting an issue. Well-written and complete bug reports are always welcome! Please open an issue on Github. 
+
+
+Before opening any issue, please look up the existing [issues](https://github.com/second-state/SSVM/issues) to avoid submitting a duplication. If you find a match, you can "subscribe" to it to get notified on updates. If you have additional helpful information about the issue, please leave a comment. 
+
+
+When reporting issues, always include: 
+
+* Version of your system
+* Configuration files of SSVM
+
+Because the issues are open to the public, when submitting the log and configuration files, be sure to remove any sensitive information, e.g. user name, password, IP address, and company name. You can replace those parts with "REDACTED" or other strings like "****". 
+Be sure to include the steps to reproduce the problem if applicable. It can help us understand and fix your issue faster. 
+
+
+## Documenting 
+
+Update the documentation if you are creating or changing features. Good documentation is as important as the code itself. 
+Documents are written with Markdown. See [Writing on GitHub](https://help.github.com/categories/writing-on-github/) for more details. 
+
+
+## Design new features 
+
+You can propose new designs for existing SSVM features. You can also design entirely new features, Please submit a proposal via GitHub issues. 
+
+
+SSVM maintainers will review this proposal as soon as possible. This is necessary to ensure the overall architecture is consistent and to avoid duplicated work in the roadmap.