add issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug Report
+about: Bug reports about the ZoKrates toolbox.
+---
+
+<!--## Prerequisites
+
+- First, many thanks for taking part in the community. We really appreciate that.
+- Support questions are better asked on our [gitter channel](https://gitter.im/ZoKrates/ZoKrates) 
+- Ensure the issue isn't already reported.
+- The issue should be reproducible with the latest ZoKrates version; however, this isn't a hard requirement and being reproducible with an older version is sufficient.
+
+*Delete the above section and the instructions in the sections below before submitting*
+
+-->
+
+## Description
+
+<!--Please shortly describe the bug you have found, and what you expect instead.-->
+
+## Environment
+
+- Compiler version:
+- Operating system:
+
+## Steps to Reproduce
+
+<!--
+Please provide a *minimal* source code example to trigger the bug you have found.
+Please also mention any command line flags that are necessary for triggering the bug.
+Provide as much information as necessary to reproduce the bug.
+
+```zokrates
+// Some *minimal* ZoKrates source code to reproduce the bug.
+// ...
+```
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,43 @@
+---
+name: Feature Request
+about: ZoKrates toolbox feature requests.
+---
+
+<!--## Prerequisites
+
+- First, many thanks for taking part in the community. We really appreciate that.
+- Support questions are better asked on our [gitter channel](https://gitter.im/ZoKrates/ZoKrates) 
+- Ensure the issue isn't already reported.
+
+*Delete the above section and the instructions in the sections below before submitting*
+
+-->
+
+## Abstract
+
+<!--
+Please describe with an example what problem you see in the current ZoKrates toolbox.
+-->
+
+## Motivation
+
+<!--
+In this section you describe how you propose to address the problem you described earlier,
+including by giving one or more exemplary source code snippets for demonstration.
+-->
+
+## Specification
+
+<!--
+The technical specification should describe the syntax and semantics of any new feature. The
+specification should be detailed enough to allow any developer to implement the functionality.
+-->
+
+## Backwards Compatibility
+
+<!--
+All language changes that introduce backwards incompatibilities must include a section describing
+these incompatibilities and their severity.
+
+Please describe how you propose to deal with these incompatibilities.
+-->