mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-07-26 11:49:16 +00:00
Anso
7c759ff2b7
Adds the github key to FUNDING.yml and links GitHub Sponsors from README and SUPPORT so both channels are visible; the org still needs to complete GitHub's Sponsors onboarding for the button to render.
2.0 KiB
2.0 KiB
Getting help with Sencho
Sencho is a solo-maintained project. Here is what to expect.
Where to ask
- Setup, configuration, "how do I" questions → Documentation
- Discussion, share your setup, propose ideas → GitHub Discussions
- Bugs, regressions, broken features → Bug report
- Feature requests → Feature request
- Security vulnerabilities → SECURITY.md. Do not open a public issue.
- Licensing, billing, refunds → licensing@sencho.io
- Support the project → GitHub Sponsors or Buy Me a Coffee. Sponsorship is not required and does not change support response times; it helps fund the work.
Response times
Sencho is built by a single maintainer. Volunteer responses target:
- Security reports: 72 hours initial response (committed in SECURITY.md)
- Bug reports: a few days, typically within a week
- Feature requests: triaged but not always replied to individually; check the roadmap
- Discussions questions: community-first; the maintainer joins when possible
There is no SLA. The paid Admiral tier gets priority for licensing-related issues through the email above. A formal paid-support tier may follow 1.0.
What is in scope
- Bugs in shipped functionality, on a supported deployment (Docker Compose or
docker runwith the documented mounts). - Setup questions where the docs are unclear; tell us which page confused you.
- Feature requests that fit Sencho's scope (Docker Compose control plane for homelab and small fleets).
What is out of scope
- Generic Docker, networking, or Compose troubleshooting unrelated to Sencho.
- Custom modifications, forks, or non-default deployments.
- Migration help from competing tools beyond what the docs already cover.