Added github files

.github/CONTRIBUTING.md

@@ -0,0 +1,31 @@
+## How to Contribute to This Project
+
+#### **Did You Find a Bug?**
+
+  * **Ensure the bug was not already reported** by searching on GitHub under **Issues**.
+  * If you're unable to find an open issue addressing the problem, **open a new one**. Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
+
+#### **Did You Write a Patch That Fixes a Bug?**
+
+  * Open a new GitHub pull request with the patch.
+    1. Fork this project
+    1. Create your feature branch: `git checkout -b my-new-feature`
+    1. Commit your changes: `git commit -am 'Add some feature'`
+    1. Push to the branch: `git push origin my-new-feature`
+    1. Submit a pull request via GitHub's web interface
+  * Ensure the PR description clearly describes the problem and its solution. Include the relevant issue number if applicable.
+
+#### **Do You Intend to Add a New Feature or Change an Existing One?**
+
+  * Suggest your change as a **new issue** using the label `enhancement` **BEFORE** you start writing code.
+
+#### **Do You Want to Sponsor Open Source Development?**
+
+If you need express resolution of a bug or new features you can consider the opportunity of **sponsoring** the relevant development.
+
+  * Open an issue on GitHub (of type `bug` or `enhancement`) with the details of what you want 
+  * Contact [example42](http://www.example42.com/#contact) referring the issue you created
+  * Tell us how you want to sponsor the development (sending money, gifts or offering services)
+  * If we agree on the conditions we will place your [company] name in the module's Sponsors List
+
+Thanks for contributing! :heart:

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+## Expected Behavior 
+
+
+## Actual Behavior
+
+
+## Steps to Reproduce the Problem
+
+  1. 
+  1. 
+  1. 
+
+## Specifications
+
+Please add this info:
+
+  1. Output of ```facter -p``` on the failing node (at least the OS related facts)
+  1. Version of Puppet and of the module
+  1. The relevant Puppet code and eventually Hiera data

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,12 @@
+## Before submitting your PR
+
+  1. Open an **issue** and refer to its number in your PR title
+  1. If it's a bug and you have the solution, go on with the PR! 
+  1. If it's an enhancement, please wait for our feedback before starting to work on it
+  1. Please run ```puppet-lint``` on your code and ensure it's compliant
+
+## After submitting your PR
+
+  1. Verify Travis checks and eventually fix the errors
+  1. Feel free to ping us if we don't reply promptly 
+