docs: Move everything commit related to a dedicated guideline document

Signed-off-by: Henrique Pereira <henrique.pereira@signativa.com.br>

Author: Hlcpereira

commits_guidelines.md

@@ -0,0 +1,21 @@
+# Commit Guidelines:
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
+
+Exceptions **SHOULD** be made by contacting the administration team.
+
+- The commit's message **MUST** have its content clear to anyone that wants to know what the commit is about. There is absolutely no need for the commit message to contain Linux Foundation's like documentation, however something that an average newbie developer would understand is required. Extra documentation/explanation **MUST** be there if the commit's content is huge, and also will always be welcome.
+
+- The commit's message **MUST** have an indicator of where the commit introduces changes, therefor following the standard: "<path/repository name reference>: <Commit title that **MUST** be a basic explanation for its content>".
+
+- The commit **MUST** be necessary for the device to build, boot, or even to have a/the device's function(s) working properly (e.g. Fingerprint On Display).
+
+- The commit **MUST** have proper authorship.
+
+- If a commit is for the ROM side, the same **MUST** be pushed to [Gerrit](https://gerrit.pixelexperience.org).
+
+- The commit's content **MUST** be as minimal and polished as possible.
+
+- The commit **MUST** be in accordance with the items, if applicable, stated at our [Maintainers Code of Conduct](https://github.com/PixelExperience/docs/blob/master/maintainers_code_of_conduct.md).
+
+- For revert commits, the same **SHOULD** contain reason for revert point - if possible at all. As stated previously, any extra bit of documentation in the commit's message is welcome.

device_requirements.md

@@ -22,14 +22,6 @@ Exceptions **SHOULD** be made by contacting the administration team.
 
 - The device **MUST NOT** have the need for a lot of patches, and if so, it must be in accordance with the following listing below.
 
-- If there are commits that are needed in repos other than the device-specific ones, they **MUST**:
+- If there are commits that are needed in repos other than the device-specific ones, they **MUST** be in accordance with our [Commit's Guidelines](https://github.com/PixelExperience/docs/blob/master/commits_guidelines.md).
 
-  - Be necessary for the device to build, boot, or even to have a/the device's function(s) working properly (e.g. Fingerprint On Display).
-
-  - Have proper authorship.
-
-  - Be pushed to [Gerrit](https://gerrit.pixelexperience.org).
-
-  - Be as minimal and polished as possible.
-
-  - Be in accordance with the items, if applicable, stated at our [Maintainers Code of Conduct](https://github.com/PixelExperience/docs/blob/master/maintainers_code_of_conduct.md).
+- The device **MUST** have on it's sources commit complying with our [Commit's Guidelines](https://github.com/PixelExperience/docs/blob/master/commits_guidelines.md).