Bring back PrusaSlicer history till 2.4

.github/CONTRIBUTING.md

@@ -0,0 +1,21 @@
+Did you encounter an issue with using PrusaSlicer? Fear not! This guide will help you to write a good bug report in just a few, simple steps.
+
+There is a good chance that the issue, you have encountered, is already reported. Please check the [list of reported issues](https://github.com/prusa3d/PrusaSlicer/issues) before creating a new issue report. If you find an existing issue report, feel free to add further information to that report.
+
+If possible, please include the following information when [reporting an issue](https://github.com/prusa3d/PrusaSlicer/issues/new):
+* PrusaSlicer version (See the about dialog for the version number. If running from git, please include the git commit ID from `git rev-parse HEAD` also.)
+* Operating system type + version
+* Steps to reproduce the issue, including:
+    * Command line parameters used, if any
+    * PrusaSlicer configuration file (Use ``Export Config...`` from the ``File`` menu - please don't export a bundle)
+    * Expected result
+    * Actual result
+    * Any error messages
+* If the issue is related to G-code generation, please include the following:
+    * STL, OBJ or AMF input file (please make sure the input file is not broken, e.g. non-manifold, before reporting a bug)
+    * a screenshot of the G-code layer with the issue (e.g. using [Pronterface](https://github.com/kliment/Printrun))
+
+Please make sure only to include one issue per report. If you encounter multiple, unrelated issues, please report them as such.
+
+Simon Tatham has written an excellent on article on [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which is well worth reading, although it is not specific to PrusaSlicer.
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,27 @@
+### Version
+_Version of PrusaSlicer used goes here_
+
+_Use `About->About PrusaSlicer` for release versions_
+
+_For -dev versions, use `git describe --tag` or get the hash value for the version you downloaded or `git rev-parse HEAD`_
+
+### Operating system type + version
+_What OS are you using, and state any version #s_
+_In case of 3D rendering issues, please attach the content of menu Help -> System Info dialog_
+
+### 3D printer brand / version + firmware version (if known)
+_What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s_
+
+### Behavior
+* _Describe the problem_
+* _Steps needed to reproduce the problem_
+  * _If this is a command-line slicing issue, include the options used_
+* _Expected Results_
+* _Actual Results_
+  * _Screenshots from __*PrusaSlicer*__ preview are preferred_
+
+_Is this a new feature request?_
+
+#### Project File (.3MF) where problem occurs
+_Upload a PrusaSlicer Project File (.3MF) (`Plater -> Export plate as 3MF` for Slic3r PE 1.41.2 and older, `File -> Save` / `Save Project` for PrusaSlicer, Slic3r PE 1.42.0-alpha and newer)_
+_Images (PNG, GIF, JPEG), PDFs or text files could be drag & dropped to the issue directly, while all other files need to be zipped first (.zip, .gz)_