|
| 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 | +## Our Standards |
| 8 | + |
| 9 | +Examples of behavior that contributes to a positive environment: |
| 10 | + |
| 11 | +* Being respectful and inclusive in discussions |
| 12 | +* Focusing on technical merit and project goals |
| 13 | +* Providing constructive feedback on contributions |
| 14 | +* Accepting criticism gracefully and learning from mistakes |
| 15 | +* Focusing on what is best for the community and project |
| 16 | + |
| 17 | +Examples of unacceptable behavior: |
| 18 | + |
| 19 | +* Harassment, trolling, or discriminatory language |
| 20 | +* Personal attacks or inflammatory comments |
| 21 | +* Publishing others' private information without permission |
| 22 | +* Spam, off-topic discussions, or promotion of unrelated projects |
| 23 | +* Any conduct that would be inappropriate in a professional setting |
| 24 | + |
| 25 | +## Project Focus |
| 26 | + |
| 27 | +This project maintains a clear focus on technical excellence: |
| 28 | + |
| 29 | +- **Stay on topic**: Discussions should relate to Shimmy's development |
| 30 | +- **Respect the philosophy**: Contributions should align with lightweight, zero-config principles |
| 31 | +- **Quality over quantity**: We value thoughtful contributions over high volume |
| 32 | +- **Technical merit**: Decisions are made based on technical merit and project goals |
| 33 | + |
| 34 | +## Enforcement Responsibilities |
| 35 | + |
| 36 | +The project maintainer is responsible for clarifying and enforcing standards of acceptable behavior and will take appropriate corrective action in response to any behavior deemed inappropriate, threatening, offensive, or harmful. |
| 37 | + |
| 38 | +## Scope |
| 39 | + |
| 40 | +This Code of Conduct applies within all project spaces, including: |
| 41 | +- GitHub repository (issues, PRs, discussions) |
| 42 | +- Project communications |
| 43 | +- Public representation of the project |
| 44 | + |
| 45 | +## Enforcement |
| 46 | + |
| 47 | +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to [michaelallenkuykendall@gmail.com](mailto:michaelallenkuykendall@gmail.com). |
| 48 | + |
| 49 | +All complaints will be reviewed and investigated promptly and fairly. The maintainer is obligated to respect the privacy and security of the reporter. |
| 50 | + |
| 51 | +## Enforcement Guidelines |
| 52 | + |
| 53 | +The maintainer will follow these Community Impact Guidelines: |
| 54 | + |
| 55 | +### 1. Correction |
| 56 | +**Community Impact**: Minor inappropriate behavior or technical disagreement. |
| 57 | +**Consequence**: Private clarification about the nature of the violation and explanation of why the behavior was inappropriate. |
| 58 | + |
| 59 | +### 2. Warning |
| 60 | +**Community Impact**: Moderate violation or pattern of inappropriate behavior. |
| 61 | +**Consequence**: Warning with consequences for continued behavior. |
| 62 | + |
| 63 | +### 3. Temporary Ban |
| 64 | +**Community Impact**: Serious violation of community standards. |
| 65 | +**Consequence**: Temporary ban from project interaction. |
| 66 | + |
| 67 | +### 4. Permanent Ban |
| 68 | +**Community Impact**: Sustained inappropriate behavior or severe violation. |
| 69 | +**Consequence**: Permanent ban from all project interaction. |
| 70 | + |
| 71 | +## Attribution |
| 72 | + |
| 73 | +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0. |
0 commit comments