chore(contributing): update contributing doc and issue template

Closes #1494

Author: deeg

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,15 @@
+The issues forum is __NOT__ for support requests. It is for bugs and feature requests only.
+Please read https://github.com/angular-ui/ui-select/blob/master/CONTRIBUTING.md and search
+existing issues (both open and closed) prior to opening any new issue and ensure you follow the instructions therein.
+
+### Bug description:
+
+### Link to minimally-working plunker that reproduces the issue:
+
+### Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS
+
+Angular:
+
+UI-Select:
+
+Bootstrap/Select2/Selectize CSS (if applicable):

CONTRIBUTING.md

@@ -1,8 +1,39 @@
 We are excited to have you working on the project and cordially request that you follow the Guidelines:
 
+ - [Got a question or problem?](#question)
+ - [You think you've found a bug?](#bug)
  - [Code Style Guidelines](#rules)
  - [Commit Message Guidelines](#commit)
 
+## <a name="question"></a> Got a question or problem?
+ 
+ Firstly, please go over our FAQ: https://github.com/angular-ui/ui-select/wiki/FAQs
+ 
+ Please, do not open issues for the general support questions as we want to keep GitHub issues for bug reports and feature requests. You've got much better chances of getting your question answered on [StackOverflow](http://stackoverflow.com/questions/tagged/angular-ui-select) where maintainers are looking at questions tagged with `angular-ui-select`.
+ 
+ StackOverflow is a much better place to ask questions since:
+ * there are hundreds of people willing to help on StackOverflow
+ * questions and answers stay available for public viewing so your question / answer might help someone else
+ * SO voting system assures that the best answers are prominently visible.
+ 
+ To save your and our time we will be systematically closing all the issues that are requests for general support and redirecting people to StackOverflow.
+ 
+## <a name="bug"></a> You think you've found a bug?
+ 
+ Oh, we are ashamed and want to fix it asap! But before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will systematically ask you to provide a _minimal_ reproduce scenario using http://plnkr.co/. Having a live reproduce scenario gives us wealth of important information without going back & forth to you with additional questions like:
+ * version of AngularJS used
+ * version of this library that you are using
+ * 3rd-party libraries used, if any
+ * and most importantly - a use-case that fails
+ 
+ A minimal reproduce scenario using http://plnkr.co/ allows us to quickly confirm a bug (or point out coding problem) as well as confirm that we are fixing the right problem.
+ 
+ We will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience users often find coding problems themselves while preparing a minimal plunk. We understand that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate the problem before we can fix it.
+ 
+ The best part is that you don't need to create plunks from scratch - you can use one from our [demo page](http://plnkr.co/edit/a3KlK8dKH3wwiiksDSn2?p=preview).
+ 
+ Unfortunately we are not able to investigate / fix bugs without a minimal reproduce scenario using http://plnkr.co/, so if we don't hear back from you we are going to close an issue that don't have enough info to be reproduced.
+ 
 ## <a name="rules"></a> Coding Rules
 To ensure consistency throughout the source code, keep these rules in mind as you are working: