split issue templates: bug report/enhancment/question

so that people are routed nicely :)

.github/ISSUE_TEMPLATE.md

@@ -1,26 +0,0 @@
-_Please read these instructions before submitting_
-
-**DELETE THIS TEMPLATE BEFORE SUBMITTING**
-
-_Only use GitHub issues to report bugs or feature requests, see
-https://www.packer.io/community.html_
-
-For example, _Timeouts waiting for SSH/WinRM_ are generally not bugs within packer and are better addressed by the mailing list. Ask on the mailing list if you are unsure.
-
-If you are planning to open a pull-request just open the pull-request instead of making an issue first.
-
-FOR FEATURES:
-
-Describe the feature you want and your use case _clearly_.
-
-FOR BUGS:
-
-Describe the problem and include the following information:
-
-- Packer version from `packer version`
-- Host platform
-- Debug log output from `PACKER_LOG=1 packer build template.json`.
-  Please paste this in a gist https://gist.github.com
-- The _simplest example template and scripts_ needed to reproduce the bug.
-  Include these in your gist https://gist.github.com
-  

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug Report
+about: You're experiencing an issue with Packer that is different than the
+documented behavior.
+---
+
+When filing a bug, please include the following headings if possible. Any
+example text in this template can be deleted.
+
+#### Overview of the Issue
+
+A paragraph or two about the issue you're experiencing.
+
+#### Reproduction Steps
+
+Steps to reproduce this issue
+
+### Packer version
+
+From `packer version`
+
+### Simplified Packer Buildfile
+
+If the file is longer than a few dozen lines, please include the URL to the
+[gist](https://gist.github.com/) of the log or use the [Github detailed
+format](https://gist.github.com/ericclemmons/b146fe5da72ca1f706b2ef72a20ac39d)
+instead of posting it directly in the issue.
+
+### Operating system and Environment details
+
+OS, Architecture, and any other information you can provide about the
+environment.
+
+### Log Fragments and crash.log files
+
+Include appropriate log fragments. If the log is longer than a few dozen lines,
+please include the URL to the [gist](https://gist.github.com/) of the log or
+use the [Github detailed format](https://gist.github.com/ericclemmons/b146fe5da72ca1f706b2ef72a20ac39d) instead of posting it directly in the issue.
+
+Set the env var `PACKER_LOG=1` for maximum log detail.

.github/ISSUE_TEMPLATE/feature_requests.md

@@ -0,0 +1,18 @@
+---
+name: Feature Request
+about: If you have something you think Packer could improve or add support for.
+
+---
+
+Please search the existing issues for relevant feature requests, and use the
+reaction feature
+(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
+to add upvotes to pre-existing requests.
+
+#### Feature Description
+
+A written overview of the feature.
+
+#### Use Case(s)
+
+Any relevant use-cases that you see.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,16 @@
+---
+name: Question
+about: If you have a question, please check out our other community resources
+instead of opening an issue.
+
+---
+
+Issues on GitHub are intended to be related to bugs or feature requests, so we
+recommend using our other community resources instead of asking here if you
+have a question.
+
+- Packer Guides: https://www.packer.io/guides/index.html
+- Discussion List: https://groups.google.com/group/packer-tool
+- Any other questions can be sent to the packer section of the [HashiCorp
+  forum](https://discuss.hashicorp.com/c/packer)
+- Packer community links: https://www.packer.io/community.html