# Support

Use the right channel so requests are handled quickly and in context. When in doubt, Discussions is always a safe starting point.

## Where to ask what

| I want to… | Go here |
|---|---|
| Ask a usage question or get help | [GitHub Discussions](https://github.com/mick-gsk/drift/discussions) |
| Report a false positive / false negative | [FP/FN template](https://github.com/mick-gsk/drift/issues/new?template=false_positive.md) |
| Report a bug | [Bug report template](https://github.com/mick-gsk/drift/issues/new?template=bug_report.md) |
| Suggest a feature or improvement | [Feature request template](https://github.com/mick-gsk/drift/issues/new?template=feature_request.md) |
| Propose a contribution before coding | [Contribution proposal](https://github.com/mick-gsk/drift/issues/new?template=contribution_proposal.md) |
| Submit a small docs or typo fix | Open a PR directly — no issue needed |
| Report a security vulnerability | [SECURITY.md](SECURITY.md) — do not open a public issue |
| Understand how to contribute | [CONTRIBUTING.md](CONTRIBUTING.md) |

## Before opening a thread

1. Check the docs: <https://mick-gsk.github.io/drift/>
2. Search existing issues and discussions
3. Include drift version, Python version, OS, and a minimal reproduction when possible

## Maintainer response expectations

- First response target: within 72 hours
- If you do not get a reply in that window, ping the thread once

## Long-term maintenance

Drift is maintained by [Mick Gottschalk](https://github.com/mick-gsk) as an independent open-source project.
All signal logic, benchmarks, and release automation are fully documented and reproducible.
If your team relies on drift in CI, consider [sponsoring](https://github.com/sponsors/mick-gsk) to support continued development.
