Contributor Covenant Code of Conduct

Our Pledge

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.

Our Standards

Examples of Behavior That Contributes to a Positive Environment

• Demonstrating empathy and kindness toward other people

  • Acknowledge that everyone has different levels of experience and expertise
  • Be patient with newcomers who may not be familiar with the project's conventions or technical stack
  • Offer constructive help and guidance when someone asks questions

• Being respectful of differing opinions, viewpoints, and experiences

  • Recognize that there are often multiple valid approaches to solving a technical problem, and engage in thoughtful discussion about trade-offs
  • Avoid dismissing ideas without providing constructive alternatives
  • Value diverse perspectives as a strength of the community

• Giving and gracefully accepting constructive feedback

  • Frame feedback in terms of the code or behavior, not the person
  • When receiving feedback, consider it as an opportunity to learn and improve
  • Thank reviewers for their time and effort in providing feedback

• Accepting responsibility and apologizing to those affected by our mistakes

  • Everyone makes mistakes; what matters is how we handle them
  • Correct mistakes promptly and learn from the experience
  • Acknowledge the impact of mistakes on others affected by them

• Focusing on what is best not just for us as individuals, but for the overall community

  • Consider the long-term impact of decisions on the project and community
  • Prioritize the health of the project over individual preferences
  • Share knowledge and help others grow in their abilities

Examples of Unacceptable Behavior

• The use of sexualized language or imagery, and sexual attention or advances of any kind

  • This includes but is not limited to: unwelcome sexual comments, jokes, or innuendos in code review, issue discussions, or community channels
  • Sexualized profile images or usernames are also not acceptable

• Trolling, insulting or derogatory comments, and personal or political attacks

  • Deliberately provoking or antagonizing other community members
  • Making disparaging remarks about someone's technical abilities
  • Engaging in flame wars or unproductive arguments

• Public or private harassment

  • Repeatedly contacting someone who has asked you to stop
  • Following someone across multiple platforms or communication channels
  • Intimidating or threatening behavior

• Publishing others' private information (physical or email address) without their explicit permission (also known as "doxxing")

  • This includes sharing personal information found through public records or social media without consent

• Other conduct which could reasonably be considered inappropriate in a professional setting

  • Excessive use of profanity
  • Sustained disruption of community events or discussions
  • Advocating for or encouraging any of the above behaviors

Enforcement Responsibilities

Community leaders 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.

Community leaders 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.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include:

• Using an official organization e-mail alias or communication asset
• Posting via an official project social media account
• Acting as an appointed representative at an online or offline event
• Engaging in project-related activities on GitHub (issues, PRs, discussions)
• Participating in project-related chat channels (Discord, Slack, etc.)

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at:

📧 srinivasbatthula05.offical@gmail.com

All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident.

What to Include in a Report

When reporting an incident, please include:

1. Your contact information (so we can follow up if needed)
2. Names or usernames of the individuals involved
3. Description of the behavior — what happened, and why you consider it a violation of this Code of Conduct
4. Date and time of the incident
5. Location where the incident occurred (e.g., GitHub issue #123, Discord channel, email thread)
6. Any supporting evidence — screenshots, links, or other documentation
7. Whether the incident is ongoing or has concluded

Response from Maintainers

You can expect the following from our enforcement team:

• Acknowledgment of your report within 24 hours
• Assessment of the situation within 72 hours
• Decision on appropriate action within 7 days for non-urgent matters
• Immediate action for situations involving active threats or harassment
• Follow-up communication about the outcome of your report

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an 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 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.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

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.

4. Permanent Ban

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.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq.

Translations are available at https://www.contributor-covenant.org/translations.