Code of conduct, issue templates, pull request template and codeowners (#64)

<!--
Thanks for your contribution! Please read this comment in its entirety.
It's quite important.
When a contributor will merge the pull request, the title and the
description will be used to build the merge commit!

### Pull Request TITLE

It should be in the following format:

[ 12345: Summary of the changes made ] Where 12345 is the corresponding
Github Issue

OR

[ Summary of the changes made ] If it's solving something trivial, like
fixing a typo.

-->

### Linked issues
<!--
Link the Issue(s) this Pull Request is related to.

Each PR should link at least one issue, in the form:

Use one line for each Issue. This allows auto-closing the related issue
when the fix is merged.

Fixes #123
Fixes #456
-->
No linked issue

### Summarize your change.

Adds code of conduct, issue templates, pull request templates and
CODEOWNER files.

Note: I filled this pull request by manually copying the pull request
template :) If you try to edit the pull request description, you see all
the comments.

### Describe the reason for the change.

I am trying to implement the missing bits of the [Community
Standards](https://github.com/AcademySoftwareFoundation/OpenRV/community)
checklist.

<img width="1650" alt="Community Standards Screenshot"
src="https://user-images.githubusercontent.com/6785406/219745446-c81e4008-3d31-487b-bf94-313c79d93642.png">

### Describe what you have tested and on what operating system.

N/A

### Add a list of changes, and note any that might need special
attention during the review.

Please watchout for typos. I am known for injecting them everywhere I
go.

### If possible, provide some screenshots.

<img width="1650" alt="Pull Request Template Edit"
src="https://user-images.githubusercontent.com/6785406/219750950-1c9b8398-7139-4297-a0e9-b49e0bc3b6b2.png">

<img width="1650" alt="Pull Request Template Preview"
src="https://user-images.githubusercontent.com/6785406/219750999-50a51330-a7bf-4f4e-a263-c6c15dfd7a01.png">

<img width="1650" alt="Create an Issue"
src="https://user-images.githubusercontent.com/6785406/219751134-08439da4-4332-484d-a33e-14d3ba90a194.png">

<img width="1650" alt="Create a Bug Report"
src="https://user-images.githubusercontent.com/6785406/219751165-6323afcd-ce5f-4696-89d0-b14a231aefcb.png">


<!-- Use the Preview tab to ensure everything looks like you expect. -->

---------

Signed-off-by: Kerby Geffrard <kerby.geffrard@autodesk.com>
Co-authored-by: Martin Chesnay <104032692+mchesnay@users.noreply.github.com>

Author: Kerby Geffrard

.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# See https://help.github.com/articles/about-codeowners/
+# for more info about CODEOWNERS file
+
+# It uses the same pattern rule for gitignore file
+# https://git-scm.com/docs/gitignore#_pattern_format
+
+*                   @AcademySoftwareFoundation/rvos-committers

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,70 @@
+name: Bug Report
+
+description: File a bug report
+
+title: "[Bug]: <title>"
+
+labels: ["bug"]
+
+assignees:
+  - AcademySoftwareFoundation/rvos-committers
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Before submitting it, please make sure it's not already covered by another issue (open or closed).
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: When possible, include steps to reproduce the bug. Also, what behaviour did you expect?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+
+  - type: input
+    id: operating-system-version
+    attributes:
+      label: List all the operating systems versions where this is happening
+      placeholder: Windows 10, macOS 12, macOS 13.2.1, RHEL 7.6
+    validations:
+      required: true
+
+  - type: input
+    id: hardware
+    attributes:
+      label: On what computer hardware is this happening?
+      description: Workstation type, GPU type, CPU + Number of Cores, Memory / RAM, Storage type, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant console log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted, so no need for backticks.
+      render: shell
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment variables
+      description: Please copy and paste any relevant environment variables. They can be accessed through the "Help / Show environment" menu.
+
+  - type: textarea
+    id: extra
+    attributes:
+      label: Extra information
+      description: Please share anything else that might be relevant. RV Preference override? Significant behavior change because of a package?
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://docs.github.com/en/site-policy/github-terms/github-community-code-of-conduct)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: yes
+
+contact_links:
+  - name: "Proposing new features"
+    url: "https://github.com/AcademySoftwareFoundation/OpenRV/discussions/categories/ideas"
+    about: "Post a message to the 'idea' category"
+
+  - name: "Discussing with the OpenRV community"
+    url: "https://github.com/AcademySoftwareFoundation/OpenRV/discussions/categories/general"
+    about: "Post a message to the 'general' category"
+
+  - name: "Troubleshooting build issues"
+    url: "https://github.com/AcademySoftwareFoundation/OpenRV/discussions/categories/build-issues"
+    about: "Post a message to the 'build-issues' category"

.github/PULL_REQUEST_TEMPLATE

@@ -0,0 +1,36 @@
+<!--
+Thanks for your contribution! Please read this comment in its entirety. It's quite important.
+When a contributor merges the pull request, the title and the description will be used to build the merge commit!
+
+### Pull Request TITLE
+
+It should be in the following format:
+
+[ 12345: Summary of the changes made ] Where 12345 is the corresponding Github Issue
+
+OR
+
+[ Summary of the changes made ] If it's solving something trivial, like fixing a typo.
+-->
+
+### Linked issues
+<!--
+Link the Issue(s) this Pull Request is related to.
+
+Each PR should link to at least one issue, in the form:
+
+Use one line for each Issue. This allows auto-closing the related issue when the fix is merged.
+
+Fixes #12345
+Fixes #54345
+-->
+
+### Summarize your change.
+
+### Describe the reason for the change.
+
+### Describe what you have tested and on which operating system.
+
+### Add a list of changes, and note any that might need special attention during the review.
+
+### If possible, provide screenshots.

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+alain.compagnat@autodesk.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.