nervosnetwork
diff --git a/‎CONTRIBUTING.md
+108 b/‎CONTRIBUTING.md
+108
@@ -0,0 +1,108 @@
+# Contributing
+
+Our goal is to make contributing to the `mercury` project easy and transparent.
+
+When contributing to this repository, please first discuss the change you wish to make via issue, or any other method with the community before making a change. 
+
+### Report Issue
+
+* Read known issues to see whether the issue is already addressed there.
+
+* Search existing issues to see whether others had already posted a similar issue.
+  
+* **Do not open up a GitHub issue to report security vulnerabilities**. Instead,
+  refer to the [security policy](SECURITY.md).
+
+* When creating a new issue, be sure to include a title and clear description. It is appreciated that if you can also attach as much relevant information as possible, such as version, environment, reproducing steps, samples.
+
+### Send PR
+
+* See [Code Standards](https://rust-coding-guidelines.github.io/rust-coding-guidelines-zh/safe-guides/intro.html) for code guidelines.
+  
+* See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
+
+1. Fork the `mercury` repo and create your branch from master.
+2. If you have added code that should be tested, add unit tests.
+3. Verify and ensure that the test suite passes.
+4. Run `make ci` to lint and test the code before commit.
+5. Make sure your code passes CI.
+6. Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
+7. Submit your pull request.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq