new issue format

This commit is contained in:
youtous 2020-05-07 00:55:56 +02:00
parent b6bc3bc073
commit 6b071c5c26
No known key found for this signature in database
GPG key ID: 592173AE8CD254A5
4 changed files with 122 additions and 33 deletions

View file

@ -21,7 +21,7 @@ to the master branch, you will only need to submit one pull request.
Don't do pull requests against `-stable` branches. Always target the master branch. Any bugfixes we'll backport to those branches. Don't do pull requests against `-stable` branches. Always target the master branch. Any bugfixes we'll backport to those branches.
At this point, you're waiting on us. We like to at least comment on, if not At this point, you're waiting on us. We like to at least comment on, if not
accept, pull requests within several days days. accept, pull requests within several days.
We may suggest some changes or improvements or alternatives. We may suggest some changes or improvements or alternatives.
Some things that will increase the chance that your pull request is accepted. Some things that will increase the chance that your pull request is accepted.

View file

@ -1,36 +1,14 @@
---
name: "\U0001F41E Bug report"
about: Create a report about a reproducible bug
title: ''
labels: bug, needs triage
assignees: ''
---
<!--- Provide a general summary of the issue in the Title above --> <!--- Provide a general summary of the issue in the Title above -->
## Context <!-- Thanks for the bug report! -->
<!--- Provide a more detailed introduction to the issue itself -->
<!--- How has this issue affected you? What were you trying to accomplish? -->
## Expected Behavior
<!--- Tell us what should happen -->
## Actual Behavior
<!--- Tell us what happens instead -->
## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the issue -->
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this issue include code to reproduce, if relevant -->
1.
2.
3.
4.
## Your Environment
<!--- Include as many relevant details about the environment you experienced the issue in -->
* Amount of RAM available:
* Mailserver version used:
* Docker version used:
* Environment settings relevant to the config:
* Any relevant stack traces ("Full trace" preferred):
<!--- Please remember to format code using triple backticks (`)
so that it is neatly formatted when the issue is posted. -->
<!--- <!---
@ -52,9 +30,57 @@
* FAQ and tips * FAQ and tips
https://github.com/tomav/docker-mailserver/wiki/FAQ-and-Tips https://github.com/tomav/docker-mailserver/wiki/FAQ-and-Tips
* And the WIKI * The wiki
https://github.com/tomav/docker-mailserver/wiki https://github.com/tomav/docker-mailserver/wiki
* Open issues * Open issues
https://github.com/tomav/docker-mailserver/issues https://github.com/tomav/docker-mailserver/issues
--> -->
## Context
<!--- Provide a more detailed introduction to the issue itself -->
<!--- How has this issue affected you? What were you trying to accomplish? -->
### *What* is affected by this bug?
### *When* does this occur?
## *How* do we replicate the issue?
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this issue include code to reproduce, if relevant -->
1.
2.
3.
4.
## Actual Behavior
<!--- Tell us what happens instead -->
## Expected behavior (i.e. solution)
<!--- Tell us what should happen -->
## Your Environment
<!--- Include as many relevant details about the environment you experienced the issue in -->
* Amount of RAM available:
* Mailserver version used:
* Docker version used:
* Environment settings relevant to the config:
* Any relevant stack traces ("Full trace" preferred):
<!---
Please remember to format code using triple backticks (`) so that it is neatly formatted when the issue is posted.
Spoilers are recommended for readability:
<details>
<summary>Click me to expand </summary>
```sh
echo "hello world"
```
</details>
-->

View file

@ -0,0 +1,42 @@
---
name: "\U0001F389 Feature request"
about: Suggest an idea for this project
title: ''
labels: feature request, needs triage
assignees: ''
---
## Is your feature request related to a problem?
<!-- A clear and concise description of what the problem is. -->
## Describe the solution you'd like
<!-- A clear and concise description of what you want to happen. -->
## Alternatives you've considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
## Who will that feature be useful to?
<!-- Is it solving a common problem, or is it an improvement that all current users will benefit from? -->
## What have you done already?
<!-- If you already built a prototype or a complete implementation of that feature, where is it possible to see it? -->
## What are you going to contribute?
<!-- Besides testing volunteering work made by other people, what are you going to contribute in order to help have that feature implemented, tested and documented? -->
## Additional context
<!-- Add any other context about the feature request here. -->

21
.github/ISSUE_TEMPLATE/questions.md vendored Normal file
View file

@ -0,0 +1,21 @@
---
name: "❓ Question"
about: Ask a question about docker-mailserver
title: ''
labels: question, needs triage
assignees: ''
---
## Subject
<!-- Select one, remove the others: -->
* [ ] I would like to contribute to the project (code, documentation, advocacy, integration, ...)
* [ ] I would like some help for integrating this container with another service (rainloop, PostFWD, ...)
* [ ] I would like to configure a not documented mail server use case
* [ ] I would like some feedback concerning a use case
* [ ] I have questions about TLS/SSL/STARTTLS/OpenSSL
* [ ] Other
## Description