chore: repo updates (#31)

Author: fuzzzerd

.github/BUG_TEMPLATE.yml

@@ -0,0 +1,57 @@
+name: 🐞 Bug
+description: File a bug/issue report
+title: "[BUG] <title>"
+labels: ["bug", "Needs Triage"]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Current Behavior
+    description: A concise description of the problem you are experiencing.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: A concise description of what you expected to happen.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: Steps to reproduce the behavior.
+    placeholder: |
+      1. In this environment...
+      1. With this config...
+      1. Run '...'
+      1. See error...
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Environment
+    description: |
+      examples:
+        - **OS**: Ubuntu 20.04
+        - **OS**: MacOS 20.04
+        - **OS**: Windows 11     
+    value: |
+        - OS:
+    render: markdown
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the issue you are encountering!
+
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false

CONTRIBUTING.md

@@ -0,0 +1,11 @@
+# Contributing
+
+Contributions are welcome! As an open source project, any help we can get fixing bugs or adding features is always appreciated. In all cases, PRs will be reviewed with an eye toward future maintainability, so things like good comments, unit test coverage, and thorough design are importat considerations. If you decide to work on a bug or feature from our issue list, please be prepared to work through design or maintenance issues in the PR.
+
+## Features
+
+Please open an issue discussing your idea prior to beginning work on a pull request. We want to make sure that any work is directed in a way that is likely to be merged into master and ultimately shipped. Since any new feature adds maintenance effort, we have to be judicious with the features we accept.
+
+## Bugs
+
+If you have found a bug, please open an issue! If you have a fix, we'd love for you to include a PR that addresses the issue.

SECURITY.md

@@ -0,0 +1,13 @@
+# Security Policy
+
+Only patches or issues that effect the latest version of SharpFM will be addressed.
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.x     | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+For security related issues, please contact <https://github.com/fuzzzerd> directly with detailed information regarding the vulnerability or explot. If you have an associated change/fix, please include a .patch file or a description of how it can be fixed. If you'd like to open a PR with a fix that is also great, provided that does not directly expose an explit.