Add/update issue, PR templates, code of conduct, contributing guide

DCN-34 - adjusted expectations

Author: petrsvihlik

.github/ISSUE_TEMPLATE/feature_request.md

@@ -10,7 +10,7 @@ Why is this feature required? What problems does it solve?
 
 ### Proposed solution
 
-An ideal solution of the above problems.
+An ideal solution for the above problems.
 
 ### Additional context
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -9,9 +9,9 @@ If no issue exists, what is the fix or new feature? Were there any reasons to fi
 - [ ] Code follows coding conventions held in this repo
 - [ ] Automated tests have been added
 - [ ] Tests are passing
-- [ ] Docu has been updated (if applicable)
-- [ ] Temporary settings (e.g. project ID used during development and testing) have been reverted to defaults
+- [ ] Docs have been updated (if applicable)
+- [ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults
 
 ### How to test
 
-If manual testing is required, what are the steps?
+If manual testing is required, what are the steps?

CONTRIBUTING.md

@@ -1,76 +1,74 @@
-# Contributing guidelines
+# Ways to contribute 
+<img align="right" width="100" height="100" src="https://i.imgur.com/PYTV0jP.png">
 
-There are many different ways in which you can contribute. One of them is simply by using our software and providing us with your feedback or you can actively participate by coding some new features.
+There are many different ways in which you can contribute. One of the easiest wazs is simply to use our software and providing us with your feedback in discussions. You can also participating on coding new features and fixing bugs by submitting pull requests with code changes.
 
-This guide describes general guidelines that most of the repositories refer to. We don't want to make things complicated so we try to follow the same rules in every repository. But sometimes there are some rules specific for that particular repository. Always check the contributing guideline and readme in that repository as well.
+We don't want to make things complicated so we try to follow these same rules in all our repositories. 
 
+# Where to get support
+Please note that level of provided support is always determined by the [LICENSE](LICENSE.md) of a given open-source project.
 
-## I have an idea for a new feature
+## I found a bug in a Kentico's open-source project
+<img align="right" width="100" height="100" src="https://i.imgur.com/TYIQdpv.png">
 
-Everybody loves new features! You can submit a new feature request or you can code it on your own and send us a pull request. In either case, don't forget to mention what's the use case and what's the expected output.
+Sorry to hear that. Just log a new [GitHub issue](../../../../issues) and someone will take a look at it. Remember, the more information you provide, the easier it will be to fix the issue. If you feel like it, you can also fix the bug on your own and submit a new pull request.
 
-It's always a good idea to discuss the feature before you start the implementation. You can check with us whether the feature fits the vision of a given project. We may also give you some useful hints before you start coding. To start chatting, either create a new GitHub issue or contact us via the [repository's default communication channel](https://github.com/Kentico/Home#questions--answers).
+## I need help with using the projects and/or coding
+<img align="right" width="100" height="100" src="https://cdn.sstatic.net/Sites/stackoverflow/company/img/logos/so/so-icon.svg">
 
+To get help with coding and structuring your projects, use [StackOverflow](https://stackoverflow.com/) to ask questions with one of the following tags:
+- [`kentico-cloud`](https://stackoverflow.com/questions/tagged/kentico-cloud)
+- [`kentico`](https://stackoverflow.com/questions/tagged/kentico)
 
-## I found a bug
+Our team members and the community monitor these channels on a regular basis.
 
-Sorry to hear that. Just create new GitHub issue and someone will take a look at that. Please, don't forget to provide us with all the important information like
+## I want to report a security bug
+<img align="right" width="100" height="100" src="https://i.imgur.com/z82nnJB.png">
 
-- Steps to reproduce the issue
-- Environment and software version used
-- Screenshot
-- Error message
-- What is the expected behavior
+Security issues and bugs should be reported privately, via email, to the Kentico Developer Community Team developerscommunity@kentico.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
 
-The more information you provide, the easier would it be to fix the issue. You can also fix the bug on your own and submit a new pull request.
+
+## I have an idea for a new feature (or feedback on existing functionality)
+<img align="right" width="100" height="100" src="https://i.imgur.com/rUFkyPy.png">
+
+Everybody loves new features! You can submit a new [feature request](../../../../issues) or you can code it on your own and [send us a pull request](#submitting-pull-requests). In either case, don't forget to mention what's the use case and what's the expected output.
 
 
 ## Submitting pull requests
+<img align="right" width="100" height="100" src="https://i.imgur.com/aSeiliy.png">
 
-If not stated otherwise, we use [feature branch workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow). To start with coding, fork the repository you want to contribute to, create a new branch and start coding.
+Unless you're fixing a typo, it's usually a good idea to discuss the feature before you submit a pull request with code changes, so let's start with submitting a new [GitHub issue](../../../../issues) and discussing the whether it fits the vision of a given project.
+You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be rigorously reviewed and tested by the Kentico Maintainers teams, and only those that meet an high bar for both quality and design/roadmap appropriateness will be merged into the source.
 
 
 ### Example - process of contribution
+If not stated otherwise, we use [feature branch workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow). 
 
-1. ```Tom``` forks this repository
-2. Creates a new branch for his ```cool``` feature
-3. Hacks his code
-4. Writes some tests
-5. Once he's happy with the changes, he submits a pull request from his ```cool``` branch to ```master``` branch
-6. We discuss the pull request with ```Tom``` and maybe suggest some adjustments
-7. Once the code is ready, someone from maintainers will merge it into the ```master``` branch
-
+To start with coding, fork the repository you want to contribute to, create a new branch, and start coding. Once the functionality is [done](#Definition-of-Done), you can submit a [pull request](https://help.github.com/articles/about-pull-requests/). 
 
 ### Definition of Done
+<img align="right" width="100" height="100" src="https://i.imgur.com/g82Ohdv.png">
 
-- Code requirements:
- - Code is buildable
- - All tests are green
- - Code design follows the .NET [Framework Design Guidelines](https://msdn.microsoft.com/en-us/library/ms229042.aspx)
-    - If you're not sure about some rules, follow the style of the existing code.
-    - Use "Format the whole document" button in Visual Studio to fix indentation ![format](https://cloud.githubusercontent.com/assets/9810625/12391368/a14d7726-bde7-11e5-9a0f-3310c833f5ca.png)
-- Documentation is updated
-  
+- New/fixed code is covered with tests
+- CI can build the code
+- All tests are pass
+- New version number follows [semantic versioning](https://semver.org/)
+- Coding style (spaces, indentation) is in line with the rest of the code in a given repository
+- Documentation is updated (e.g. code examples in README, Wiki pages, etc.)
+- All `public` members are documented (using XML doc, phpdoc, etc.)
+- Code doesn't contain any secrets (private keys, etc.)
+- Commit messages are clear. Please read these articles: [Writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages), [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), [On commit messages](https://who-t.blogspot.com/2009/12/on-commit-messages.html)
 
 
-### Learn how to write good commit messages
+### Feedback
+<img align="right" width="100" height="100" src="https://i.imgur.com/ZQfNzJJ.png">
 
-We hate sloppy commit messages. No more ```Performance tuning``` or ```Changed a few files```. Please read the following articles to understand what a good commit message is.
+Your pull request will now go through extensive checks by the subject matter experts on our team. Please be patient. Update your pull request according to feedback until it is approved by one of the Kentico maintainers. After that, one of our team members may adjust the branch you merge into based on the expected release schedule.
 
-- [Writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages)
-- [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
-- [On commit messages](https://who-t.blogspot.com/2009/12/on-commit-messages.html)
 
 ## Code of Conduct
+<img align="right" width="100" height="100" src="https://i.imgur.com/cObdKQy.png">
 
-The Kentico team is committed to fostering a welcoming community.
-
-**Our Code of Conduct can be found here**:
-
-https://github.com/Kentico/Home/blob/master/CODE_OF_CONDUCT.md
-
-For a history of updates, see the page history here:
-
-https://github.com/Kentico/Home/commits/master/CODE_OF_CONDUCT.md
+The Kentico team is committed to fostering a welcoming community, therefore this project has adopted the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). If you have any additional questions or comments, you can contact us directly at developerscommunity@kentico.com.
 
 ![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/Kentico/Home/master/CONTRIBUTING.md?pixel)