Support and community
Where to ask Flux questions, report bugs, and chat with other users — and which channel fits which kind of question.
Flux is an open-source project. Support is community-driven; there is no commercial support contract in 0.56.0.
Where to ask
GitHub Issues — bug reports and confirmed feature requests
Use for:
- Reproducible bugs. Include the Flux version (
pip show flux-core), Python version, OS, a minimal reproduction, and the error message or unexpected behavior. - Confirmed feature requests, ideally after discussion in another channel.
- Security issues that are not severe enough for private disclosure (see below).
Location: the flux repository on GitHub. Search before filing — duplicates are common.
GitHub Discussions — questions and design conversations
Use for:
- “How do I do X with Flux?” questions.
- Design feedback on proposed features.
- Comparisons against other tools.
- Showing off what you built (a good way to find collaborators).
Discussions stay open longer than Issues and are easier to find via search later.
Real-time chat
If a Discord or Slack server exists, the link is in the main flux repository’s README.md and on the docs site footer. As of 0.56.0, the project does not run an official always-on chat channel — that may change as the community grows.
Security disclosures
For vulnerabilities that should not be discussed publicly, use GitHub’s security advisory flow on the flux repository, or email the maintainer addresses listed in the repository’s README.md (or MAINTAINERS file if present).
Do not open public Issues for unpatched vulnerabilities.
When to use which
| You want to | Use |
|---|---|
| Report a reproducible bug | Issue |
| Ask “how do I do X?” | Discussion |
| Propose a new feature | Discussion first, Issue when the design is settled |
| Find someone to pair-debug with | Discussion or chat |
| Report a security concern | Security advisory or maintainer email |
| Confirm whether a behavior is intended | Discussion |
What to include in a bug report
A bug report that lands is usually one with: the Flux version, the Python version, the OS, a 10-30 line reproduction script, the full traceback, and what you expected to happen instead. Reports without a reproduction are usually closed with a polite ask for more detail.
Response expectations
This is volunteer-supported. Maintainers triage Issues weekly; Discussions get answered when someone has time and interest. Critical bugs (data loss, security) move faster — flag them in the title.
Cross-references
- Contributing code — if your question turns into a PR
- Contributing docs — same for docs improvements
- Code of conduct — applies to every channel above