Added Github bits...

Author: Geolim4

.github/CONTRIBUTING.md

@@ -0,0 +1,19 @@
+Contributing to the PhpFastCache Bundle
+========================================
+
+Please note that this project is released with a
+[Contributor Code of Conduct](http://contributor-covenant.org/version/1/4/).
+By participating in this project you agree to abide by its terms.
+
+Reporting Issues
+----------------
+
+When reporting issues, please try to be as descriptive as possible, and include
+as much relevant information as you can. A step by step guide on how to
+reproduce the issue will greatly increase the chances of your issue being
+resolved in a timely manner.
+
+Contributing policy
+-------------------
+
+Our contributing policy is described in our [Coding Guideline](https://github.com/PHPSocialNetwork/phpfastcache-bundle/blob/V3/CODING_GUIDELINE.md)

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,12 @@
+### Configuration:
+
+- **PhpFastCache API version:** "...replace me (Can be retrieved using method `\Phpfastcache\Api::GetVersion()`)..."
+- **PhpFastCache bundle version:** "...replace me (Can be retrieved using constant `\Phpfastcache\Bundle\PhpfastcacheBundle::VERSION`)..."
+- **PhpFastCache version:** "...replace me (Can be retrieved using method `\Phpfastcache\Api::getPhpFastCacheVersion()`)..."
+- **PHP version:** "...replace me (Can be retrieved using command line `php -v | sed -n 1p`)..."
+- **Operating system:** " ...replace me (You REALLY should know it)... "
+
+#### Issue description:
+
+> ... Your description goes here ... 
+... You can also read the [wiki](https://github.com/PHPSocialNetwork/phpfastcache-bundle/wiki) ...

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be 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 [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CODING_GUIDELINE.md

@@ -0,0 +1,55 @@
+CODING GUIDELINE
+-------------------
+
+Fork the project, create a feature branch, and send us a pull request.
+Preferably on a distinct branch.
+
+To ensure a consistent code base, you should make sure the code follows
+the [PSR-2 Coding Standards](http://www.php-fig.org/psr/psr-2/). You can also
+run [php-cs-fixer](https://github.com/FriendsOfPHP/PHP-CS-Fixer) with the
+configuration file that can be found in the project root directory.
+
+If you would like to help, take a look at the [list of open issues](https://github.com/PHPSocialNetwork/phpfastcache/issues).
+
+PHPFASTCACHE's specialties 
+-------------------
+As of the V7 your contributions MUST comply the following standards:
+
+### PHP CORE FUNCTIONS
+- To improve opcode efficiency, you MUST prefix core function by a '\\'
+  - E.g: `$var = \str_replace('value', '', $var);`
+
+### PHP CORE CLASSES
+- Do not imports non-namespaced classes, use an absolute path instead:  
+  - E.g: `$date = new \DateTime();`
+
+### CODE STYLE
+- Unneeded/inconsistent `else` statements have to be shortened.
+  - E.g: 
+ ```php 
+ <?php
+function setAcme($acme)
+{
+    if ($acme instanceof Acme) {
+        $this->acme = $acme;
+        return $this;
+    } else {
+        throw new phpFastCacheInvalidArgumentException('Invalid acme instance');
+    }
+}
+ ```
+  - This example can be safely replaced by this one:
+```php 
+ <?php
+function setAcme($acme)
+{
+    if ($acme instanceof Acme) {
+        $this->acme = $acme;
+        return $this;
+    } 
+
+    throw new phpFastCacheInvalidArgumentException('Invalid acme instance');
+}
+ ```
+[Read this thread on StackExchange for more information](https://softwareengineering.stackexchange.com/questions/122485/elegant-ways-to-handle-ifif-else-else)
+This list is non-exhaustive and will may subject to evolve at any time.