Add issue templates. #623
12
.github/ISSUE_TEMPLATE/1_Software_Suggestion.md
vendored
Normal file
@ -0,0 +1,12 @@
|
||||
|
|
||||
---
|
||||
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
name: "🆕 Software Suggestion"
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
about: Suggest new software that enhances privacy.
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
---
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
## Basic Information
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
jonah
commented
Maybe add some fields like name and category? Maybe add some fields like name and category?
```suggestion
**URL:**
```
|
||||
**Name:**
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
**Category:**
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
**URL:**
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
## Description
|
||||
|
jonah
commented
Do we need these for issues? Do we need these for issues?
Which part? Both? Which part? Both?
jonah
commented
Screenshots. Description should be enough. Screenshots. Description should be enough.
```suggestion
**URL:**
```
|
||||
7
.github/ISSUE_TEMPLATE/2_Software_Removal.md
vendored
Normal file
@ -0,0 +1,7 @@
|
||||
```suggestion
### Description
```
```suggestion
### Description
```
|
||||
---
|
||||
```suggestion
### Description
```
|
||||
name: "❌ Software Removal"
|
||||
```suggestion
### Description
```
|
||||
about: Suggest the removal of outdated, insecure, or otherwise bad software.
|
||||
```suggestion
### Description
```
|
||||
---
|
||||
```suggestion
### Description
```
|
||||
|
||||
```suggestion
### Description
```
|
||||
## Description
|
||||
```suggestion
### Description
```
|
||||
|
||||
```suggestion
### Description
```
|
||||
6
.github/ISSUE_TEMPLATE/3_Discussion.md
vendored
Normal file
@ -0,0 +1,6 @@
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
---
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
name: "💬 Discussion"
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
about: Discuss the website or any mentioned software in general.
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
---
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
<!-- Remember to stay civil! -->
|
||||
|
jonah
commented
I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it. I'd make this an HTML comment so that the user sees it but it doesn't get rendered even if he forgets to remove it.
@Shifterovich what do you think of this? ```suggestion
about: Discuss the website or any mentioned software in general.
```
@Shifterovich what do you think of this?
jonah
commented
👍 The point of discussions is to mainly discuss mentioned software. :+1: The point of discussions is to *mainly* discuss mentioned software.
|
||||
7
.github/ISSUE_TEMPLATE/4_Feature.md
vendored
Normal file
@ -0,0 +1,7 @@
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
---
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
name: "✨ Feature Suggestion"
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
about: Suggest a new feature for the website.
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
---
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
## Description:
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
|
||||
|
jonah
commented
What do you mean by mockup in this context? What do you mean by mockup in this context?
I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes. I was thinking these would be meta-website-related changes (like "change this color" or "move this button here") - which would benefit from having a picture sometimes.
jonah
commented
That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts? That highly depends on the type of the feature. I'd only keep the description and ditch the mockup. @Vincevrp thoughts?
|
||||
12
.github/ISSUE_TEMPLATE/5_Website_Issues.md
vendored
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
name: "🌐 Website Issues"
|
||||
about: Report issues with the website.
|
||||
---
|
||||
|
||||
## Description
|
||||
|
Your headings are inconsistent. I prefer to use h2 like you did here, instead of h3 in the other templates. Your headings are inconsistent. I prefer to use h2 like you did here, instead of h3 in the other templates.
|
||||
|
||||
<!--
|
||||
## Screenshots
|
||||
|
||||
Please add screenshots if applicable
|
||||
-->
|
||||
Do we need these for issues?
Do we need these for issues?
Which part? Both?
Which part? Both?
Screenshots. Description should be enough.
Screenshots. Description should be enough.