|
| 1 | +# Code of Conduct |
| 2 | + |
| 3 | +## Our Pledge |
| 4 | + |
| 5 | +We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible 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. |
| 6 | + |
| 7 | +We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. |
| 8 | + |
| 9 | +## Our Standards |
| 10 | + |
| 11 | +Examples of behavior that contributes to a positive environment for our community include: |
| 12 | + |
| 13 | +* **Being respectful and inclusive** of differing opinions, viewpoints, and experiences |
| 14 | +* **Giving and gracefully accepting constructive feedback** |
| 15 | +* **Accepting responsibility** and apologizing to those affected by our mistakes, and learning from the experience |
| 16 | +* **Focusing on what is best** not just for us as individuals, but for the overall community |
| 17 | +* **Showing empathy** towards other community members |
| 18 | +* **Using welcoming and inclusive language** |
| 19 | +* **Being patient** with new contributors and questions |
| 20 | + |
| 21 | +Examples of unacceptable behavior include: |
| 22 | + |
| 23 | +* The use of sexualized language or imagery, and sexual attention or advances of any kind |
| 24 | +* Trolling, insulting or derogatory comments, and personal or political attacks |
| 25 | +* Public or private harassment |
| 26 | +* Publishing others' private information, such as a physical or email address, without their explicit permission |
| 27 | +* Spam, promotional content, or excessive self-promotion |
| 28 | +* Disruptive behavior that interferes with constructive discussion |
| 29 | +* Other conduct which could reasonably be considered inappropriate in a professional setting |
| 30 | + |
| 31 | +## Enforcement Responsibilities |
| 32 | + |
| 33 | +Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. |
| 34 | + |
| 35 | +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, and will communicate reasons for moderation decisions when appropriate. |
| 36 | + |
| 37 | +## Scope |
| 38 | + |
| 39 | +This Code of Conduct applies within all community spaces, including: |
| 40 | + |
| 41 | +- GitHub repository (issues, pull requests, discussions) |
| 42 | +- Project communication channels |
| 43 | +- Official project social media accounts |
| 44 | +- Project events and meetups |
| 45 | + |
| 46 | +This Code of Conduct also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. |
| 47 | + |
| 48 | +## Reporting Violations |
| 49 | + |
| 50 | +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at: |
| 51 | + |
| 52 | +- **GitHub Issues** (for public, non-sensitive violations) |
| 53 | +- **Email:** conduct@interceptsuite.com (for private reports) |
| 54 | +- **GitHub Security Advisories** (for security-related concerns) |
| 55 | + |
| 56 | +All complaints will be reviewed and investigated promptly and fairly. |
| 57 | + |
| 58 | +All project maintainers are obligated to respect the privacy and security of the reporter of any incident. |
| 59 | + |
| 60 | +## Enforcement Guidelines |
| 61 | + |
| 62 | +Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: |
| 63 | + |
| 64 | +### 1. Correction |
| 65 | + |
| 66 | +**Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. |
| 67 | + |
| 68 | +**Consequence:** A private, written warning from project maintainers, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. |
| 69 | + |
| 70 | +### 2. Warning |
| 71 | + |
| 72 | +**Community Impact:** A violation through a single incident or series of actions. |
| 73 | + |
| 74 | +**Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. |
| 75 | + |
| 76 | +### 3. Temporary Ban |
| 77 | + |
| 78 | +**Community Impact:** A serious violation of community standards, including sustained inappropriate behavior. |
| 79 | + |
| 80 | +**Consequence:** A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. |
| 81 | + |
| 82 | +### 4. Permanent Ban |
| 83 | + |
| 84 | +**Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. |
| 85 | + |
| 86 | +**Consequence:** A permanent ban from any sort of public interaction within the community. |
| 87 | + |
| 88 | +## Technical Conduct |
| 89 | + |
| 90 | +In addition to general community standards, we expect technical contributions to adhere to: |
| 91 | + |
| 92 | +### Code Quality |
| 93 | +- Follow the coding standards outlined in [CONTRIBUTING.md](CONTRIBUTING.md) |
| 94 | +- Write clear, maintainable code with appropriate comments |
| 95 | +- Test your changes thoroughly before submitting |
| 96 | + |
| 97 | +### Security |
| 98 | +- Report security vulnerabilities privately (see [SECURITY.md](SECURITY.md)) |
| 99 | +- Do not publicly disclose security issues before they are addressed |
| 100 | +- Do not include malicious code or backdoors |
| 101 | + |
| 102 | +### Intellectual Property |
| 103 | +- Respect software licenses and copyright |
| 104 | +- Do not submit copyrighted code without proper attribution |
| 105 | +- Ensure you have the right to contribute the code you submit |
| 106 | + |
| 107 | +### Pull Requests and Issues |
| 108 | +- Create GitHub issues before submitting PRs for new features or bug fixes |
| 109 | +- Provide clear descriptions and context |
| 110 | +- Be responsive to feedback and questions |
| 111 | +- Respect maintainers' decisions on feature inclusion |
| 112 | + |
| 113 | +## Attribution |
| 114 | + |
| 115 | +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html). |
| 116 | + |
| 117 | +Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). |
| 118 | + |
| 119 | +For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). |
| 120 | + |
| 121 | +## Contact |
| 122 | + |
| 123 | +For questions about this Code of Conduct, please: |
| 124 | +- Open a discussion in [GitHub Discussions](https://github.com/InterceptSuite/ProxyBridge/discussions) |
| 125 | +- Contact the project maintainers via [GitHub Issues](https://github.com/InterceptSuite/ProxyBridge/issues) |
| 126 | + |
| 127 | +--- |
| 128 | + |
| 129 | +**Last Updated:** January 2026 |
| 130 | + |
| 131 | +Thank you for helping make ProxyBridge a welcoming and inclusive community! 🤝 |
0 commit comments