Move to new style issue template system (#8898)

* Move to new style issue template system

This lets us have a template for each type of issue, notably this includes a template for requesting a CI image update.

* Fix checkboxes

* Codify the use of Discourse rather than raising issues

* Change CI to CI Image and introduce CI Issue template

* Fix poor english

* Add more tags where we have them

* CI Issue -> CI Problem

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,27 @@
+---
+name: "\U0001F41B Bug report"
+about: To help the developer act on the issues, please include a description of your environment, preferably a minimum script to reproduce the problem.
+title: "[Bug] "
+labels: "type: bug"
+
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
+
+Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
+
+### Expected behavior
+
+What you were expecting
+
+### Actual behavior
+
+What actually happened
+
+### Environment
+
+Any environment details, such as: Operating System, TVM version, etc
+
+### Steps to reproduce
+
+Preferably a minimal script to cause the issue to occur.

.github/ISSUE_TEMPLATE/ci-image.md

@@ -0,0 +1,29 @@
+---
+name: "\U0001F40B Update CI Docker Image"
+about: Provide information on CI Docker Images requiring updates
+title: "[CI Image] "
+
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
+
+Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
+
+- [ ] S0. Reason: For example, a blocked PR or a feature issue
+
+- [ ] S1. Tag of nightly build: TAG. Docker hub: https://hub.docker.com/layers/tlcpackstaging/ci_cpu/...
+
+- [ ] S2. The nightly is built on TVM commit: TVM_COMMIT. Detailed info can be found here: https://ci.tlcpack.ai/blue/organizations/jenkins/docker-images-ci%2Fdaily-docker-image-rebuild/detail/daily-docker-image-rebuild/....
+
+- [ ] S3. Testing the nightly image on ci-docker-staging: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/...
+
+- [ ] S4. Retag TAG to VERSION:
+```
+docker pull tlcpackstaging/IMAGE_NAME:TAG
+docker tag tlcpackstaging/IMAGE_NAME:TAG tlcpack/IMAGE_NAME:VERSION
+docker push tlcpack/IMAGE_NAME:VERSION
+```
+
+- [ ] S5. Check if the new tag is really there: https://hub.docker.com/u/tlcpack
+
+- [ ] S6. Submit a PR updating the IMAGE_NAME version on Jenkins

.github/ISSUE_TEMPLATE/ci-problem.md

@@ -0,0 +1,22 @@
+---
+name: "\U0000274C CI Problem"
+about: To help the developers act on these problems, please give us as many details of the CI failure as possible.
+title: "[CI Problem] "
+
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
+
+Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
+
+### Branch/PR Failing
+
+Please provide a link to the PR that has failed to run CI.
+
+### Jenkins Link
+
+Provide a link to the specific run that has failed.
+
+### Flakiness
+
+Have you seen this multiple times in this branch or in other branches?

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false  # default: true
+contact_links:
+- name: 💬 Discourse
+  url: https://discuss.tvm.apache.org/
+  about: Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first 😺

.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/feature-tracking.md

@@ -1,7 +1,14 @@
-Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :)
+---
+name: "\U0001F527 Feature Tracking"
+about: List clear, small actionable items so we can track the progress of the change.
+title: "[Tracking Issue] "
+labels: type:rfc-tracking
 
-Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
 
-For bug reports, to help the developer act on the issues, please include a description of your environment, preferably a minimum script to reproduce the problem.
+Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
 
-For feature proposals, list clear, small actionable items so we can track the progress of the change.
+### This issue is to track progress for FEATURE NAME
+- [ ] P1. Title of this piece of the feature (PR link if available)