Skip to content

docs: make issue forms user-friendly (drop engine/component jargon)#19

Merged
tamimbinhakim merged 2 commits into
masterfrom
docs/friendly-issue-forms
Jun 6, 2026
Merged

docs: make issue forms user-friendly (drop engine/component jargon)#19
tamimbinhakim merged 2 commits into
masterfrom
docs/friendly-issue-forms

Conversation

@tamimbinhakim

Copy link
Copy Markdown
Contributor

Why

The issue forms ask regular users things only a maintainer could answer:

  • Bug form had an Engine field (deepfilternet / bandit / demucs) and an internal Component dropdown (core / cli / cloud / …).
  • Quality form asked users to pick the engine — with options (BandIt Plus, Demucs mdx_q) that aren't even shipped anymore.

Changes (plain language, no jargon)

  • Bug report: "Where did this happen?" → Browser extension / Command-line tool / Desktop app / Website / Docs / Not sure. Dropped the freeform Engine field. Added an optional "which website?" and friendlier setup/log prompts.
  • Music-removal quality (renamed from "Separation-quality report"): replaced the engine dropdown with "Where did you use Sukoon?" — which tells us the engine without asking the user to know it — and reworded the problem kinds (e.g. "underwater sound", "audio and video out of sync").
  • Feature request: "Which part of Sukoon?" instead of Component; kept the ad-principle check (reworded to explain it), dropped the contributor-only sukoon-core checkbox.

All four templates validated as well-formed YAML.

🤖 Generated with Claude Code

tamimbinhakim and others added 2 commits June 6, 2026 11:26
Regular users can't answer "Engine (deepfilternet/bandit/demucs)" or pick an
internal "Component (core/cli/cloud/...)", and the quality form's engine options
(BandIt Plus, Demucs mdx_q) aren't even what ships now. Rewrites all three forms
in plain language:

- "Where did this happen?" with friendly options (Browser extension / CLI /
  Desktop app / Website / Docs / Not sure) instead of the Component dropdown.
- Removes the freeform "Engine" question from the bug form entirely.
- Quality form: replaces the engine dropdown with "Where did you use Sukoon?"
  (which implies the engine, no jargon) and plainer problem-kind wording.
- Feature form: friendly "Which part of Sukoon?" and a single ad-principle check
  (dropped the contributor-only sukoon-core checkbox).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tamimbinhakim tamimbinhakim merged commit b141a37 into master Jun 6, 2026
5 checks passed
@tamimbinhakim tamimbinhakim deleted the docs/friendly-issue-forms branch June 6, 2026 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant