lhumina_public/feedback
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
2 commits 1 branch 0 tags 31 KiB
Find a file
Exact
mik-tf 437f5d4ccc feat: bootstrap feedback repo (README + .forgejo/issue_template/) 
Two-commit PR setting up the public feedback channel that hero_cockpits feedback iframe lands users on.

- README: purpose, filing flow, team triage labels, privacy note, cross-links to hero_cockpit#1 + hero_os_tfgrid_deployer#1
- .forgejo/issue_template/{bug,feature,feedback}.md with appropriate labels

Forgejo-native template path (.forgejo/issue_template/ lowercase snake_case), not legacy .gitea/ISSUE_TEMPLATE/.
2026-05-20 22:00:31 +00:00
.forgejo/issue_template feat: bootstrap feedback repo (README + .forgejo/issue_template/) 2026-05-20 22:00:31 +00:00
README.md feat: bootstrap feedback repo (README + .forgejo/issue_template/) 2026-05-20 22:00:31 +00:00

README.md

Hero OS — Demo User Feedback

This repo is the public feedback channel for users of the Hero OS demo environment provisioned via hero_os_tfgrid_deployer.

Background: each demo user receives a TFGrid VM running Hero OS, accessed through their browser via a Forge-OAuth-gated public URL. The user-facing UI on the VM (hero_cockpit) embeds this repo's issue creation form so users can submit feedback directly without leaving the demo experience.

Filing feedback

You'll need a Forge account; the demo deployer issues you one as part of provisioning.

What this repo IS

  • A place for demo users to report what works, what doesn't, and what they wish existed
  • A communication channel back to the Hero OS team
  • Public — so other users can see what's already reported and pile on

What this repo is NOT

  • A support channel — the team responds when capacity allows, this is best-effort
  • A bug tracker for the underlying Hero OS codebase (those live in lhumina_code/ per-repo)
  • A production-incident reporting system — the demo environment is non-production and data loss is expected

For the team

User feedback lands here as issues. Triage flow:

  • Label triaged feedback with the relevant Hero OS component (e.g. hero_books, hero_slides, hero_cockpit).
  • If a bug requires a code-side fix, file the issue in the relevant lhumina_code/<service> repo, and cross-link back from here.
  • Use the acknowledged label when the team has read + accepted the feedback.
  • Use the shipped label when a feedback item has been addressed in a release.

Privacy

This repo is public. Don't paste secrets, tokens, private URLs, or sensitive personal data into issues. The cockpit's feedback form reminds users of this at submission time.

Related