Use issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Compilation and or execution command lines
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Error message**
+Full Python backtrace or virtual machine outputs
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/general-question.md

@@ -0,0 +1,14 @@
+---
+name: General question
+about: Any questions not related to a bug or a missing feature
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Relevant documentation**
+Which section in the [documentation](https://mp-spdz.readthedocs.io) would you expect your question to be answered? Or is there a missing section?
+
+**The question**
+Please don't be too brief and explain your thinking process. One-line questions are often hard to answer precisely.