|
| 1 | +# Code of Conduct |
| 2 | + |
| 3 | +## 1. Purpose |
| 4 | + |
| 5 | +The purpose of this Code of Conduct is to provide a clear set of expectations for participation in this project and its community. |
| 6 | +We aim to create an open and welcoming environment for collaboration, where contributors of all backgrounds and experience levels can participate productively and respectfully. |
| 7 | + |
| 8 | +This document outlines expected behavior, unacceptable behavior, enforcement responsibilities, and contribution expectations. |
| 9 | + |
| 10 | +--- |
| 11 | + |
| 12 | +## 2. Our Standards |
| 13 | + |
| 14 | +### Expected Behavior |
| 15 | +- Demonstrate respect and professionalism in all interactions. |
| 16 | +- Use inclusive and welcoming language. |
| 17 | +- Accept constructive feedback gracefully. |
| 18 | +- Respect differing opinions and experiences. |
| 19 | +- Focus on what is best for the community and the project. |
| 20 | +- Follow all contribution and review processes defined by the maintainers. |
| 21 | + |
| 22 | +### Unacceptable Behavior |
| 23 | +- Harassment, discrimination, or personal attacks of any kind. |
| 24 | +- Use of inappropriate, sexualized, or offensive language or imagery. |
| 25 | +- Trolling, insulting comments, or disruptive behavior. |
| 26 | +- Public or private harassment or disclosure of private information without consent. |
| 27 | +- Submitting low-quality, spam, or irrelevant pull requests or issues. |
| 28 | +- Misrepresentation or plagiarism of another contributor’s work. |
| 29 | + |
| 30 | +--- |
| 31 | + |
| 32 | +## 3. Maintainer and Contributor Responsibilities |
| 33 | + |
| 34 | +Project maintainers are responsible for clarifying standards of acceptable behavior and taking appropriate and fair corrective action in response to unacceptable behavior. |
| 35 | + |
| 36 | +Contributors are expected to: |
| 37 | +- Abide by the Code of Conduct in all project-related activities. |
| 38 | +- Submit pull requests that adhere to the **Project Maintainer’s Checklist** (see Section 6). |
| 39 | +- Respect decisions made by the maintainers during review. |
| 40 | +- Maintain the integrity and quality of the project. |
| 41 | + |
| 42 | +Maintainers have the authority to: |
| 43 | +- Merge, request changes, or reject contributions that do not comply with this Code of Conduct or the project’s contribution standards. |
| 44 | +- Temporarily or permanently ban any contributor for serious or repeated violations. |
| 45 | + |
| 46 | +--- |
| 47 | + |
| 48 | +## 4. Scope |
| 49 | + |
| 50 | +This Code of Conduct applies to: |
| 51 | +- All project spaces, including GitHub repositories, issue trackers, and discussions. |
| 52 | +- All communication channels officially associated with the project. |
| 53 | +- Any situation where an individual is representing the project or its community, whether online or offline. |
| 54 | + |
| 55 | +--- |
| 56 | + |
| 57 | +## 5. Enforcement |
| 58 | + |
| 59 | +Instances of unacceptable behavior may be reported to the project maintainers at: |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | +All complaints will be reviewed and investigated promptly and fairly. |
| 64 | +All reports will be handled confidentially and in accordance with applicable laws. |
| 65 | +Maintainers are obligated to respect the privacy and security of the reporter. |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +## 6. Maintainer’s Checklist for Pull Requests |
| 70 | + |
| 71 | +To maintain quality and consistency across contributions, all contributors must ensure that their pull requests meet the following checklist requirements: |
| 72 | + |
| 73 | +- Code follows the repository’s **formatting and style guidelines**. |
| 74 | +- All relevant **tests pass successfully**. |
| 75 | +- Commit messages follow the prescribed **naming and structure conventions**. |
| 76 | +- Documentation or comments are added or updated where necessary. |
| 77 | +- The change has been **reviewed and approved** by at least one project maintainer. |
| 78 | +- Any dependencies or related files are properly referenced. |
| 79 | +- No unrelated or unnecessary changes are included. |
| 80 | + |
| 81 | +Pull requests that do not satisfy the checklist may be rejected or requested for modification at the maintainers’ discretion. |
| 82 | + |
| 83 | +--- |
| 84 | + |
| 85 | +## 7. Enforcement Actions |
| 86 | + |
| 87 | +Violations of this Code of Conduct may result in one or more of the following actions: |
| 88 | +1. Warning issued to the contributor. |
| 89 | +2. Temporary suspension from contributing. |
| 90 | +3. Permanent ban from the project or organization spaces. |
| 91 | +4. Reversal or removal of non-compliant contributions. |
| 92 | + |
| 93 | +Decisions regarding enforcement will be made by the maintainers collectively and documented appropriately. |
| 94 | + |
| 95 | +--- |
| 96 | + |
| 97 | +## 8. Attribution |
| 98 | + |
| 99 | +This Code of Conduct is adapted from the **[Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)**. |
| 100 | +For answers to common questions about this code of conduct, see the [Contributor Covenant FAQ](https://www.contributor-covenant.org/faq). |
| 101 | + |
| 102 | +--- |
| 103 | + |
| 104 | +## 9. License |
| 105 | + |
| 106 | +This Code of Conduct is distributed under the terms of the **Creative Commons Attribution 4.0 International License (CC BY 4.0)**. |
| 107 | +You are free to share and adapt this material with appropriate attribution to the original source. |
| 108 | + |
| 109 | +--- |
| 110 | + |
| 111 | +*End of Code of Conduct* |
0 commit comments