Update community documentation

.github/CODE_OF_CONDUCT.md

@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at `owzie123@gmail.com`. All
+reported by contacting the project team at `development@pxgamer.xyz`. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.

.github/CONTRIBUTING.md

@@ -8,7 +8,7 @@ We accept contributions via Pull Requests on [Github](https://github.com/pxgamer
 
 - **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)** - Check the code style with ``$ composer check-style`` and fix it with ``$ composer fix-style``.
 
-- **Add tests!** - Your patch won't be accepted if it doesn't have tests.
+- **Add tests!** - If possible, try to add tests to support your patch.
 
 - **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.
 
@@ -17,13 +17,3 @@ We accept contributions via Pull Requests on [Github](https://github.com/pxgamer
 - **Create feature branches** - Don't ask us to pull from your master branch.
 
 - **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.
-
-- **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](https://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.
-
-## Running Tests
-
-```bash
-$ composer test
-```
-
-**Happy coding**!

.github/ISSUE_TEMPLATE.md

@@ -1,17 +1,11 @@
 <!-- Provide a general summary of the issue in the Title above -->
 
-## Detailed description
+## Description
 
 Provide a detailed description of the change or addition you are proposing.
 
 Make it clear if the issue is a bug, an enhancement or just a question.
 
-## Context
-
-Why is this change important to you? How would you use it?
-
-How can it benefit other users?
-
 ## Possible implementation
 
 Not obligatory, but suggest an idea for implementing addition or change.
@@ -20,8 +14,6 @@ Not obligatory, but suggest an idea for implementing addition or change.
 
 Include as many relevant details about the environment you experienced the bug in and how to reproduce it.
 
-* Version used (e.g. PHP 5.6, HHVM 3):
-* Operating system and version (e.g. Ubuntu 16.04, Windows 7):
-* Link to your project:
-* ...
+* Version used (e.g. PHP 7.3):
+* Operating system and version (e.g. Ubuntu 18.10, Windows 10):
 * ...

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,42 +2,22 @@
 
 ## Description
 
-Describe your changes in detail.
-
-## Motivation and context
-
-Why is this change required? What problem does it solve?
-
-If it fixes an open issue, please link to the issue here (if you write `fixes #num`
-or `closes #num`, the issue will be automatically closed when the pull is accepted.)
-
-## How has this been tested?
-
-Please describe in detail how you tested your changes.
-
-Include details of your testing environment, and the tests you ran to
-see how your change affects other areas of the code, etc.
-
-## Screenshots (if appropriate)
+...
 
 ## Types of changes
 
-What types of changes does your code introduce? Put an `x` in all the boxes that apply:
+Put an `x` in all the boxes that apply:
+
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to change)
 
-## Checklist:
-
-Go over all the following points, and put an `x` in all the boxes that apply.
+## Checklist
 
-Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our [continuous integration](https://www.phptherightway.com/#continuous-integration) server to make sure your [tests and code style pass](https://help.github.com/articles/about-required-status-checks).
+Put an `x` in all the boxes that apply:
 
 - [ ] I have read the **[CONTRIBUTING](CONTRIBUTING.md)** document.
 - [ ] My pull request addresses exactly one patch/feature.
 - [ ] I have created a branch for this patch/feature.
-- [ ] Each individual commit in the pull request is meaningful.
-- [ ] I have added tests to cover my changes.
-- [ ] If my change requires a change to the documentation, I have updated it accordingly.
 
 If you're unsure about any of these, don't hesitate to ask. We're here to help!

README.md

@@ -52,7 +52,7 @@ $ composer test
 
 ## Contributing
 
-Please see [CONTRIBUTING](CONTRIBUTING.md) and [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) for details.
+Please see [CONTRIBUTING](.github/CONTRIBUTING.md) and [CODE_OF_CONDUCT](.github/CODE_OF_CONDUCT.md) for details.
 
 ## Security