Merge branch '8.0'

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,62 @@
+name: 🐞 Report a bug
+description: We made a mess, sorry for that and thank you for telling us.
+title: "BUG: <title>"
+labels: [Bug]
+body:
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: textarea
+    attributes:
+      label: Current Behavior
+      description: A concise description of what you're experiencing.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A concise description of what you expected to happen instead.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Steps To Reproduce
+      description: |
+        To understand your problem faster we need a description how the issue can be
+        reproduced. Please be as specific as possible here, this helps us solving
+        issues faster. Issues that cannot be reproduced are hardly ever fixed.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Environment
+      description: |
+        If you report a bug add the versions of Flow that you are using.
+        If you want to be a super-hero, try to find out the oldest supported version
+        affected by the bug you describe. Thanks!
+      value: |
+        - Flow:
+        - PHP:
+      render: markdown
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Anything else?
+      description: |
+        Links? References? Anything that will give us more context about the issue you are encountering!
+
+        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        ### Sponsoring / Support ###
+
+        Since we are an open source project we always have to find time for the tasks at hand.
+        By sponsoring you may be able to by the time needed actually work on the feature you need.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Neos Forum
+    url: https://discuss.neos.io/
+    about: The official online forum for questions and discussions around Neos.
+  - name: Neos Slack
+    url: https://slack.neos.io/
+    about: Direct chat of the Neos creators and users.

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,33 @@
+name: 🎁 Request a new feature
+description: You are missing a feature, please tell us about it
+title: "FEATURE: <title>"
+labels: [Feature]
+body: 
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: textarea
+    attributes:
+      label: Description
+      description: | 
+        Please describe the feature briefly. Try to avoid beeing specific about the solution as there may be more options available.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Possible Solution
+      description: | 
+        If you already have an idea how the feature could be implemented describe this here. We may still suggest other solutions but will consider your suggestion.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        ### Sponsoring / Support ###
+  
+        Since we are an open source project we always have to find time for the tasks at hand. 
+        By sponsoring you may be able to by the time needed actually work on the feature you need.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,21 +1,36 @@
-<!--
-Thanks for your contribution, we appreciate it!
+<!-- 
+    Thanks for your contribution, we appreciate it!
 
-Please read through our pull request guidelines, there are some interesting things there:
-https://discuss.neos.io/t/creating-a-pull-request/506
+    The first section should explain briefly what is changed. 
+    Some examples are always nice to showcase the use. 
+    The content will be used in the change-logs and addresses 
+    developers working with Neos.
 
-And one more thing... Don't forget about the tests!
+    If there are issues regarding the topic of your PR link 
+    them here as `related:` or `resolved:`
 -->
 
+**Upgrade instructions**
 
-**What I did**
+<!-- 
+    Add upgrade instructions for breaking changes. 
+    Explain who is affected, what has to be adjusted  
+-->
 
-**How I did it**
+**Review instructions**
 
-**How to verify it**
+<!-- 
+    If your change is not explained fully by the first section you can 
+    add more details here to help the reviewers understand the change.
+    We have to understand what you did, why you did it and how we can 
+    verify it works correctly and does no harm.
+-->
 
 **Checklist**
 
 - [ ] Code follows the PSR-2 coding style
 - [ ] Tests have been created, run and adjusted as needed
 - [ ] The PR is created against the [lowest maintained branch](https://www.neos.io/features/release-roadmap.html)
+- [ ] Reviewer - PR Title is brief but complete and starts with `FEATURE|TASK|BUGFIX`
+- [ ] Reviewer - The first section explains the change briefly for change-logs
+- [ ] Reviewer - Breaking Changes are marked wit `!!!` and have upgrade-instructions