Few doc pages

.gitattributes

@@ -1,11 +1,16 @@
 * text=auto
 
+/.github export-ignore
 /doc export-ignore
 /tests export-ignore
 /.gitattributes export-ignore
-/.github export-ignore
 /.gitignore export-ignore
+/CODE_OF_CONDUCT.md export-ignore
 /ecs.php export-ignore
-/rector.php export-ignore
+/infection.json.dist export-ignore
+/Makefile export-ignore
+/phpstan.neon export-ignore
 /phpunit.xml.dist export-ignore
 /README.md export-ignore
+/rector.php export-ignore
+/SECURITY.md export-ignore

.github/CONTRIBUTING.md

@@ -1,16 +1,27 @@
-# Aux contributeurs
+# Contributing
 
-Tout d’abord, **merci** pour votre contribution.
+First of all, **thank you** for contributing.
 
-Les bogues ou les demandes de fonctionnalités peuvent être publiés en ligne dans la section des problèmes GitHub du projet.
+Bugs or feature requests can be posted online on the GitHub issues section of the project.
 
-Quelques règles pour faciliter les revues de code et les fusions :
+Few rules to ease code reviews and merges:
 
-- Vous DEVEZ suivre le [PSR-1](http://www.php-fig.org/psr/psr-1/), [PSR-2](http://www.php-fig.org/psr /psr-2/) et [PSR-4](http://www.php-fig.org/psr/psr-4/).
-- Vous DEVEZ exécuter la suite de tests.
-- Vous DEVEZ écrire (ou mettre à jour) des tests lorsque des bogues sont corrigés ou que des fonctionnalités sont ajoutées.
-- Vous DEVRIEZ rédiger de la documentation.
+- You MUST follow the [PSR-12](http://www.php-fig.org/psr/psr-12/) coding standards.
+- You MUST run the test suite.
+- You MUST write (or update) unit tests when bugs are fixed or features are added.
+- You SHOULD write documentation.
 
-[Git-Flow](http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/) est vivement recommandé.
+To contribute use [Pull Requests](https://help.github.com/articles/using-pull-requests), please, write commit messages that make sense, and rebase your branch before submitting your PR.
 
-Merci de mettre à jour votre dépôt avant de soumettre votre Pull Request.
+May be asked to squash your commits too. This is used to "clean" your Pull Request before merging it, avoiding commits such as fix tests, fix 2, fix 3, etc.
+
+Run test suite
+------------
+
+* install composer: `curl -s http://getcomposer.org/installer | php`
+* install dependencies: `php composer.phar install`
+* run tests: `vendor/bin/phpunit`
+* check and fix coding standards:
+  * `vendor/bin/phpstan analyse`
+  * `vendor/bin/rector process`
+  * `vendor/bin/ecs check --fix`

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: Spomky
+patreon: FlorentMorselli

.github/ISSUE_TEMPLATE/1_Bug_report.md

@@ -1,21 +1,21 @@
 ---
 name: 🐛 Bug Report
-about: ⚠️ For all bug reports except security issues (see below)
-labels: bug
+about: ⚠️ See below for security reports
+labels: Bug
 
 ---
 
-**Version(s)** : x.y.z
+**Version(s) affected**: x.y.z
 
 **Description**
 <!-- A clear and concise description of the problem. -->
 
-**How to reproduce?**
-<!-- Code or configuration needed to reproduce the problem. If it is a complex bug,
-      create a "bug reproducer" -->
+**How to reproduce**
+<!-- Code and/or config needed to reproduce the problem. If it's a complex bug,
+     create a "bug reproducer" as explained in: -->
 
-**Possible solution**
-<!--- Optional: only if you have any suggestions on a fix/bug reason -->
+**Possible Solution**
+<!--- Optional: only if you have suggestions on a fix/reason for the bug -->
 
 **Additional context**
-<!-- Optional: any other context regarding the issue: log messages, screenshots, etc. -->
+<!-- Optional: any other context about the problem: log messages, screenshots, etc. -->

.github/ISSUE_TEMPLATE/2_Feature_request.md

@@ -1,13 +1,12 @@
 ---
-name: 🎉 Feature request
+name: 🚀 Feature Request
 about: Ideas for new features and improvements
-labels: feature
 
 ---
 
 **Description**
 <!-- A clear and concise description of the new feature. -->
 
 **Example**
-<!-- A simple example of the new feature in action (include PHP code, YAML configuration, etc.)
-      If the new feature changes an existing feature, include a before/after comparison. -->
+<!-- A simple example of the new feature in action (include PHP code, YAML config, etc.)
+     If the new feature changes an existing feature, include a simple before/after comparison. -->

.github/ISSUE_TEMPLATE/3_Support_question.md

@@ -0,0 +1,11 @@
+---
+name: ⛔ Support Question
+about: We usually do not provide support. Please ask your question on https://stackoverflow.com/
+
+---
+
+We use GitHub issues only to discuss bugs and new features.
+For this kind of questions about using the library or the bundle, please use
+https://stackoverflow.com/ using the tags `[aes]` and `[php]`
+
+Thanks!

.github/ISSUE_TEMPLATE/4_Documentation_issue.md

@@ -0,0 +1,5 @@
+---
+name: 📖 Documentation Issue
+about: To report typo or obsolete section in the documentation
+
+---

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,15 +1,19 @@
-| Q                       | A
-| ----------------------- | ---
-| Correction de bogues?   | oui/non
-| Nouvelle fonctionnalité | oui/non
-| Dépréciations?          | oui/non
-| Tickets                | Corrige #...
+| Q             | A
+| ------------- | ---
+| Branch?       | <!-- see below -->
+| Bug fix?      | yes/no
+| New feature?  | yes/no <!-- please update src/**/CHANGELOG.md files -->
+| Deprecations? | yes/no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
+| Tickets       | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
+| License       | MIT
 <!--
-Remplacez cet avis par un court README pour votre fonctionnalité/correction de bogues. Cela aidera les autres à
-comprendre votre PR. Cela peut être utilisé comme point de départ pour la documentation.
+Replace this notice by a short README for your feature/bugfix. This will help people
+understand your PR and can be used as a start for the documentation.
 
-En outre:
-  - Ajoutez toujours des tests et assurez-vous qu’ils réussissent.
-  - Ne jamais rompre la rétrocompatibilité, sauf si c’est l’objet de votre PR.
-  - Votre dépôt doit être à jour.
--->
+Additionally:
+ - Always add tests and ensure they pass.
+ - Never break backward compatibility (unless you are working on the next major release branch).
+ - Bug fixes must be submitted against the lowest maintained branch where they apply
+   (lowest branches are regularly merged to upper ones so they get the fixes too.)
+ - Features and deprecations must be submitted against the last major branch (e.g. 1.x).
+-->

.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+- package-ecosystem: composer
+  directory: "/"
+  schedule:
+    interval: daily
+    time: "11:00"
+  open-pull-requests-limit: 10

SECURITY.md

@@ -2,16 +2,15 @@
 
 ## Supported Versions
 
-
-| Version | Supported          |
-| ------- | ------------------ |
-| 11.0.x  | :white_check_mark: |
-| 10.0.x  | :white_check_mark: |
-| < 10.0  | :x:                |
+| Version | Supported                              |
+| ------- |----------------------------------------|
+| 11.0.x  | :white_check_mark:                     |
+| 10.0.x  | :white_check_mark: (security fix only) |
+| < 10.0  | :x:                                    |
 
 ## Reporting a Vulnerability
 
-Please send an email to `[email protected]`.
+Please email `[email protected]`.
 If deemed necessary, you can encrypt your message using one of the following GPG key
 
 ```