Merge pull request #5557 from ascillato/patch-1

Update CONTRIBUTING.md

.github/PULL_REQUEST_TEMPLATE.md

@@ -3,8 +3,9 @@
 **Related issue (if applicable):** fixes #<Sonoff-Tasmota issue number goes here>
 
 ## Checklist:
-  - [ ] The pull request is done against the dev branch
+  - [ ] The pull request is done against the latest dev branch
-  - [ ] Only relevant files were touched (Also beware if your editor has auto-formatting feature enabled)
+  - [ ] Only relevant files were touched (Also remember to update _changelog.ino_ file)
   - [ ] Only one feature/fix was added per PR.
   - [ ] The code change is tested and works.
   - [ ] The code change pass travis tests. **Your PR cannot be merged unless tests pass**
+  - [ ] I accept the [CLA](https://github.com/arendst/Sonoff-Tasmota/blob/development/CONTRIBUTING.md#contributor-license-agreement-cla).

CONTRIBUTING.md

@@ -56,7 +56,57 @@ The process is straight-forward.
 7. All pull requests should consider updates to the documentation.
 8. Pull requests that address an outstanding issue, particularly an issue deemed to be severe, should be given priority.
 9. If a PR is accepted, then it should undergo review and updated based on the feedback provided, then merged.
-10. Pull requests that don't meet the above will be denied and closed.
+10. By submitting a PR, it is needed to use the provided PR template and check all boxes, performing the required tasks and accepting the CLA.
+11. Pull requests that don't meet the above will be denied and closed.
+
+--------------------------------------
+
+## Contributor License Agreement (CLA)
+
+```
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the GPL-3.0 license; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the GPL-3.0 license; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it) is maintained indefinitely
+    and may be redistributed consistent with this project or the open
+    source license(s) involved.
+```
+
+This Contributor License Agreement (CLA) was adopted on April 1st, 2019.
+
+The text of this license is available under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/).  It is based on the Linux [Developer Certificate Of Origin](http://elinux.org/Developer_Certificate_Of_Origin), but is modified to explicitly use the GPL-3.0 license and not mention sign-off (due to GitHub.com keeps an historial, with your user name, of PRs' commits and all editions on PR's comments).
+
+To accept the CLA it is required to put a x between [ ] on `[ ] I accept the CLA` in the PR template when submitting it. The [ ] is an opt-in box, so you have to manually accept it.
+
+**Why a CLA ?**
+
+_"A Contributor Licence Agreement (CLA) is strongly recommended when accepting third party contributions to an open development project, such as an open source software project. In order to redistribute contributions, it is necessary to ensure that the project has the necessary rights to do so. A Contributor Licence Agreement is a lightweight agreement, signed by the copyright holder, that grants the necessary rights for the contribution to be redistributed as part of the project."_ [OSS Watch](http://oss-watch.ac.uk/resources/cla)
+
+A CLA is a legal document in which you state _you are entitled to contribute the code/documentation/translation to the project_ you’re contributing to and that _you are willing to have it used in distributions and derivative works_. This means that should there be any kind of legal issue in the future as to the origins and ownership of any particular piece of code, then that project has the necessary forms on file from the contributor(s) saying they were permitted to make this contribution.
+
+CLA is a safety because it also ensures that once you have provided a contribution, you cannot try to withdraw permission for its use at a later date. People can therefore use that software, confident that they will not be asked to stop using pieces of the code at a later date.
+
+A __license__ grants "outbound" rights to the user of project. 
+
+A __CLA__ enables a contributor to grant "inbound" rights to a project.
+
+
+
+
 
 <Other>
 <A table should be maintained for relating maintainers and components. When triaging, this is essential to figure out if someone in particular should be consulted about specific changes.>