You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by ma...@apache.org on 2021/09/11 04:10:54 UTC

[tvm] branch main updated: add github issue template for docs (#8982)

This is an automated email from the ASF dual-hosted git repository.

masahi pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tvm.git


The following commit(s) were added to refs/heads/main by this push:
     new f0adc1b  add github issue template for docs (#8982)
f0adc1b is described below

commit f0adc1bf87dfe7e9b86549bfa65800838bb0d4ba
Author: Denise Kutnick <de...@octoml.ai>
AuthorDate: Fri Sep 10 21:10:28 2021 -0700

    add github issue template for docs (#8982)
---
 .github/ISSUE_TEMPLATE/documentation.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/.github/ISSUE_TEMPLATE/documentation.md b/.github/ISSUE_TEMPLATE/documentation.md
new file mode 100644
index 0000000..a1c1fac
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/documentation.md
@@ -0,0 +1,22 @@
+---
+name: "\U0001F4C4 Documentation"
+about: Use this template to suggest additions and changes to the documentation.
+title: "[Docs] "
+labels: "type: doc"
+
+---
+
+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.
+
+### 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.
+