Help build open customer messaging infrastructure
Opencom is open source and actively evolving. Contributions across product, docs, and developer tooling are all high leverage.
We optimize for pragmatic contributions: focused scope, clear testing, and docs updates when behavior changes. If you are not sure where to start, begin with labeled issues and discussions.
Report Bugs
Found something broken? Share repro details so we can fix it quickly.
Submit PRs
Pick up an issue, implement cleanly, and ship a scoped pull request.
Improve Docs
Clarify setup, architecture, and troubleshooting docs for new users.
Join Discussions
Share product ideas and implementation feedback with the core team.
Getting started docs (canonical)
Detailed setup and verification instructions live in GitHub docs so landing content stays minimal and up to date.
Minimal local bootstrap
If you just want a local contributor environment quickly, use the repo bootstrap script first, then follow the canonical docs below for package-specific workflows.
git clone https://github.com/opencom-org/opencom.git
cd opencom
./scripts/setup.shContributing Guide
Canonical contributor workflow: setup, conventions, verification, and PR expectations.
Setup, Self-Host, and Deploy
Bootstrap script path, manual setup path, environment variables, and deployment profiles.
Testing and Verification
Focused package checks, E2E prep, and CI-equivalent verification commands.
Browse OSS Docs HubGood first issues
New contributors can start with focused tasks that have clear implementation boundaries.
Community resources
Ask questions, propose ideas, and review contribution standards.
Thanks to everyone contributing
Opencom exists because contributors turn ideas into shipped improvements.
Star us on GitHub