|
| 1 | +# Contributing |
| 2 | + |
| 3 | +When contributing to this repository, please first discuss the change you wish |
| 4 | +to make via issue, email, or any other method with the owners of this repository |
| 5 | +before making a change. |
| 6 | + |
| 7 | +Please note we have a code of conduct, please follow it in all your interactions |
| 8 | +with the project. |
| 9 | + |
| 10 | +## Pull Request Process |
| 11 | + |
| 12 | +1. Ensure any install or build dependencies are removed and untracked. |
| 13 | +2. Update the `README.md` with details of changes to the interface along with an |
| 14 | + example or two. |
| 15 | +3. State whether or not the Pull Request is backwards compatible and if not, |
| 16 | + then state what the breaking changes are so that they can be documented in |
| 17 | + the release notes. |
| 18 | +4. Create the Pull Request and a reviewer will either accept and merge the Pull |
| 19 | + Request, then tag the new release, or alternatively the reviewer will request |
| 20 | + for more information regarding the Pull Request or even some changes for you |
| 21 | + to make before we can accept the Pull Request. |
| 22 | + |
| 23 | +## Code of Conduct |
| 24 | + |
| 25 | +### Our Pledge |
| 26 | + |
| 27 | +In the interest of fostering an open and welcoming environment, we as |
| 28 | +contributors and maintainers pledge to making participation in our project and |
| 29 | +our community a harassment-free experience for everyone, regardless of age, body |
| 30 | +size, disability, ethnicity, gender identity and expression, level of experience, |
| 31 | +nationality, personal appearance, race, religion, or sexual identity and |
| 32 | +orientation. |
| 33 | + |
| 34 | +### Our Standards |
| 35 | + |
| 36 | +Examples of behavior that contributes to creating a positive environment |
| 37 | +include: |
| 38 | + |
| 39 | +* Using welcoming and inclusive language |
| 40 | +* Being respectful of differing viewpoints and experiences |
| 41 | +* Gracefully accepting constructive criticism |
| 42 | +* Focusing on what is best for the community |
| 43 | +* Showing empathy towards other community members |
| 44 | + |
| 45 | +Examples of unacceptable behavior by participants include: |
| 46 | + |
| 47 | +* The use of sexualized language or imagery and unwelcome sexual attention or |
| 48 | +advances |
| 49 | +* Trolling, insulting/derogatory comments, and personal or political attacks |
| 50 | +* Public or private harassment |
| 51 | +* Publishing others' private information, such as a physical or electronic |
| 52 | + address, without explicit permission |
| 53 | +* Other conduct which could reasonably be considered inappropriate in a |
| 54 | + professional setting |
| 55 | + |
| 56 | +### Our Responsibilities |
| 57 | + |
| 58 | +Project maintainers are responsible for clarifying the standards of acceptable |
| 59 | +behavior and are expected to take appropriate and fair corrective action in |
| 60 | +response to any instances of unacceptable behavior. |
| 61 | + |
| 62 | +Project maintainers have the right and responsibility to remove, edit, or |
| 63 | +reject comments, commits, code, wiki edits, issues, and other contributions |
| 64 | +that are not aligned to this Code of Conduct, or to ban temporarily or |
| 65 | +permanently any contributor for other behaviors that they deem inappropriate, |
| 66 | +threatening, offensive, or harmful. |
| 67 | + |
| 68 | +### Scope |
| 69 | + |
| 70 | +This Code of Conduct applies both within project spaces and in public spaces |
| 71 | +when an individual is representing the project or its community. Examples of |
| 72 | +representing a project or community include using an official project e-mail |
| 73 | +address, posting via an official social media account, or acting as an appointed |
| 74 | +representative at an online or offline event. Representation of a project may be |
| 75 | +further defined and clarified by project maintainers. |
| 76 | + |
| 77 | +### Enforcement |
| 78 | + |
| 79 | +Instances of abusive, harassing, or otherwise unacceptable behavior may be |
| 80 | +reported by contacting the project team at [[email protected]](mailto:[email protected]). |
| 81 | +All complaints will be reviewed and investigated and will result in a response |
| 82 | +that is deemed necessary and appropriate to the circumstances. The project team |
| 83 | +is obligated to maintain confidentiality with regard to the reporter of an |
| 84 | +incident. Further details of specific enforcement policies may be posted |
| 85 | +separately. |
| 86 | + |
| 87 | +Project maintainers who do not follow or enforce the Code of Conduct in good |
| 88 | +faith may face temporary or permanent repercussions as determined by other |
| 89 | +members of the project's leadership. |
| 90 | + |
| 91 | +### Attribution |
| 92 | + |
| 93 | +This Code of Conduct is adapted from the [Contributor Covenant][homepage], |
| 94 | +version 1.4, available at [http://contributor-covenant.org/version/1/4][version]. |
| 95 | + |
| 96 | +[homepage]: http://contributor-covenant.org |
| 97 | +[version]: http://contributor-covenant.org/version/1/4/ |
0 commit comments