Contact us¶
Use GitHub as the default coordination channel so product questions, bugs, and contribution context remain visible to the community.
| Need | Where to go | What to include |
|---|---|---|
| Report a bug or broken workflow | GitHub Issues | Version, environment, reproduction steps, expected behavior, actual behavior, and relevant logs. |
| Propose a feature or datasource | GitHub Issues | Scenario, datasource type, user role, expected outcome, and why the current workflow is insufficient. |
| Join the community group | README Community | Scan the QR code in the README to discuss product usage, roadmap, and adoption scenarios. |
| Improve docs | Pull requests | Page path, proposed wording, screenshots if visual behavior changed, and validation steps. |
| Contribute code | Contributing | Scope, linked issue, tests or smoke checks, and any migration or compatibility notes. |
| Share a scenario case | Scenario cases | Business context, sample schema or data shape, expected analysis path, and demo-safe constraints. |
| Security or data exposure concern | GitHub Security Advisories | Redacted impact description and affected area. Do not include secrets, credentials, or private data in the initial report. |
Before opening an issue¶
- Search existing issues to avoid duplicate reports.
- Check whether the problem reproduces on the latest
mainbranch. - Include enough context for maintainers to reproduce the problem without access to private systems.
For public examples, keep screenshots and logs sanitized. DataFoundry is designed around governed data work, so community reports should follow the same discipline.