Add issue templates, codeowners and code of conduct

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @awslabs/mlsrs

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Template
+title: ""
+labels: ""
+assignees: ""
+---
+
+### Description of feature:
+
+A short description of the feature you would like to see implemented.
+
+### Use case:
+
+Describe your particular application's necessity for the feature and why it would be beneficial.
+
+### Implementation discussion (Optional)
+
+If you are planning to implement this feature yourself, please give a brief overview of the changes
+you would be making to accomplish it.

.github/ISSUE_TEMPLATE/general-issue.md

@@ -0,0 +1,33 @@
+---
+name: General Issue
+about: Template
+title: ""
+labels: ""
+assignees: ""
+---
+
+### Security issue notifications
+
+If you discover a potential security issue in mls-rs we ask that you notify AWS Security via our
+[vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a
+public github issue, if in doubt contact AWS security first.
+
+### Problem:
+
+A short description of what the problem is and why we need to fix it. Add reproduction steps if necessary.
+
+### Solution:
+
+A description of the possible solution. Highlight and explain any potentially controversial design decisions taken.
+
+### Requirements / Acceptance Criteria:
+
+What must a solution address in order to solve the problem? How do we know the solution is complete?
+
+- **RFC links:** Links to relevant RFC(s)
+- **Related Issues:** Link any relevant issues
+- **Testing:** How will this change be tested?
+
+### Out of scope:
+
+Is there anything the solution will intentionally NOT address?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+### Issues:
+
+Resolves #ISSUE-NUMBER1
+Addresses #ISSUE-NUMBER2
+
+### Description of changes:
+
+Describe the current behavior and how your code changes that behavior. If there are no issues that this PR resolves, please create one first.
+
+### Call-outs:
+
+Point out areas that need special attention or support during the review process. Discuss architecture or design changes.
+
+### Testing:
+
+How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer?
+
+By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT license.

CODE_OF_CONDUCT.md

@@ -0,0 +1,4 @@
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+opensource-codeofconduct@amazon.com with any additional questions or comments.

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
+information to effectively respond to your bug report or contribution.
+
+## Reporting Bugs/Feature Requests
+
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+
+When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+- A reproducible test case or series of steps
+- The version of our code being used
+- Any modifications you've made relevant to the bug
+- Anything unusual about your environment or deployment
+
+## Contributing via Pull Requests
+
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the _main_ branch.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+
+To send us a pull request, please:
+
+1. Fork the repository.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+3. Ensure local tests pass.
+4. Commit to your fork using clear commit messages.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+## Finding contributions to work on
+
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
+
+## Code of Conduct
+
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+opensource-codeofconduct@amazon.com with any additional questions or comments.
+
+## Security issue notifications
+
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+
+## Licensing
+
+See the [LICENSE (Apache)](LICENSE-apache) and [LICENSE (MIT)](LICENSE-mit) files for our project's licensing. We will ask you to confirm the licensing of your contribution.