> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/learn-more/community/community-guidelines.md).
# Community Guidelines
π€ Hyperswitch Community Code of Conduct & Slack Guidelines
Version 1.0 | Last updated: April 2025
Welcome to the Hyperswitch community! This is a space where developers, contributors, and product builders collaborate to create the future of open-source payments. To keep this space welcoming, productive, and respectful, all members must follow the Code of Conduct and Slack guidelines below.
### π§ Code of Conduct
#### Our Pledge
We are committed to providing a harassment-free experience for everyone, regardless of age, race, gender identity, disability, level of experience, nationality, or personal background. We pledge to behave in ways that foster a positive and inclusive environment.
#### Expected Behavior
* Be respectful, kind, and inclusive
* Assume good intent; seek to understand before judging
* Share feedback constructively and with empathy
* Help others when you can; ask for help when needed
* Use appropriate channels and keep discussions relevant
#### Unacceptable Behavior
* Harassment, hate speech, discrimination, or threats
* Trolling, personal attacks, or aggressive criticism
* Sharing private information without consent
* Excessive self-promotion or unsolicited DMs
### π¬ Slack Participation Guidelines
#### 1. Be a Good Citizen
* Keep discussions respectful and on-topic
* Avoid heated arguments β move complex topics to threads
* Use inclusive language and emoji reactions to show appreciation
#### 2. Use Threads & Channels Properly
* Always reply in threads to avoid noise
* Use the right channels:
* \#dev-support β Technical questions here
* \#general β regular business discussion or Non-tech discussion
* Avoid cross-posting the same message in multiple channels
#### 3. Ask Good Questions
* Include relevant context: error logs, code snippets, links
* Be patient and avoid tagging multiple team members unless urgent
#### 5. Security, Privacy & Respect
* Donβt share sensitive data (API keys, access tokens, etc.)
* Donβt screenshot or share Slack content outside without permission
* Respect others' time and privacy in DMs
### π§ Moderation & Admins
Community moderators are here to ensure the space remains safe and welcoming.\
They may take action at their discretion to uphold these guidelines.
π© Contact admins: DM @Neeraj Kumar in Slack
### π Quick Links
* [π Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
* [π Hyperswitch Website](https://hyperswitch.io)
* [π§βπ» GitHub Repository
](https://github.com/juspay/hyperswitch)\\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hyperswitch.io/learn-more/community/community-guidelines.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.