Add merge request templates and contributing.md

Author: Craig-J

.gitlab/merge_request_templates/default.md

@@ -0,0 +1,37 @@
+## This Merge Request Template
+
+This merge request template is the default and should be used when contributing any changes to stable packages.
+
+For contributions to pre-release/preview packages use the lightweight merge request template.
+
+For release merge requests, use the release template.
+
+## Summary
+
+_Summary of the purpose of this merge request._
+
+## Contributor Tasks
+
+_These tasks are for the merge request creator to tick off when creating a merge request._
+
+- [ ] Pair review with a member of the QA team.
+- [ ] Add any release testing considerations to the MR for the next release.
+- [ ] Check any relevant CHANGELOG files have been updated.
+- [ ] Ensure documentation requirements are met e.g., public API is commented.
+- [ ] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
+- [ ] Add any relevant labels such as `breaking` to this MR.
+
+## Reviewer Tasks
+
+_Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged._
+
+[Use emojis in review threads to communicate intent and help contributors.](../../CONTRIBUTING.md#review-threads)
+
+- [ ] Code reviewed.
+- [ ] Non-code assets e.g. Unity assets/scenes reviewed.
+- [ ] Documentation has been reviewed. Includes checking documentation requirements are met and not missing e.g., public API is commented.
+- [ ] Checked and agree with release testing considerations added to MR for the next release.
+
+## Closes JIRA Issue
+
+_If this MR closes any JIRA issues list them below in the form `Closes PROJECT-#`_

.gitlab/merge_request_templates/lightweight.md

@@ -0,0 +1,29 @@
+## This Merge Request Template
+
+This merge request template is for contributing to pre-release/preview packages and has fewer tasks to complete. The quality threshold for reviewing these merge requests is lower - prioritize a lean review process.
+
+## Summary
+
+_Summary of the purpose of this merge request._
+
+## Contributor Tasks
+
+_These tasks are for the merge request creator to tick off when creating a merge request._
+
+- [ ] Pair review with a member of the QA team.
+- [ ] Add any release testing considerations to the MR for the next release.
+- [ ] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
+
+## Reviewer Tasks
+
+_Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged._
+
+[Use emojis in review threads to communicate intent and help contributors.](../../CONTRIBUTING.md#review-threads)
+
+- [ ] Code reviewed.
+- [ ] Non-code assets e.g. Unity assets/scenes reviewed.
+- [ ] Checked and agree with release testing considerations added to MR for the next release.
+
+## Closes JIRA Issue
+
+_If this MR closes any JIRA issues list them below in the form `Closes PROJECT-#`_

.gitlab/merge_request_templates/release.md

@@ -0,0 +1,30 @@
+## This Merge Request Template
+
+This merge request template is for release merge requests.
+
+## Summary
+
+_Summary of the purpose of this merge request._
+
+## Release Tasks
+
+_These tasks are for the merge request creator to tick off when creating a merge request._
+
+- [ ] Run through the pre-release steps on [Confluence](https://ultrahaptics.atlassian.net/wiki/spaces/SV/pages/3665625233). The rest of the process continues after this merge request is merged.
+- [ ] Check any relevant CHANGELOG files have been updated.
+- [ ] Ensure documentation requirements are met e.g., public API is commented.
+- [ ] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
+- [ ] Add any relevant labels such as `breaking` to this MR.
+- [ ] Ensure package.json files are updated with new package versions and any changes dependency versions.
+- [ ] If this is a major release, action any `Obsolete` items and other breaking considerations.
+- [ ] Check that additional release tasks for each MR contributing to this release have been considered.
+
+### Additional Release Tasks
+
+_This task list should be populated from MRs contributing to this release. Can include functionality tests and regression tests such as tests for integration of multiple features as well as any other tasks that should be performed during the release._
+
+- [ ] 
+
+## Closes JIRA Issue
+
+_If this MR closes any JIRA issues list them below in the form `Closes PROJECT-#`_

CONTRIBUTING.md

@@ -0,0 +1,12 @@
+# Contributing to Unity Plugin
+
+We welcome contributions from the community. Feel free to create an issue or submit a pull request to address problems you've been having or add new functionality that others would be interested in.
+
+## Review Threads
+Help the contributor when reviewing by using emoji's to show intent with each thread:
+* :eyes:  - “Please do this, I want to look at it again once done / discuss it further” - reviewer is responsible for resolving thread
+* :see_no_evil: - “Please do this, I don’t need to look at it again once done” - MR submitter is responsible for resolving thread
+* :shrug: - “Suggestion, I don’t mind if you do it or not” - MR submitter is responsible for resolving thread
+* :+1: - “This is just a positive comment on your code, no changes needed” - MR submitter is responsible for resolving thread
+
+Got ideas for any other emojis that would be helpful? Add them here with an MR :eyes:.