[Release] simplify the pr template a little (dmlc#268)

.github/ISSUE_TEMPLATE/bug-report.md

@@ -25,15 +25,15 @@ Steps to reproduce the behavior:
 ## Environment
 
  - DGL Version (e.g., 1.0):
- - Backend Library & Version (e.g., PyTorch 0.4.1):
+ - Backend Library & Version (e.g., PyTorch 0.4.1, MXNet/Gluon 1.3):
  - OS (e.g., Linux):
  - How you installed DGL (`conda`, `pip`, source):
  - Build command you used (if compiling from source):
  - Python version:
- - CUDA/cuDNN version:
- - GPU models and configuration:
+ - CUDA/cuDNN version (if applicable):
+ - GPU models and configuration (e.g. V100):
  - Any other relevant information:
 
 ## Additional context
 
-<!-- Add any other context about the problem here. -->
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/documentation.md

@@ -7,4 +7,4 @@ about: Report an issue related to docs.dgl.ai
 ## 📚 Documentation
 
 <!-- Please specify whether it's tutorial part or API reference part-->
-<!-- A clear and concise description of what content in docs.dgl.ai is an issue.-->
+<!-- Describe the issue.-->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -5,11 +5,13 @@ about: Submit a proposal/request for a new DGL feature
 ---
 
 ## 🚀 Feature
-<!-- A clear and concise description of the feature proposal -->
+<!-- A brief description of the feature proposal -->
 
 ## Motivation
 
-<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
+<!-- Please outline the motivation for the proposal. Is your feature request
+related to a problem? e.g., I'm always frustrated when [...]. If this is
+related to another GitHub issue, please link here too -->
 
 ## Alternatives
 
@@ -21,4 +23,4 @@ about: Submit a proposal/request for a new DGL feature
 
 ## Additional context
 
-<!-- Add any other context or screenshots about the feature request here. -->
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/questions-help-support.md

@@ -6,8 +6,6 @@ about: Do you need support? We have resources.
 
 ## ❓ Questions and Help
 
-### Please note that this issue tracker is not a help forum and this issue will be closed.
-
-Our primary means of support is our discussion forum:
-
-- [Discussion Forum](http://discuss.dgl.ai/)
+<!-- Before proceeding, please note that we recommend
+using our discussion forum (https://discuss.dgl.ai) for
+general questions. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,28 +1,19 @@
-IMPORTANT: Please do not create a Pull Request without creating an issue first.
-
-Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
-
-Please provide enough information so that others can review your pull request:
-
 ## Description
-Explain the details for making this change. What existing problem does the pull request solve?
-
-## Test Plan
-Describe the test plan (required)
+<!-- Brief description. Refer to the related issues if existed.
+It'll be great if relevant reviewers can be assigned as well.-->
 
 ## Checklist
-### Essentials
 Please feel free to remove inapplicable items for your PR.
 - [ ] The PR title starts with [$CATEGORY] (such as [Model], [Doc], [Feature]])
 - [ ] Changes are complete (i.e. I finished coding on this PR)
 - [ ] All changes have test coverage
 - [ ] Code is well-documented
-- [ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change
+- [ ] To the my best knowledge, examples are either not affected by this change,
+      or have been fixed to be compatible with this change
 - [ ] Related issue is referred in this PR
 
-### Changes ###
+## Changes
+<!-- You could use following template
 - [ ] Feature1, tests, (and when applicable, API doc)
 - [ ] Feature2, tests, (and when applicable, API doc)
-
-## Comments ##
-Add any other context about the pull request here.
+-->