Make it more explicit that we do not look for external contributions

docs/PULL_REQUEST_TEMPLATE.md

@@ -1,8 +1,13 @@
-Please review our [contribution guidelines](https://github.com/SonarSource/sonarqube/blob/master/docs/contributing.md).
+Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes. If you would like to see a new feature, please create a new thread in the forum ["Suggest new features"](https://community.sonarsource.com/c/suggestions/features).
 
-And please ensure your pull request adheres to the following guidelines: 
+With that in mind, if you would like to submit a code contribution, make sure that you adhere to the following guidelines and all tests are passing (Travis build is executed for each pull request):
 
 - [ ] Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make
 - [ ] Use the following formatting style: [SonarSource/sonar-developer-toolset](https://github.com/SonarSource/sonar-developer-toolset#code-style)
 - [ ] Provide a unit test for any code you changed
 - [ ] If there is a [JIRA](http://jira.sonarsource.com/browse/SONAR) ticket available, please make your commits and pull request start with the ticket ID (SONAR-XXXX)
+
+We will try to give you feedback on your contribution as quickly as possible.
+
+Thank You!
+The SonarSource Team

docs/PULL_REQUEST_TEMPLATE/FRONT_END_PULL_REQUEST_TEMPLATE.md

@@ -1,8 +0,0 @@
-**Checklist**
-
-* [ ] Write/update ITs
-* [ ] Functional validation
-* [ ] Public documentation update
-* [ ] Private documentation update
-* [ ] Run accessibility audit using [Chrome's Lighthouse](https://developers.google.com/web/tools/lighthouse/)
-* [ ] Ping a member of the other team (SQ/SC)