Our Pledge
The Aya project and its contributors are committed to providing a friendly, safe, and welcoming environment for everyone, regardless of:- Age, body size, disability, ethnicity
- Gender identity and expression
- Level of experience
- Nationality, personal appearance, race, religion
- Sexual identity and orientation
Our Standards
Expected Behavior
Examples of behavior that contributes to a positive environment: ✅ Respectful Communication- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
- Supporting newcomers and helping them get started
- Giving and receiving feedback constructively
- Acknowledging contributions from others
- Staying on topic in discussions
- Using professional language in code, comments, and documentation
- Respecting time zones and response times
- Being patient with different skill levels
Unacceptable Behavior
Examples of unacceptable behavior: ❌ Harassment- Trolling, insulting/derogatory comments, personal or political attacks
- Public or private harassment
- Publishing others’ private information without explicit permission
- Unwelcome sexual attention or advances
- Deliberately derailing discussions
- Spamming issues or pull requests
- Repeatedly ignoring project guidelines after correction
- Using sexualized language or imagery
- Making assumptions about others’ identity or experience
- Advocating for or encouraging any of the above behaviors
Scope
This Code of Conduct applies in all project spaces, including:- GitHub repository (issues, pull requests, discussions)
- Project documentation
- Code comments and commit messages
- Email communications
- Social media when representing the project
- Any other forum where you represent the Aya community
Enforcement
Reporting Issues
If you experience or witness unacceptable behavior, please report it to: Email: [email protected] All reports will be:- Handled with discretion and confidentiality
- Reviewed and investigated promptly and fairly
- Responded to within 48 hours (acknowledgment) and 7 days (resolution)
Enforcement Guidelines
Project maintainers will follow these Community Impact Guidelines:1. Correction
Community Impact: Use of inappropriate language or other unprofessional behavior. Consequence: A private, written warning with clarity around the violation and explanation of why the behavior was inappropriate. A public apology may be requested.2. Warning
Community Impact: A violation through a single incident or series of actions. Consequence: A warning with consequences for continued behavior. No interaction with involved parties for a specified period. Violating these terms may lead to a temporary or permanent ban.3. Temporary Ban
Community Impact: A serious violation of community standards, including sustained inappropriate behavior. Consequence: Temporary ban from all project interaction for a specified period. No public or private interaction with the community is allowed during this time.4. Permanent Ban
Community Impact: Demonstrating a pattern of violations, sustained inappropriate behavior, harassment, or aggression. Consequence: Permanent ban from all project interaction.Technical Conduct Standards
In addition to general conduct, we expect technical professionalism:Code Review Standards
Code Review Standards
When reviewing code:✅ Do:
- Focus on the code, not the person
- Explain the “why” behind suggestions
- Offer specific, actionable feedback
- Recognize good work and improvements
- Be patient with different experience levels
- Use harsh or dismissive language
- Make assumptions about the author’s knowledge
- Nitpick without explaining the importance
- Demand changes without discussion
Issue and Discussion Standards
Issue and Discussion Standards
When participating in issues and discussions:✅ Do:
- Search for existing issues before creating new ones
- Provide reproduction steps for bugs
- Stay on topic and contribute constructively
- Accept maintainer decisions gracefully
- Hijack threads with unrelated topics
- Demand features or immediate fixes
- Argue endlessly about closed decisions
- Use issues for support questions (use Discussions instead)
Git Commit Standards
Git Commit Standards
Maintain professionalism in commit messages:✅ Do:
- Write clear, descriptive commit messages
- Follow Conventional Commits format
- Keep language professional and concise
- Use profanity or offensive language
- Include personal frustrations or complaints
- Write vague messages like “fix stuff” or “wip”
Attribution
This Code of Conduct is adapted from:- Contributor Covenant v2.1
- @eser/directives - Our broader organizational guidelines
Questions?
If you have questions about this Code of Conduct, please:- Review the @eser/directives for additional context
- Open a GitHub Discussion for clarification
- Contact the maintainers at [email protected]
By participating in the Aya project, you agree to abide by this Code of Conduct. Violations may result in removal from the project community.