Thank you for your interest in making contributions to Mina-rs! Start by taking a look at this page for overall information on repository workflow and standards.
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
To start contributing to mina-rs, following is a cursory guideline on how to make the process of making changes more efficient for the contributer and the maintainer.
- File an issue for the change you want to make. This way we can track the why of the change. Get consensus from community for the change.
- Clone the project and perform a fresh build. Create a branch with the naming "feature/issue-number.
- Ensure that the PR only changes the parts of code which implements/solves the issue. This includes running the linter (cargo fmt) and removing any extra spaces and any formatting that accidentally were made by the code editor in use.
- If your PR has changes that should also reflect in README.md, please update that as well.
- Document non obvious changes and the why of your changes if it's unclear.
- If you are adding a public API, add the documentation as well.
- Increase the version numbers in
Cargo.tomlfile if needed and theREADME.mdto the new version that this Pull Request would represent. The versioning scheme we use is SemVer. - Update the CHANGELOG.md to reflect the change if applicable.
More details: https://github.community/t/best-practices-for-pull-requests/10195
Looking for a good place to start contributing? How about checking out some good first issues
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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
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
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.
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.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. 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.
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4