Add github Template

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,53 @@
+---
+name: Bug report
+about: Report us a bug
+
+---
+
+---
+### Describe the bug
+
+> A clear and concise description of what the bug is.
+
+---
+### Reproduction scenario
+
+> **note**: You might want to use the Vagrant environment to create a reproducible scenario triggering the bug.
+
+Steps to reproduce the behaviour:
+
+1. ...
+2. ...
+
+---
+### Expected behaviour
+
+> A clear and concise description of what you expected to happen.
+
+---
+### Allspark informations
+
+> Informations about the control and allspark machines.
+
+- *Terraform version* (if used to reproduce the issue) :
+
+```
+output of `terraform version`
+```
+
+- *Vagrant version* (if used to reproduce the issue) :
+
+```
+output of `vagrant version`
+```
+
+  - *Vagrant plugin version* (if used to reproduce the issue) :
+
+```
+output of `vagrant plugin list`
+```
+
+---
+### Additional context
+
+> Add any other informations about the problem here. (e.g: logs, screenshots)

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea
+
+---
+
+---
+### Feature
+
+> Describe the feature with its scope.
+> Replace $ROLE by the role of the feature destinated users (e.g: developer, user, operator)
+
+- as a $ROLE i need ...
+
+
+---
+### Motivation
+
+> Why is this feature needed ?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+### Current behaviour
+
+> Describe here the observed behaviour of the software.
+
+---
+### Expected behaviour
+
+> Describe here what you expected the software to do instead.
+
+---
+### Modifications
+
+> What are the changes involved to match with the expected behaviour ?
+
+-  [ ] ...
+-  [ ] ...
+-  [ ] ...
+
+---
+### Related issues
+
+> What issue are affected by or affecting this pull request.
+
+- resolve #
+
+> **note** : Put closes #XXXX in your commit message to auto-close the issue that your PR fixes (if such).
+
+---
+### Status
+
+- [ ] Implementation
+- [ ] Test coverage
+- [ ] Documentation
+- [ ] ...

.github/stale.yml

@@ -0,0 +1,52 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 30
+
+# Number of days of inactivity before a stale Issue or Pull Request is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: 7
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels: []
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: false
+
+# Label to use when marking as stale
+staleLabel: stale
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  activity in the past month. It will be closed in one week if no further activity occurs.
+  Thank you for your contributions.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+
+# Comment to post when closing a stale Issue or Pull Request.
+# closeComment: >
+#   Your comment here.
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed