chore: import upstream snapshot with attribution

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,32 @@
+---
+name: "\U0001F41B Bug report"
+about: Please include a description of your environment, preferably a minimum script to reproduce the problem. Find the list of label tags at https://github.com/apache/tvm/labels.
+title: "[Bug] "
+labels: "needs-triage, type: bug"
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.apache.org/ 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.
+
+### Triage
+
+Please refer to the list of label tags [here](https://github.com/apache/tvm/labels) to find the relevant tags and add them below in a bullet format (example below).
+
+* needs-triage

.github/ISSUE_TEMPLATE/ci-problem.md

@@ -0,0 +1,28 @@
+---
+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. Find the list of label tags at https://github.com/apache/tvm/labels.
+title: "[CI Problem] "
+labels: "needs-triage, type:ci"
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.apache.org/ 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?
+
+### Triage
+
+Please refer to the list of label tags [here](https://github.com/apache/tvm/labels) to find the relevant tags and add them below in a bullet format (example below).
+
+* needs-triage

.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.apache.org/ 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/documentation.md

@@ -0,0 +1,26 @@
+---
+name: "\U0001F4C4 Documentation"
+about: Use this template to suggest additions and changes to the documentation. Find the list of label tags at https://github.com/apache/tvm/labels.
+title: "[Docs] "
+labels: "needs-triage, type: doc"
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.apache.org/ 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.
+
+### Documentation Title & Type
+
+Include the title of the document (e.g. "Getting Started with TVM"), and the type of documentation (e.g. user docs, developer docs, tutorials)
+
+### Additions/Changes Requested
+
+If an RFC/discuss post exists, link it here.
+
+Otherwise, specify what actions should be taken to provide additional clarity/readability/reproducibility to the document. Include code snippets from the previous documentation if applicable.
+
+### Triage
+
+Please refer to the list of label tags [here](https://github.com/apache/tvm/labels) to find the relevant tags and add them below in a bullet format (example below).
+
+* needs-triage

.github/ISSUE_TEMPLATE/feature-tracking.md

@@ -0,0 +1,19 @@
+---
+name: "\U0001F527 Feature Tracking"
+about: List clear, small actionable items so we can track the progress of the change. Find the list of label tags at https://github.com/apache/tvm/labels.
+title: "[Tracking Issue] "
+labels: "needs-triage, type:rfc-tracking"
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.apache.org/ 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.
+
+### This issue is to track progress for FEATURE NAME
+- [ ] P1. Title of this piece of the feature (PR link if available)
+
+### Triage
+
+Please refer to the list of label tags [here](https://github.com/apache/tvm/labels) to find the relevant tags and add them below in a bullet format (example below).
+
+* needs-triage

.github/ISSUE_TEMPLATE/flaky-test.md

@@ -0,0 +1,24 @@
+---
+name: "\U00002744 Flaky Test"
+about: Report flaky tests, make sure to include link to CI runs, a sample failure log, and the name of the test(s). Find the list of label tags at https://github.com/apache/tvm/labels.
+title: "[Flaky Test] "
+labels: "needs-triage, test: flaky"
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.apache.org/ 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:
+
+These tests were found to be flaky (intermittently failing on `main` or failed in a PR with unrelated changes). As per [the docs](https://github.com/apache/tvm/blob/main/docs/contribute/ci.rst#handling-flaky-failures), these failures will be disabled in a PR that references this issue until the test owners can fix the source of the flakiness.
+
+### Test(s)
+
+- `tests/python/some_file.py::the_test_name`
+
+### Jenkins Links
+
+- Please provide link(s) to failed CI runs. If runs are for a PR, explain why your PR did not break the test (e.g. did not touch that part of the codebase)
+
+### Triage
+
+Please refer to the list of label tags [here](https://github.com/apache/tvm/labels) to find the relevant tags and add them below in a bullet format (example below).
+
+* needs-triage