Support
Start with the public path whenever possible. Public questions improve the docs, surface real adoption friction, and help other teams solving the same upload problems.
Best channel for each request
Section titled “Best channel for each request”| Situation | Best path |
|---|---|
| Usage question or design discussion | GitHub Discussions |
| Reproducible bug | GitHub Issues |
| Docs gap or unclear example | GitHub Issues or a docs pull request |
| Vulnerability disclosure | SECURITY.md |
| Private rollout help or commercial discussion | Contact path below |
Community support
Section titled “Community support”Useful public entry points:
Private or commercial support
Section titled “Private or commercial support”Use the private path when the work cannot be handled well in public, for example:
- Rollout guidance for a production deployment.
- Architecture review for a multi-service upload workflow.
- Policy tuning for a sensitive or high-volume endpoint.
- A commercial support relationship.
What to expect:
- Scope is agreed in advance.
- Support is async unless another arrangement is made.
- There is no implied SLA unless explicitly contracted.
Contact
Section titled “Contact”- Private or commercial inquiry: pompelmideveloper@yahoo.com
- Commercial details: Enterprise support
Include your stack, versions, upload profile, and a concise description of the blocker.