Loïck Bonniot
--- a/CONTRIBUTING.md 0 → 100644
+++ b/CONTRIBUTING.md 0 → 100644
+5. Locally merge (or rebase) the upstream development branch into your topic branch:
+
+  ```bash
+  git pull [--rebase] upstream <dev-branch>
+  ```
+
+6. Push your topic branch up to your fork:
+
+  ```bash
+  git push origin <topic-branch-name>
+  ```
+
+7. Open a Pull Request with a clear title and description.
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project owner to
+license your work under the same license as that used by the project.
--- a/CONTRIBUTING.md 0 → 100644
+++ b/CONTRIBUTING.md 0 → 100644
+
+You can rebase. But, please, do it locally (when refactoring your own topic branch).
+You don't want to have contributors against you after a missed forced push.
+
+## Pull requests
+
+Good pull requests (patches, improvements, new features) are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any significant pull request (e.g.
+implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the
+project's developers might not want to merge into the project.
+
+Please adhere to the coding conventions used throughout a project (indentation,