Skip to content

Commit 0dc35f0

Browse files
NO-JIRA added contributing.md (SonarSource#111)
1 parent ec127a9 commit 0dc35f0

File tree

1 file changed

+20
-9
lines changed

1 file changed

+20
-9
lines changed

CONTRIBUTING.md

+20-9
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,26 @@
1-
Issues / Questions
2-
------------------
3-
4-
If you want to raise an issue or ask a question ("How do I?", "I got this error, why?", ...), please first read the [documentation](https://docs.sonarqube.org) and then head to the [SonarSource forum](https://community.sonarsource.com/). There are chances that a question similar to yours has already been answered.
5-
6-
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. :-)
7-
81
Contributing
9-
------------
2+
============
103

114
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).
125

13-
Please be aware that we are not actively looking for feature contributions. We typically accept minor improvements and bug-fixes.
6+
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.
7+
8+
## Submitting a pull request
149

1510
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.
11+
12+
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).
13+
14+
## Next steps
15+
16+
One of the members of our team will carefully review your pull request. You might be asked at this point for clarifications or your pull request might be rejected if we decide that it doesn't fit our roadmap and vision for the product.
17+
If your contribution looks promising then either we will decide:
18+
19+
- it is good to go and merge your pull request to the master branch
20+
21+
or
22+
23+
- that we need to think over your change and modify it to adhere to our roadmap and internal standards. We will close your pull request at this point, but we might come back to your changes later in the future when we decide it is the right time to work on it.
24+
25+
Thank You!
26+
The SonarSource Team

0 commit comments

Comments
 (0)