**SPDX-License-Identifier: MPL-2.0-or-later
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, caste, color, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Examples of behavior that contributes to a positive environment:
- Empathy and Kindness: Being understanding and compassionate toward others
- Respect: Valuing different opinions, viewpoints, and experiences
- Constructive Feedback: Giving and accepting feedback gracefully
- Accountability: Accepting responsibility for mistakes and learning from them
- Community Focus: Prioritizing what is best for the overall community
- Collaboration: Working together toward common goals
- Inclusivity: Welcoming newcomers and helping them succeed
- Patience: Understanding that people have different skill levels and learning paces
Examples of unacceptable behavior:
- Harassment: Sexualized language/imagery, unwelcome sexual attention or advances
- Trolling: Insulting/derogatory comments, personal or political attacks
- Doxxing: Publishing others' private information without permission
- Conduct: Other conduct reasonably considered inappropriate in a professional setting
- Discrimination: Any form of discrimination based on protected characteristics
- Intimidation: Deliberate intimidation, stalking, or following
- Disruption: Sustained disruption of discussions or events
Beyond basic respect, we prioritize emotional safety in our community:
- Safe to Experiment: Mistakes are learning opportunities, not failures
- Safe to Question: No question is "stupid" or unwelcome
- Safe to Disagree: Technical disagreements are healthy when respectful
- Safe to Learn: Everyone was a beginner once
- Clear Documentation: Reduce uncertainty with comprehensive guides
- Predictable Processes: Well-defined contribution workflow
- Supportive Reviews: Code review focuses on improvement, not criticism
- Reversibility: Design decisions can be changed if better approaches emerge
- No Crunch Culture: Sustainable pace, no burnout encouraged
- Work-Life Balance: Respect personal boundaries and time zones
- Mental Health: Breaks and time away are encouraged and respected
- Compassionate Communication: Assume good intent, communicate kindly
Project maintainers are responsible for:
- Clarifying Standards: Explaining and enforcing standards of acceptable behavior
- Fair Moderation: Taking appropriate and fair corrective action
- Content Moderation: Removing/rejecting inappropriate content
- Banning: Temporarily or permanently banning inappropriate participants
- Transparency: Communicating reasons for moderation decisions
All community members are expected to:
- Follow Standards: Adhere to this Code of Conduct
- Report Violations: Report unacceptable behavior to moderators
- Support Others: Help create a welcoming environment
- Learn and Grow: Be open to feedback and continuous improvement
If you experience or witness unacceptable behavior:
Primary Contact:
- Email: conduct@vext.dev
- Expected response: Within 24 hours
Confidential Reporting:
- All reports are treated confidentially
- Reporters' identity is protected
- Anonymous reports accepted but may be harder to follow up
What to Include:
- Description of the incident
- When and where it occurred
- Who was involved
- Any relevant screenshots or logs
- Your contact information (unless reporting anonymously)
-
Acknowledgment (24 hours)
- Confirm receipt of report
- Assign to appropriate moderator
- Provide incident number
-
Investigation (1-7 days)
- Review all available information
- Interview involved parties if needed
- Consult with other moderators
- Determine appropriate action
-
Resolution (After investigation)
- Take corrective action
- Communicate decision to involved parties
- Document incident (confidentially)
We follow a graduated enforcement approach:
Impact: Use of inappropriate language or unprofessional behavior
Consequence:
- Private written warning
- Clarification of violation
- Apology may be requested
- No public record
Example: Heated technical argument that became personal
Impact: Repeated minor violations or single moderate violation
Consequence:
- Formal written warning
- Temporary restriction of privileges
- Public or private (depending on severity)
- Recorded in moderation log
Example: Continued argumentative behavior after correction
Impact: Sustained inappropriate behavior or harassment
Consequence:
- Temporary ban (7-90 days)
- No interaction with community
- Prohibited from public or private communication
- Public announcement of ban
Example: Harassment, doxxing, or discriminatory behavior
Impact: Severe violations, sustained harassment, or repeated serious violations
Consequence:
- Permanent expulsion from community
- All accounts and access revoked
- Public announcement
- May involve legal action if applicable
Example: Threats, severe harassment, coordinated attacks
You may appeal enforcement decisions:
- Submit Appeal: Email conduct-appeal@vext.dev within 30 days
- Include: Incident number, reason for appeal, additional context
- Review: Different moderator reviews the case
- Decision: Final decision within 14 days
- Outcome: Decision is final and binding
This Code of Conduct applies:
- Project Spaces: GitHub, GitLab, chat channels, mailing lists
- Public Representation: Social media, conferences, meetups when representing the project
- Private Communication: When affecting community members (extreme cases)
- Events: Any vext-related events, online or in-person
We provide resources to help build a positive community:
- Onboarding Guide: How to contribute positively
- Communication Guide: Effective and empathetic communication
- Conflict Resolution: How to handle disagreements constructively
- Unconscious Bias Training: Recognizing and addressing biases
We publish quarterly transparency reports:
- Number of reports received
- Categories of violations
- Actions taken (anonymized)
- Trends and patterns
- Improvements made
See: docs/conduct/transparency/
Before formal reports, consider:
- Direct Communication: Politely address the issue directly (if safe)
- Request Mediation: Ask a moderator to facilitate discussion
- Take a Break: Step away from heated discussions
- Seek Advice: Ask moderators for guidance (not necessarily a report)
❌ Bad: "That's a stupid idea. Anyone who knows Python would see the problem."
✅ Good: "I have concerns about this approach. In my experience, [specific technical reason]. Have you considered [alternative]? I'd be happy to discuss further."
❌ Bad: "This code is terrible. Did you even test it?"
✅ Good: "Thanks for the contribution! I noticed a few edge cases that might need handling: [specific cases]. Here's how similar issues were addressed in [other file]. Want to pair on this?"
❌ Bad: "Why doesn't this work? The docs are useless."
✅ Good: "I'm trying to [goal] and getting [error]. I've read [doc section] and tried [attempt]. Could someone point me in the right direction?"
This Code of Conduct is adapted from:
- Contributor Covenant, version 2.1
- Django Code of Conduct
- Rust Code of Conduct
- Compassionate Collaboration Community Principles (CCCP)
- Code of Conduct Violations: conduct@vext.dev
- Appeals: conduct-appeal@vext.dev
- General Questions: community@vext.dev
- Immediate Safety Concerns: Call local emergency services
This Code of Conduct is licensed under CC BY 4.0.
Last Updated: 2025-01-01 Version: 1.1 Next Review: 2025-07-01
Thank you for helping make vext a welcoming and inclusive community! 💙