Community and Support
DUUMBI is developed in the open. Use the channel that matches what you need:
| Need | Best place |
|---|---|
| Usage question or design discussion | GitHub Discussions |
| Bug report with reproduction steps | GitHub Issues |
| Chat, orientation, or lightweight support | Discord |
| Source code and pull requests | hgahub/duumbi |
Before opening an issue
Section titled “Before opening an issue”Include the smallest useful reproduction:
- DUUMBI version or commit SHA
- operating system and CPU architecture
- command you ran
- relevant
.jsonld, intent, config, or registry input - expected result
- actual result, including error output
Do not include provider API keys, registry tokens, private source code, or unredacted credentials.
Documentation feedback
Section titled “Documentation feedback”Use the source repository issue tracker for documentation problems:
- stale install or provider setup instructions
- broken links
- missing CLI or JSON-LD reference material
- confusing Query, Agent, Intent, registry, or module guidance
Public docs live in
hgahub/duumbi-web/docs/src/content/docs.
Implementation and workflow documentation lives in
hgahub/duumbi/docs.
Contribution expectations
Section titled “Contribution expectations”DUUMBI changes should keep behavior, docs, and verification evidence aligned.
For user-facing changes, update the canonical docs site. For source-repo
workflow, architecture, automation, or testing changes, update the internal
docs in hgahub/duumbi/docs.
Before requesting review, include:
- the problem being solved
- affected commands, docs, or modules
- checks you ran
- any remaining risk or follow-up
Support boundaries
Section titled “Support boundaries”The current preview docs describe verified behavior or clearly marked preview constraints. Install-channel work is tracked separately, so packaged install instructions are updated only after a release path is verified. Provider setup docs describe supported direct providers and compatibility notes; they do not require users to choose or maintain default model IDs unless they are working with compatibility configuration.