Create issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,54 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG]"
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Thank you for reporting a bug in OpenSIPS!
+
+In order for us to understand better the issue you are facing, kindly provide all the available information you have about this bug, according to the template below
+-->
+
+**OpenSIPS version you are running**
+<!-- paste below, inside the ticks block,  the output of the `opensips -V` command -->
+
+```
+```
+
+**Describe the bug**
+<!--
+A clear and concise description of what the issue you are experiencing.
+-->
+
+**To Reproduce**
+<!--
+Steps to reproduce the behavior:
+Example:
+1. Start OpenSIPS
+2. Start traffic with special headers
+3. Inspect traces
+4. Notice the `X-Custom-Header` has wrong format
+-->
+
+**Expected behavior**
+<!--
+A clear and concise description of what you expected to happen.
+Example: the expected `X-Custom-Header` header should be sip:user@contact
+-->
+
+**Relevant System Logs**
+<!--
+Please provide, in ticks block, relevant information from the system logs
+-->
+
+**OS/environment information**
+ - Operating System: <!-- (example: `Debian 9`) -->
+ - OpenSIPS installation: <!-- (example: `git`/`source`/`debs`/`manual packages`) -->
+ - other relevant information:
+
+**Additional context**
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/crash-report.md

@@ -0,0 +1,54 @@
+---
+name: Crash Report
+about: Report a crash in OpenSIPS
+title: "[CRASH]"
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Thank you for reporting a crash in OpenSIPS!
+
+In order for us to understand better the reason of the crash, kindly provide all the available information you have about it, according to the template below
+-->
+
+**OpenSIPS version you are running**
+<!-- paste below, inside the ticks block,  the output of the `opensips -V` command -->
+
+```
+```
+
+**Crash Core Dump**
+<!--
+*Please* DO NOT post the content of the corefile here, but rather provide *a link* to a place (dropbox, pastebin, gdrive) where you stored the output of the core dump.
+If you don't have a core dump, please generate one according to the steps described here:
+https://www.opensips.org/Documentation/TroubleShooting-Crash
+-->
+
+**Describe the traffic that generated the bug**
+<!--
+Please describe what kind of traffic made OpenSIPS crash
+-->
+
+**To Reproduce**
+<!--
+Steps to reproduce the behavior:
+Example:
+1. Start OpenSIPS
+2. Start traffic
+3. Check OpenSIPS crashed
+-->
+
+**Relevant System Logs**
+<!--
+Please provide, in ticks block (```example```), relevant information from the system logs
+-->
+
+**OS/environment information**
+ - Operating System: <!-- (example: `Debian 9`) -->
+ - OpenSIPS installation: <!-- (example: `git`/`source`/`debs`/`manual packages`) -->
+ - other relevant information:
+
+**Additional context**
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,42 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[FEATURE]"
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Thank you for issuing a feature request in OpenSIPS!
+
+In order for us to understand better the feature you want, kindly provide all the available information you have about it, according to the template below
+-->
+
+**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.
+-->
+
+**Implementation**
+<!--
+Indicate in which OpenSIPS component this feature affects should be integrated in, and what type the component should have
+--> 
+  - Component: <!-- (example: `core`, `dialog` module, `tm` module) -->
+  - Type: <!-- (example: variable, function, module's parameter) -->
+  - Name: <!-- proposed name of the new element, if relevant -->
+
+**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.
+-->