miao.my

COMMUNITY / SUPPORT

Start with a reproducible signal.

This is MIAO’s public collaboration map: read the docs first, then choose the right issue, discussion or release record. MIAO is open source and self-hosted; community collaboration is not an enterprise SLA.

Browse issues ↗Read the docs

Choose the right route

BUG

Report a reproducible problem

Include minimal reproduction steps, the MIAO version or commit, browser/system details and a redacted error excerpt.

Open an issue ↗

IDEA

Suggest a capability

Describe the work problem, affected roles and acceptable boundaries. Check the docs and open issues first.

Join discussions ↗

SELF-HOSTING

Debug a deployment

Start with the self-hosting and operations docs, then share the deployment mode, commit, log summary and a reproducible command.

Read self-hosting docs

RELEASES

Confirm versions and changes

Use releases and the changelog to align versions, compatibility and rollback boundaries. Local success is not production acceptance.

Browse releases ↗

SECURITY

Do not paste security issues in public.

Never include tokens, passwords, internal addresses, complete production data or unredacted attachments in an issue, discussion or log. Prefer GitHub Security Advisories; if the repository does not show a private report entry, contact the maintainers to confirm a private channel.

Open private security report ↗

Support boundaries

  • Public support: docs, reproducible problems, code collaboration and release notes.
  • Self-hosting responsibility: model configuration, backups, credentials, networking and on-site operations stay with the deployer.
  • Upstream services: model, Jev, mail and paid API quotas or authorization require separate acceptance.
  • Response expectations: issues are triaged by reproducibility, impact and maintainer time; no enterprise SLA is promised.