PlanOpticon
Merge pull request #16 from ConflictHQ/add-code-of-conduct Add Code of Conduct
Commit
38c3d8782106961646a0c3cc6a31eaf8d1e78934a59be801ce254cf873c65b60
Parent
6f74a6c91f664e7…
2 files changed
+44
+4
| --- a/.github/CODE_OF_CONDUCT.md | ||
| +++ b/.github/CODE_OF_CONDUCT.md | ||
| @@ -0,0 +1,44 @@ | ||
| 1 | +# Code of Conduct | |
| 2 | + | |
| 3 | +## Our Pledge | |
| 4 | + | |
| 5 | +We as members, contributors, and maintainers pledge to make participation in PlanOpticon a welcoming 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. | |
| 6 | + | |
| 7 | +## Our Standards | |
| 8 | + | |
| 9 | +**Expected behavior:** | |
| 10 | + | |
| 11 | +- Using welcoming and inclusive language | |
| 12 | +- Being respectful of differing viewpoints and experiences | |
| 13 | +- Gracefully accepting constructive criticism | |
| 14 | +- Focusing on what is best for the community | |
| 15 | +- Showing empathy toward other community members | |
| 16 | + | |
| 17 | +**Unacceptable behavior:** | |
| 18 | + | |
| 19 | +- Trolling, insulting or derogatory comments, and personal attacks | |
| 20 | +- Public or private unwelcome conduct | |
| 21 | +- Publishing others' private information without explicit permission | |
| 22 | +- Other conduct which could reasonably be considered inappropriate in a professional setting | |
| 23 | + | |
| 24 | +## Responsibilities | |
| 25 | + | |
| 26 | +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. | |
| 27 | + | |
| 28 | +Project maintainers have the right to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to temporarily or permanently ban any contributor for behaviors they deem inappropriate. | |
| 29 | + | |
| 30 | +## Scope | |
| 31 | + | |
| 32 | +This Code of Conduct applies within all project spaces and in public spaces when an individual is representing the project or its community. | |
| 33 | + | |
| 34 | +## Enforcement | |
| 35 | + | |
| 36 | +Instances of unacceptable behavior may be reported by contacting the project team at: | |
| 37 | + | |
| 38 | +**[email protected]** | |
| 39 | + | |
| 40 | +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. | |
| 41 | + | |
| 42 | +## Attribution | |
| 43 | + | |
| 44 | +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1. |
| --- a/.github/CODE_OF_CONDUCT.md | |
| +++ b/.github/CODE_OF_CONDUCT.md | |
| @@ -0,0 +1,44 @@ | |
| --- a/.github/CODE_OF_CONDUCT.md | |
| +++ b/.github/CODE_OF_CONDUCT.md | |
| @@ -0,0 +1,44 @@ | |
| 1 | # Code of Conduct |
| 2 | |
| 3 | ## Our Pledge |
| 4 | |
| 5 | We as members, contributors, and maintainers pledge to make participation in PlanOpticon a welcoming 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. |
| 6 | |
| 7 | ## Our Standards |
| 8 | |
| 9 | **Expected behavior:** |
| 10 | |
| 11 | - Using welcoming and inclusive language |
| 12 | - Being respectful of differing viewpoints and experiences |
| 13 | - Gracefully accepting constructive criticism |
| 14 | - Focusing on what is best for the community |
| 15 | - Showing empathy toward other community members |
| 16 | |
| 17 | **Unacceptable behavior:** |
| 18 | |
| 19 | - Trolling, insulting or derogatory comments, and personal attacks |
| 20 | - Public or private unwelcome conduct |
| 21 | - Publishing others' private information without explicit permission |
| 22 | - Other conduct which could reasonably be considered inappropriate in a professional setting |
| 23 | |
| 24 | ## Responsibilities |
| 25 | |
| 26 | 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. |
| 27 | |
| 28 | Project maintainers have the right to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to temporarily or permanently ban any contributor for behaviors they deem inappropriate. |
| 29 | |
| 30 | ## Scope |
| 31 | |
| 32 | This Code of Conduct applies within all project spaces and in public spaces when an individual is representing the project or its community. |
| 33 | |
| 34 | ## Enforcement |
| 35 | |
| 36 | Instances of unacceptable behavior may be reported by contacting the project team at: |
| 37 | |
| 38 | **[email protected]** |
| 39 | |
| 40 | 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. |
| 41 | |
| 42 | ## Attribution |
| 43 | |
| 44 | This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1. |
| --- .github/CONTRIBUTING.md | ||
| +++ .github/CONTRIBUTING.md | ||
| @@ -123,10 +123,14 @@ | ||
| 123 | 123 | |
| 124 | 124 | - **Bugs:** Open an issue using the [Bug Report](https://github.com/ConflictHQ/PlanOpticon/issues/new?template=bug_report.yml) template. |
| 125 | 125 | - **Features:** Open an issue using the [Feature Request](https://github.com/ConflictHQ/PlanOpticon/issues/new?template=feature_request.yml) template. |
| 126 | 126 | - **Questions:** Start a thread in [Discussions](https://github.com/ConflictHQ/PlanOpticon/discussions). |
| 127 | 127 | |
| 128 | +## Code of Conduct | |
| 129 | + | |
| 130 | +This project follows a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold it. | |
| 131 | + | |
| 128 | 132 | ## Security |
| 129 | 133 | |
| 130 | 134 | If you discover a security vulnerability, please do **not** open a public issue. Instead, follow the process described in our [Security Policy](SECURITY.md). |
| 131 | 135 | |
| 132 | 136 | ## License |
| 133 | 137 |
| --- .github/CONTRIBUTING.md | |
| +++ .github/CONTRIBUTING.md | |
| @@ -123,10 +123,14 @@ | |
| 123 | |
| 124 | - **Bugs:** Open an issue using the [Bug Report](https://github.com/ConflictHQ/PlanOpticon/issues/new?template=bug_report.yml) template. |
| 125 | - **Features:** Open an issue using the [Feature Request](https://github.com/ConflictHQ/PlanOpticon/issues/new?template=feature_request.yml) template. |
| 126 | - **Questions:** Start a thread in [Discussions](https://github.com/ConflictHQ/PlanOpticon/discussions). |
| 127 | |
| 128 | ## Security |
| 129 | |
| 130 | If you discover a security vulnerability, please do **not** open a public issue. Instead, follow the process described in our [Security Policy](SECURITY.md). |
| 131 | |
| 132 | ## License |
| 133 |
| --- .github/CONTRIBUTING.md | |
| +++ .github/CONTRIBUTING.md | |
| @@ -123,10 +123,14 @@ | |
| 123 | |
| 124 | - **Bugs:** Open an issue using the [Bug Report](https://github.com/ConflictHQ/PlanOpticon/issues/new?template=bug_report.yml) template. |
| 125 | - **Features:** Open an issue using the [Feature Request](https://github.com/ConflictHQ/PlanOpticon/issues/new?template=feature_request.yml) template. |
| 126 | - **Questions:** Start a thread in [Discussions](https://github.com/ConflictHQ/PlanOpticon/discussions). |
| 127 | |
| 128 | ## Code of Conduct |
| 129 | |
| 130 | This project follows a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold it. |
| 131 | |
| 132 | ## Security |
| 133 | |
| 134 | If you discover a security vulnerability, please do **not** open a public issue. Instead, follow the process described in our [Security Policy](SECURITY.md). |
| 135 | |
| 136 | ## License |
| 137 |