update github issue template

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,8 @@
 blank_issues_enabled: false
 contact_links:
+  - name: Feature Request
+    url: "https://github.com/dynamail/gosmtp/discussions/new?category=ideas"
+    about: "Please suggest new features in Discussions"
   - name: Question
-    url: "https://web.libera.chat/gamja/#emersion"
-    about: "Please ask questions in #emersion on Libera Chat"
+    url: "https://github.com/dynamail/gosmtp/discussions"
+    about: "Please ask questions in Discussions"

.github/ISSUE_TEMPLATE/issue_template.md

@@ -1,12 +1,28 @@
 ---
-name: Bug report or feature request
-about: Report a bug or request a new feature
+name: Bug report
+about: Report a bug
 ---
 
-<!--
+<!-- Please provide all of the information requested below. We're a small team and without all of this information it's not possible for us to help and your bug report will be closed. -->
 
-Please read the following before submitting a new issue:
+**What version of gosmtp are you using?**
 
-Do NOT create GitHub issues if you have a question about go-smtp or about the SMTP protocol in general. Ask questions on IRC in #emersion on Libera Chat.
+For example: v0.1.0
 
--->
+**What version of Golang are you using?**
+
+For example: v1.19
+
+**What operating system are you using?**
+
+For example: macOS, Windows
+
+**Reproduction Example**
+
+A public GitHub repo or steps that lead to a minimal reproduction of the bug. **Please do not link to your actual project**, what we need instead is a _minimal_ reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.
+
+A reproduction is **required** when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.
+
+**Describe your issue**
+
+Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.