Create CONTRIBUTING.md

Author: Tanner Blair

CONTRIBUTING.md

@@ -0,0 +1,46 @@
+# Contribution Guide
+
+This project adheres to the following standards and practices.
+
+
+## Versioning
+
+This project is versioned under the [Semantic Versioning](http://semver.org/) guidelines as much as possible.
+
+Releases will be numbered with the following format:
+
+- `<major>.<minor>.<patch>`
+- `<breaking>.<master>.<develop>`
+
+And constructed with the following guidelines:
+
+- Breaking backward compatibility bumps the major and resets the minor and patch.
+- New additions without breaking backward compatibility bumps the minor and resets the patch.
+- Bug fixes and misc changes bumps the patch.
+
+
+## Pull Requests
+
+The pull request process differs for new features and bugs.
+
+Pull requests for bugs may be sent without creating any proposal issue. If you believe that you know of a solution for a bug that has been filed, please leave a comment detailing your proposed fix or create a pull request with the fix mentioning that issue id.
+
+
+## Coding Standards
+
+This project follows LabVIEW Best Practices
+
+## Feature Requests
+
+If you have a proposal or a feature request, you may create an issue with `[Proposal]` in the title.
+
+The proposal should also describe the new feature, as well as implementation ideas. The proposal will then be reviewed and either approved or denied. Once a proposal is approved, a pull request may be created implementing the new feature.
+
+
+## Git Flow
+
+This project follows [Git-Flow](http://nvie.com/posts/a-successful-git-branching-model/), and as such has `master` (latest stable releases), `develop` (latest WIP development) and X.Y support branches (when there's multiple major versions).
+
+Accordingly all pull requests MUST be sent to the `develop` branch.
+
+> **Note:** Pull requests which do not follow these guidelines will be closed without any further notice.