Issue and question routing
Use a public issue only for a reproducible, non-sensitive project problem or a considered feature proposal. The maintainer currently reviews and decides project changes. Labels describe intent and priority; they do not create an assignment, review commitment, or release date.
Route by subject
Section titled “Route by subject”| Subject | Route |
|---|---|
| Reproducible project defect | Public bug report, with a minimal reproduction and versions. Remove secrets, access links, buyer records, and learner data. |
| Feature or documentation idea | Public proposal form. State the problem, current workaround, scope fit, and observable acceptance criteria. A proposal is not a commitment to implement or support a feature. |
| Setup or project usage question | Contact project support; maintainer availability varies. If the owner later enables GitHub Discussions, use its Q&A category for non-sensitive project questions. |
| Course purchase, refund, or learner access | Contact the owner of the site where the course was purchased. StratoLMS maintainers cannot inspect or change a creator’s independent purchase records. |
| Security vulnerability | Follow SECURITY.md and report privately. Do not create a public issue or paste exploit details into Discussions. |
| Conduct concern | Follow the private reporting route in CODE_OF_CONDUCT.md. |
GitHub Discussions and funding links remain conditional on owner setup and verification. Until a destination has been enabled and checked, keep the existing issue, security, conduct, and email routes. Do not create a public issue as a substitute for a private report.
Turn repeated answers into documentation
Section titled “Turn repeated answers into documentation”When the same setup answer recurs, remove private details, verify the command
against the current source, and update the narrow guide under docs/. Link the
relevant guide in future answers. Do not publish a support conversation, learner
record, credential, private provider event, or unverified account state as an
example.
The prepared label meanings are recorded in .github/labels.yml.
They are a manual inventory; no automatic triage or label-creation bot is
configured.