Community

How to get involved in Bondy — Bondy Connect and Bondy, the language — as an open-source contributor, and how to reach the team on Zulip.

Bondy is built in the open, on the BEAM, under Apache-2.0 — both Bondy Connect (the application networking platform, WAMP router, API gateway and event mesh) and Bondy, the declarative language. Everything happens in public, and contributions of every size are welcome: code, docs, examples, bug reports, and design discussion.

Where the work happens ​

  • Source & issues — the code, the roadmap, and "good first issues" live on GitHub.
  • Real-time chat — day-to-day discussion, questions and design debate happen on Zulip (see below).
  • Docs — reference and guides are at developer.bondy.io.

The Zulip workspace ​

We use Zulip rather than Slack or Discord because its topic-based threading keeps long-running technical discussion legible — every message lives under a channel and a topic, so conversations don't scroll away.

Getting started:

  1. Join the workspace with this invitation link. Public channels are also readable on the web without an account.
  2. Subscribe to the channels relevant to you — start with #Announcements and #Newcomers.
  3. Post under a topic. Pick an existing topic in a channel, or start a new one with a short, descriptive name. This is the one habit that makes Zulip work.
  4. Be kind and be specific. Link code, share errors verbatim, and assume good faith. Everything here, on Zulip and on GitHub alike, follows our Code of Conduct.

Channels ​

Each channel below has its own page with its current topics and how to take part.

Community & General

Language

Protocols

Platform

Development Process

Help & Learning

DEV TOOLS

Ways to contribute beyond chat ​

  • Pick up a good first issue on GitHub, or open one describing a bug you hit.
  • Improve the docs — corrections and examples are hugely valuable.
  • Propose a change via an RFC in #Governance for anything cross-cutting.
  • Help others in #Newcomers once you've found your footing.