Refreshed contributing docs

.github/ISSUE_TEMPLATE.md

@@ -4,8 +4,9 @@
     remove the "is:open" filter from the search bar to include closed issues.
 
     Check the appropriate type for your issue below by placing an x between the
-    brackets. If none of the below apply, please raise your issue for
-    discussion on our mailing list:
+    brackets. For assistance with installation issues, or for any other issues
+    other than those listed below, please raise your topic for discussion on
+    our mailing list:
 
         https://groups.google.com/forum/#!forum/netbox-discuss
 
@@ -20,7 +21,9 @@
 <!--
     Please describe the environment in which you are running NetBox. (Be sure
     to verify that you are running the latest stable release of NetBox before
-    submitting a bug report.)
+    submitting a bug report.) If you are submitting a bug report and have made
+    any changes to the code base, please first validate that your bug can be
+    recreated while running an official release.
 -->
 ### Environment
 * Python version:  <!-- Example: 3.5.4 -->
@@ -28,8 +31,8 @@
 
 <!--
     BUG REPORTS must include:
-        * A list of the steps needed to reproduce the bug
-        * A description of the expected behavior
+        * A list of the steps needed for someone else to reproduce the bug
+        * A description of the expected and observed behavior
         * Any relevant error messages (screenshots may also help)
 
     FEATURE REQUESTS must include:
@@ -37,5 +40,11 @@
         * A use case for the new feature
         * A rough description of any necessary changes to the database schema
         * Any relevant third-party libraries which would be needed
+
+    Do not prepend any sort of tag to your issue's title. An administator will
+    review your issue and assign labels as appropriate.
+
+    Please note that, due to an excessive backlog of feature requests, we are
+    not currently accepting any proposals which extend NetBox's feature scope.
 -->
 ### Description