Find us.
z4j is built in the open. Every feature decision, every bug report, every release lives on GitHub.
GitHub
Source code, issue tracker, pull requests, releases. Star the repo to follow releases.
Learn moreGitHub Discussions
General questions, show-and-tell, RFCs. The primary support channel.
Learn moreIssue tracker
Bug reports + feature requests. Security issues go to security@z4j.com, not here.
Learn moreChangelog
Every release, every change, dated. Lives on the docs site as the single source of truth.
Learn moreContact
Email addresses for support, security, sales, and press, plus a contact form for everything else.
Learn moreHow to contribute
Bug fixes
Open a PR against main. DCO sign-off required (git commit -s). Tests required for anything non-trivial.
New engine adapter
~300 LOC per adapter. Protocol is public + stable. The existing adapters are the reference.
New scheduler adapter
~200 LOC per adapter. Read + lifecycle operations supported today; create/update is an open contribution area.
Documentation
docs live in /docs on the main branch. Markdown. z4j.dev is auto-built from that content.
Triage
Helping new contributors land their first PR, labeling incoming issues, verifying bug reports.
Security
Find a bug, email security@z4j.com, get credit in the advisory. We welcome adversarial reviews.
How we behave here
We follow the Contributor Covenant 2.1. Translation: be respectful, assume good intent, disagree on the technical merits, let maintainers have the last word when the conversation stops being productive.
Harassment, personal attacks, or hostile behavior will get you banned. Reports go to conduct@z4j.com.
Start contributing
Open a Discussion to introduce yourself or float an idea, file an issue if you found a bug, or jump straight to a pull request. DCO sign-off (git commit -s) is the only ceremony, no CLA.