For Freezer 0.5.2

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,13 +1,45 @@
 ---
 name: Bug report
-about: Create a report to help us improve
+about: Follow the instructions carefully on the next page.
 title: ''
 labels: 1 backlog, bug
 assignees: ryanheise
 
 ---
 
-<!--    ALL SECTIONS BELOW MUST BE COMPLETED   -->
+<!--
+
+        Note: Issues that don't follow these instructions will be closed,
+        therefore please read them carefully.
+
+        1. A bug report must demonstrate a bug in the plugin, and not merely a
+           bug in your app. Understand that this plugin WILL throw exceptions
+           or otherwise misbehave if not used in accordance with the
+           documentation. In order to verify that you have indeed found a bug,
+           you will need to make a reference to the documentation in order to
+           explain how the actual behaviour you experienced is different from
+           the behaviour that was documented. If the behaviour you want is
+           undocumented, please submit either a documentation request or a
+           feature request instead, whichever is more appropriate.
+
+        2. You must supply a link to a minimal reproduction project and explain
+           what steps I need to perform (as a user) in the app to reproduce the
+           bug. A minimal reproduction project can be created by forking this
+           project and making the minimal number of changes required to the
+           example to reproduce the bug. Do not post code directly into the bug
+           report, it must be a link to a git repo that I can clone and then
+           immediately run.
+
+        3. Leave all markdown formatting in this template intact. Do not modify
+           the section headings in any way, and insert your answers below each
+           section heading. Use code markdown (3 backticks) when inserting
+           errors and logs, not only for readability, but also to avoid issue
+           reference spamming using the # symbol.
+
+        THANK YOU :-D
+
+
+-->
 **Which API doesn't behave as documented, and how does it misbehave?**
 Name here the specific methods or fields that are not behaving as documented, and explain clearly what is happening.
 

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Community Support
+  - name: Stack Overflow
     url: https://stackoverflow.com/search?q=audio_service
-    about: Ask for help on Stack Overflow.
-  - name: New to Flutter?
+    about: Ask here if it's not a bug report, documentation request or feature request.
+  - name: Gitter
     url: https://gitter.im/flutter/flutter
-    about: Chat with other Flutter developers on Gitter.
+    about: Ask here if you want to have a live chat with other Flutter developers.

.github/ISSUE_TEMPLATE/documentation-request.md

@@ -1,6 +1,6 @@
 ---
 name: Documentation request
-about: Suggest an improvement to the documentation
+about: Follow the instructions carefully on the next page.
 title: ''
 labels: 1 backlog, documentation
 assignees: ryanheise
@@ -9,15 +9,19 @@ assignees: ryanheise
 
 <!--
 
-        PLEASE READ CAREFULLY!
+        Note: Issues that don't follow these instructions will be closed,
+        therefore please read them carefully.
 
+        1. This form is not intended for asking questions or asking for
+           support. For that, you are advised to ask your question on
+           StackOverflow or Gitter. Instead, this form is intended for people
+           who wish to help improve this plugin's documentation in a concrete
+           way.
 
-
-
-
-        FOR YOUR DOCUMENTATION REQUEST TO BE PROCESSED, YOU WILL NEED
-        TO FILL IN ALL SECTIONS BELOW. DON'T DELETE THE HEADINGS.
-
+        2. To that end, it is required that you link to the specific
+           page/section, and quote the words that are unclear (unless you are
+           proposing an entirely new section), and describe how you would like
+           it to be improved.
 
         THANK YOU :-D
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,6 +1,6 @@
 ---
 name: Feature request
-about: Suggest an idea for this project
+about: Follow the instructions carefully on the next page.
 title: ''
 labels: 1 backlog, enhancement
 assignees: ryanheise
@@ -9,15 +9,26 @@ assignees: ryanheise
 
 <!--
 
-        PLEASE READ CAREFULLY!
+        Note: Issues that don't follow these instructions will be closed,
+        therefore please read them carefully.
 
+        1. A prerequisite before requesting a feature is that you familiarise
+           yourself with the existing features by reading the API
+           documentation.
 
+        2. If it is unclear from the documentation whether an existing feature
+           is the one you want, this is a shortcoming of the documentation. In
+           this case, please submit a documentation request instead.
 
+        3. Do not use this form for asking questions. My goal is to provide
+           good documentation that answers your questions, and if the
+           documentation isn't doing its job, please submit a documentation
+           request to help me to improve it. Remember that the purpose of this
+           GitHub issues page is for plugin development and not for support
+           (community support is available via StackOverflow and Gitter).
 
-
-        FOR YOUR FEATURE REQUEST TO BE PROCESSED, YOU WILL NEED
-        TO FILL IN ALL SECTIONS BELOW. DON'T DELETE THE HEADINGS.
-
+        4. You must complete at least the first 3 sections below. Leave the
+           section headings intact, and insert your answers below each heading.
 
         THANK YOU :-D
 
@@ -26,13 +37,13 @@ assignees: ryanheise
 
 
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+<!-- A clear and concise description of what you want to happen. -->
 
 **Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+<!-- Add any other context or screenshots about the feature request here. -->