Centralize Bugs, Feature Requests & Questions in GitHub Issues/Discussions

[yogi4]

Objective

Move all bug reports, feature requests, and questions into OpenCHAMI’s public GitHub Issues & Discussions so that:

1. Conversations are transparent and searchable.
2. Contributors can self‑serve (find previous answers, avoid duplicates).
3. Core maintainers can prioritize work from a single, public backlog.

---

Transition Steps

Phase	What to Do	Owner	Target Date
1. Announce	Post this guideline in Slack/Matrix & pin it.	Maintainers	Week 0
2. Freeze Private Channels	Answer questions with a polite redirect link to GitHub.	Everyone	Immediately
3. Migrate Open Threads	Connect active Slack/Matrix threads to Issues or Discussions (use templates).	Original author & maintainers	By Week 2
4. Review & Label Backlog	Apply correct labels (bug, enhancement, question, etc.) and triage into the project board.	Triage team	Week 2‑3
5. Iterate	Run a 15‑min triage segment in each community call; close stale items every 60 days.	Maintainers	Ongoing

---

Where to File What

Use‑case	Issue	Discussion
Bug report	✔︎
Feature request	✔︎
“How do I…?” / design help		✔︎
Docs clarification	✔︎
RFC / big‑picture design		✔︎

Tip: If unsure, start a Discussion; maintainers can promote it to an Issue.

---

Label & Template Conventions

Label	When to Apply
bug	Reproducible defect in current release
enhancement	New capability or improvement
good first issue	≤ ½‑day effort, clear steps
needs‑info	Waiting on reporter feedback (auto‑close after 14 days)
question	Pure Q&A items (Discussions only)

Templates (stored in .github/ISSUE_TEMPLATE/ To Be Created)

• bug_report.md – env info & reproduction steps
• feature_request.md – use‑case & acceptance criteria
• discussion_template.md – lightweight, free‑form

---

Community Etiquette

• Search first – duplicates will be closed.
• Be specific: logs, screenshots, version info.
• Keep one topic per Issue/Discussion.
• Use reactions and comments.
• Respect the Code of Conduct; be kind and concise.

---

Roll‑Out Timeline (Suggested)

• Week 0 (today): Announce & pin guidelines.
• Week 1: All new bugs/questions redirected to GitHub.
• Week 2: Legacy threads migrated; first triage session.
• Week 4: Review adoption; adjust labels or templates if needed.

---

Need Help?

Open a Discussion with the meta tag or mention @openchami/maintainers for assistance.