Add contributing guidelines

Author: GlassToeStudio

CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# Contributing to Unity Custom Inspector Creator
+We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
+
+## We Develop with Github
+We use github to host code, to track issues and feature requests, as well as accept pull requests.
+
+## All Code Changes Happen Through Pull Requests
+Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `master`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
+
+## Any contributions you make will be under the MIT Software License
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+## Report bugs using Github's [issues](https://github.com/GlassToeStudio/UnityCustomInspectorCreator/issues)
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/GlassToeStudio/UnityCustomInspectorCreator/issues/new); it's that easy!
+
+## Write bug reports with detail, background, and sample code
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+### Example:
+**Steps To Reproduce**
+* Start app
+* Populate 'add' box(es) with 4 and 5
+* Click 'Add' Button
+
+**Expected Behavior**
+* Output should be 9
+
+**Actual Behavior**
+* Output is -1
+
+**If error: provide line number and/or stack trace**
+* Error on line 56 of MathUtils.cs
+
+    ```cs
+    >54 public int Add(int a, int b)
+    >55 {
+    >56     return(a - b);
+    >57 }
+    ```
+
+
+People *love* thorough bug reports. I'm not even kidding.
+
+## Use a Consistent Coding Style
+We use [Microsoft's .NET Guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/)
+
+* 4 spaces for indentation rather than tabs
+* We use Visual Studio or VS Code, which should allow you to automagically implement some of these.
+
+## License
+By contributing, you agree that your contributions will be licensed under its [MIT License](LISCENSE).
+
+## References
+This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md) and this this one [By briandk](https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62)