docs: update wording describing issue lifecycle (NativeScript#5742)

radeva · manoldonev · commit 72fa5c9bc1a4 · 2018-04-30T10:50:29.000+03:00
- describe when an issue will be closed without waiting for response
- add this description in a comment in the issue template. This way it will be visible to the creator of the issue, but won't add noise when reading the issues in github.
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,12 +1,8 @@
-Dear friend, we, the rest of the NativeScript community really
-appreciate your feedback! While we are doing all we can to take care of every
-issue, sometimes we get overwhelmed. Because of that, we will consider issues
-that are not constructive or problems that cannot be reproduced "dead".
-Additionally, we will treat feature requests or bug reports with unanswered
-questions regarding the behavior/reproduction for more than 20 days "dead". All
-"dead" issues will get closed.
-
-## Please, provide the details below:
+<!--
+We appreciate your feedback! While we are doing all we can to take care of every issue, sometimes we get overwhelmed. That's why
+ - issues that are not constructive or describe problems that cannot be reproduced will be closed
+ - feature requests or bug reports with unanswered questions regarding the behavior/reproduction for more than 20 days will be closed 
+-->
 
 ### Did you verify this is a real problem by searching the [NativeScript Forum](http://forum.nativescript.org) and the [other open issues in this repo](https://github.com/NativeScript/nativescript/issues)?
 
@@ -31,3 +27,5 @@ The best approach would be to get your code running in the [NativeScript Playgro
 
 ### Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
 
+
+
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -19,6 +19,10 @@ Help us keep a healthy and open community. We expect all participants in this pr
 2. Search for similar issues in the issues list for this repo; it may already be an identified problem.
 3. If this is a bug or problem that is clear, simple, and is unlikely to require any discussion -- it is OK to open an issue on GitHub with a reproduction of the bug including workflows and screenshots. If possible, submit a Pull Request with a failing test, entire application or module. If you'd rather take matters into your own hands, fix the bug yourself (jump down to the [Submitting a PR](#pr) section).
 
+> While we are doing all we can to take care of every issue, sometimes we get overwhelmed. That's why
+> - issues that are not constructive or describe problems that cannot be reproduced will be closed
+> - feature requests or bug reports with unanswered questions regarding the behavior/reproduction for more than 20 days will be closed 
+
 ## <a name="features"></a> Requesting Features
 
 1. Use Github Issues to submit feature requests.
