Add contributing guide

Author: henryju

README.md

@@ -1,13 +1,33 @@
-SonarQube Scanner API [![Build Status](https://travis-ci.org/SonarSource/sonar-scanner-api.svg?branch=master)](https://travis-ci.org/SonarSource/sonar-scanner-api)
-=========================
+SonarQube Scanner API
+=====================
 
 Common library used by many Scanners (SQ Scanner, SQ Scanner for Maven, SQ Scanner for Gradle, SQ Scanner for Ant, ...). Used to programmatically run SQ analysis.
 
-Issue Tracker:
-https://jira.sonarsource.com/browse/SCANNERAPI
+[![Build Status](https://travis-ci.org/SonarSource/sonar-scanner-api.svg?branch=master)](https://travis-ci.org/SonarSource/sonar-scanner-api)
+
+Have Question or Feedback?
+--------------------------
+
+For support questions ("How do I?", "I got this error, why?", ...), please head to the [SonarSource forum](https://community.sonarsource.com/c/help). There are chances that a question similar to yours has already been answered. 
+
+Be aware that this forum is a community, so the standard pleasantries ("Hi", "Thanks", ...) are expected. And if you don't get an answer to your thread, you should sit on your hands for at least three days before bumping it. Operators are not standing by. :-)
+
+
+Contributing
+------------
+
+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).
+
+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.
+
+With that in mind, if you would like to submit a code contribution, please create a pull request for this repository. Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make.
+
+Make sure that you follow our [code style](https://github.com/SonarSource/sonar-developer-toolset#code-style) and all tests are passing (Travis build is executed for each pull request).
+
 
-### License
+License
+-------
 
-Copyright 2011-2017 SonarSource.
+Copyright 2011-2019 SonarSource.
 
 Licensed under the [GNU Lesser General Public License, Version 3.0](http://www.gnu.org/licenses/lgpl.txt)

docs/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+Please review our [contribution guidelines](https://github.com/SonarSource/sonar-scanner-api/blob/master/contributing.md).
+
+And please ensure your pull request adheres to the following guidelines: 
+
+- [ ] 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](https://jira.sonarsource.com/browse/SCANNERAPI) ticket available, please make your commits and pull request start with the ticket ID (SCANNERAPI-XXXX)

docs/contributing.md

@@ -0,0 +1,12 @@
+Contributing
+============
+
+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).
+
+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.
+
+With that in mind, if you would like to submit a code contribution, please create a pull request for this repository. Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make.
+
+Make sure that you follow our [code style](https://github.com/SonarSource/sonar-developer-toolset#code-style) and all tests are passing (Travis build is executed for each pull request).
+
+Thank You! The SonarSource Team