Discussion-First Workflow

[rkuester]

Mujina uses a discussion-first workflow for contributions. Bug reports, feature
requests, and questions start as GitHub Discussions, then graduate to Issues in
the tracker after community input and maintainer review.

The flow:
Discussion 🗨️ → Confirmation ✅ → Issue 📋 → Pull Request 🔀

What This Means

All issues in the tracker are actionable. When you browse the issue
tracker, every item is vetted, understood, and ready to be worked on. No vague
reports, no duplicates, no "won't fix" issues cluttering the list.

Discussions are where we figure things out. Bug reports get refined with
diagnostic info. Feature ideas get shaped by community feedback. Questions get
answered. Once something is clear and actionable, it becomes an issue.

You get feedback early. Before investing time implementing a feature, you can
discuss the approach and ensure it aligns with project goals.

How to Participate

Reporting a Bug

Open an "Issue Triage" discussion with:

• Clear description of the problem
• Expected vs. actual behavior
• Reproduction steps
• Logs, hardware info, configuration

Proposing a Feature

Open an "Ideas" discussion to discuss the feature and gather feedback.

Asking Questions

Use the Q&A category for setup, usage, or troubleshooting questions.

Contributing Code

Browse the issue tracker for work items. Look for the good first issue label
for beginner-friendly tasks.

Quick Fixes Welcome

Trivial improvements—typo fixes, wording improvements, log level adjustments,
documentation clarifications—can skip the discussion and go straight to a PR.

Credit

This workflow is adapted from Ghostty's contribution model. Thanks to
Mitchell Hashimoto and contributors for the pattern!

---

Questions? Ask below!