DispatchAtlasCommunity
DispatchAtlas community and governance surfaces — where to ask questions, propose changes, and engage with maintainers around the toolkit.
DispatchAtlas community channels favor maintainable, structured surfaces over activity signals. Everything listed here exists today; nothing is aspirational.
💬 Where To Talk
| Channel | Use it for | Entry point |
|---|---|---|
| GitHub Issues | Bug reports, documentation issues, feature requests, questions, and non-sensitive security notes — five structured forms keep reports public-evidence-safe. | Issue forms |
| GitHub Discussions | Announcements, ideas, Q&A, and show-and-tell — four templated categories. | Discussions |
| Security reports | Sensitive disclosures, kept out of public issues. | Security policy |
| Support routing | The full channel map, including documentation and troubleshooting links. | SUPPORT.md |
| Sponsorship | GitHub Sponsors for the maintainer. | Sponsor |
There is no chat server. If one is added later, it will be announced through the Discussions announcements category and linked here.
🤝 How To Contribute
The contribution guide maps intents to folders and
lists the local check matrix. The lifecycle — propose, align, implement,
review, merge — and the single-maintainer decision model are recorded in
GOVERNANCE.md.
All channels operate under the
code of conduct.
🛡️ Ground Rules
- Use the issue forms rather than blank issues so reports stay structured.
- Never post credentials, private evidence, exploit details, or unpublished vulnerability material in public channels — route those through the security policy.