Community guidelines
The rules that govern OpenWA community spaces — GitHub issues, pull requests, and discussions. This page is the practical reference for the project's Code of Conduct: what's expected, what isn't, how to report a problem, and what enforcement looks like.
OpenWA adopts the Contributor Covenant, version 2.1 as its Code of Conduct. By participating in any community space you agree to uphold it. The covenant text is the binding document; the summary below is for orientation, not a substitute.
Code of Conduct at a glance
| Item | Value |
|---|---|
| Standard | Contributor Covenant 2.1 |
| Canonical text | Contributor Covenant 2.1 |
| In-repo copy | CODE_OF_CONDUCT.md |
| Scope | All project spaces: issues, pull requests, discussions, and any space representing OpenWA |
| Reporting contact | yudhi@rmyndharis.com |
| Enforcement | Project maintainer |
Expected behavior
- Be welcoming, patient, and respectful in every interaction.
- Assume good intent. Give and accept constructive feedback gracefully.
- Focus on what is best for the community and the project.
- Help newcomers and answer questions where you can.
Unacceptable behavior
- Harassment, insults, or personal or political attacks.
- Trolling or deliberately derailing discussions.
- Publishing another person's private information without their explicit permission.
- Spam, excessive self-promotion, or persistent off-topic content.
- Any conduct a reasonable person would find inappropriate in a professional setting.
The full list of standards, including the four-tier enforcement guidelines, is in the Contributor Covenant 2.1 text.
Where to participate
| Space | Use it for |
|---|---|
| GitHub Issues | A reproducible defect with steps and expected versus actual behavior, a crash or a wrong API response, a regression after an upgrade, documented behavior contradicted by what you observe, and feature requests. Use the issue templates. |
| GitHub Discussions | Setup and configuration help, provider-specific quirks (proxy vendors, hosting platforms), network and firewall questions, "is X possible" and "what is the best way to Y", ideas, and sharing what you've built |
When in doubt, open a Discussion. It can be promoted to an issue once a defect is confirmed, and a large share of opened issues turn out to be configuration, provider, or environment questions rather than defects. An issue in the gray zone is labeled needs-info, not-a-bug, or move-to-discussions; one that proves environmental or provider-side is closed and continued in Discussions. upstream-blocked marks a report that is waiting on WhatsApp or an upstream library and has no OpenWA-side fix.
Before opening an issue, check the troubleshooting reference and search existing issues to avoid duplicates. To contribute code or documentation, follow the contributing guide.
Reporting a concern
Report conduct concerns privately to the project maintainer:
- Email:
yudhi@rmyndharis.com
Every report is reviewed and investigated promptly and fairly, and the reporter's privacy is respected. Include what happened, where, and when, along with any links or screenshots that help establish context.
Do not report a security vulnerability through a conduct report, a public issue, or a discussion. Follow the disclosure process in the repository's SECURITY.md instead.
Enforcement
Project maintainers are responsible for clarifying the standards of acceptable behavior and will take fair, proportionate corrective action in response to any conduct they deem inappropriate. This includes the right to edit, remove, or reject comments, commits, code, and other contributions that violate these guidelines, and to apply the Contributor Covenant's four-tier escalating responses — Correction, Warning, Temporary Ban, and Permanent Ban — depending on severity.
Reporter privacy is maintained throughout. Maintainers who do not follow or enforce the Code of Conduct in good faith may face consequences as determined by the project's leadership.
Next steps
- Contributing guide — how to open a pull request that gets merged.
- Troubleshooting reference — check this before filing an issue.
- Community integrations — projects built by the community.