Merge pull request #1483 from matthiasbeyer/readme-vacation-notice

Readme vacation notice

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,35 @@
+<!--
+
+Thank you very much for contributing to imag.
+
+Please notice: I, the author of imag, am currently on a sabatical (May 2018
+until early 2019). I am not sure whether I will have access to the internet
+during that time. I may respond slowly - delay of 2-4 weeks or even more are
+possible! I hope it won't be more.
+
+
+For below: Omit the not applicable sections.
+
+-->
+
+### Issue type
+
+- [ ] Bug
+- [ ] Idea/Feature request
+- [ ] Question/Other
+
+<!-- In case of a bug: -->
+
+### What I tried to do
+
+### What I expected to happen
+
+### What happened
+
+### My idea on how to solve this issue
+
+### Metadata
+
+* Output of `imag-<tool> --version`
+* Output of `imag --versions` (if multiple imag tools were used)
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+<!--
+
+Thank you very much for contributing to imag.
+
+Please notice: I, the author of imag, am currently on a sabatical (May 2018
+until early 2019). I am not sure whether I will have access to the internet
+during that time. I may respond slowly - delay of 2-4 weeks or even more are
+possible! I hope it won't be more.
+
+-->
+
+### PR type
+
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Refactor/dependency update
+- [ ] Other
+

README.md

@@ -12,6 +12,17 @@
 but we do not consider anything stable or usable at this moment. Feel free to
 play around anyways.**
 
+## Vacation notice
+
+**Notice:** I, the author of imag, will be on vacation from mid-May 2018 until
+early 2019. I hope I can continue develop imag during that time, but I cannot
+guarantee that. I hope I can continue development of imag after that and I
+certainly plan to do so.
+
+But from May 2018 until early 2019, expect long response times on issues and
+pull requests.
+
+
 ## Goal / What is imag?
 
 Our (long-term) goal is to