Merge pull request #130 from Charliekenney23/add-contrib-doc

Add contributing documentation

Author: 0xch4z

.github/CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# Contributing Guidelines
+
+:+1::tada: First off, we appreciate you taking the time to contribute! THANK YOU! :tada::+1:
+
+We put together the handy guide below to help you get support for your work. Read on!  
+
+## I Just Want to Ask the Maintainers a Question
+
+The [Linode Community](https://www.linode.com/community/questions/) is a great place to get additional support.
+
+## How Do I Submit A (Good) Bug Report or Feature Request
+
+Please open a [github issue](https://guides.github.com/features/issues/) to report bugs or suggest features.
+
+When filing an issue or feature request, help us avoid duplication and redundant effort -- check existing open or recently closed issues first. 
+
+Detailed bug reports and requests easier for us to work with. Please include the following in your issue:
+
+* 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
+* Screenshots and code samples where illustrative and helpful
+
+## How to Open a Pull Request
+
+We follow the [fork and pull model](https://opensource.guide/how-to-contribute/#opening-a-pull-request) for open source contributions.
+
+Tips for a faster merge:
+ * address one feature or bug per pull request. 
+ * large formatting changes make it hard for us to focus on your work.
+ * follow language coding conventions.
+ * make sure that tests pass.
+ * make sure your commits are atomic, [addressing one change per commit](https://chris.beams.io/posts/git-commit/). 
+ * add tests!
+
+## Code of Conduct
+
+This project follows the [Linode Community Code of Conduct](https://www.linode.com/community/questions/conduct). 
+
+## Vulnerability Reporting
+
+If you discover a potential security issue in this project we ask that you notify Linode Security via our [vulnerability reporting process](https://hackerone.com/linode). Please do **not** create a public github issue.
+
+## Licensing
+
+See the LICENSE file for our project's licensing.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,34 @@
+## General:
+
+* [ ] Have you removed all sensitive information, including but not limited to access keys and passwords?
+* [ ] Have you checked to ensure there aren't other open or closed [Pull Requests](../../pulls) for the same bug/feature/question?
+
+----
+
+## Feature Requests:
+* [ ] Have you explained your rationale for why this feature is needed? 
+* [ ] Have you offered a proposed implementation/solution? 
+
+----
+
+## Bug Reporting
+
+### Expected Behavior
+
+### Actual Behavior
+
+### Steps to Reproduce the Problem
+
+  1.
+  1.
+  1.
+
+### Environment Specifications
+
+#### Screenshots, Code Blocks, and Logs
+
+#### Additional Notes
+
+----
+
+The [Linode Community](https://www.linode.com/community/questions/) is a great place to get additional support.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+### General:
+
+* [ ] Have you removed all sensitive information, including but not limited to access keys and passwords?
+* [ ] Have you checked to ensure there aren't other open or closed [Pull Requests](../../pulls) for the same bug/feature/question?
+
+### Pull Request Guidelines:
+
+1. [ ] Does your submission pass tests?
+1. [ ] Have you added tests? 
+1. [ ] Are you addressing a single feature in this PR? 
+1. [ ] Are your commits atomic, addressing one change per commit?
+1. [ ] Are you following the conventions of the language? 
+1. [ ] Have you saved your large formatting changes for a different PR, so we can focus on your work?
+1. [ ] Have you explained your rationale for why this feature is needed? 
+1. [ ] Have you linked your PR to an [open issue](https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/)