Find us.
z4j is built in the open. Public discussions, issues, and release history are available 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 [email protected], not here.
Learn moreChangelog
Published release notes and dated changes live on the docs site.
Learn moreContact
Email addresses for general questions, security disclosure, licensing, and privacy, plus GitHub Discussions and Issues.
Learn morecontributing
How 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
Roughly 900 to 5,000 lines per adapter, depending on how much of the engine's control surface it can safely expose. The Protocol is public, and the existing adapters are the reference.
New scheduler adapter
Roughly 200 lines for a read-only surface, more where the adapter adds managed create, edit and pause. Current native integrations support dashboard management with their documented producer setup; new integrations must prove their advertised actions.
Documentation
Spotted a gap or an error on docs.z4j.com? Open an issue or a Discussion with the page and the correction, and a maintainer updates and redeploys the docs site.
Triage
Helping new contributors land their first PR, labeling incoming issues, verifying bug reports.
Security
Find a bug, email [email protected], and get credit in the release notes if you want it. We welcome adversarial reviews.
code of conduct
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 [email protected].
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.