Add CODEOWNERS and PULL_REQUEST_TEMPLATE

Specific code owners will be automatically added as reviewers, whenever new
PRs are opened. CODEOWNERS file can be different on each branch.

PULL_REQUEST_TEMPLATE.md will populate all new PR description field.
Beside PR description, it contains a list of checkboxes, ensuring all
team members follow the same guidelines and enforce best practices.
PR Template applies for PRs against all protected branches.

Both files were added in .github

Signed-off-by: Stefan Raus <[email protected]>

Author: SRaus

.github/CODEOWNERS

@@ -0,0 +1,17 @@
+# This document lists the code owners for all Linux repo sources, and it is
+# used automatically whenever Pull Requests are created, in next way:
+#  - People listed as CODEOWNERS are automatically added as reviewers to all
+#    PRs open to branches containing this file.
+#  - In addition to Code Owners, other reviewers can be added.
+#  - There can be different code owners for different branches.
+#  - PRs will require the approval of at least one code owner.
+#
+# For more details, you can refer [GitHub CodeOwners Documentation](ttps://github.blog/2017-07-06-introducing-code-owners/)
+#
+# The format of CODEOWNERS is: <pattern> + <mail address of one/more owners>
+#
+# In case of multiple matches, the last pattern matched will take precedence.
+
+##### Global code owners (for folders with no later match) #####
+
+*    [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+## PR Description
+
+- Please replace this comment with a summary of your changes, and add any context
+necessary to understand them. List any dependencies required for this change.
+- To check the checkboxes below, insert a 'x' between square brackets (without
+any space), or simply check them after publishing the PR.
+- If you changes include a breaking change, please specify dependent PRs in the
+description and try to push all related PRs simultaneously.
+
+## PR Type
+- [ ] Bug fix (a change that fixes an issue)
+- [ ] New feature (a change that adds new functionality)
+- [ ] Breaking change (a change that affects other repos or cause CIs to fail)
+
+## PR Checklist
+- [ ] I have conducted a self-review of my own code changes
+- [ ] I have tested the changes on the relevant hardware
+- [ ] I have updated the documentation outside this repo accordingly (if there is the case)