From 1f0adf739fd1aaa1a839c2ee0e8ed949280685d7 Mon Sep 17 00:00:00 2001 From: Jeremy Thomerson Date: Fri, 10 Jan 2020 02:59:42 -0500 Subject: [PATCH] chore: update issue templates --- .github/ISSUE_TEMPLATE/bug_report.md | 49 +++++++++++++++++++++++ .github/ISSUE_TEMPLATE/feature_request.md | 22 ++++++++++ 2 files changed, 71 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..62ac156 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,49 @@ +--- +name: Bug report +about: Create a report to help us improve +title: "[BUG]" +labels: '' +assignees: '' + +--- + +**Describe the bug** +A clear and concise description of what the bug is. + +**To Reproduce** +If you'd like assistance, you will need to post a [minimal, complete, verifiable example](https://stackoverflow.com/help/minimal-reproducible-example). (MCVE) Sometimes just by creating a MCVE you will actually discover the source of the problem yourself - or at least more details to help us reproduce it. + +If you want some good examples of MCVE's, see a couple of issues that we have posted elsewhere, e.g: + + * https://github.com/videojs/video.js/issues/4765 + * https://github.com/videojs/http-streaming/issues/172 + +All of that detail is really important in getting help - especially on an open source plugin where people are donating their time. Without it we can't be sure what version of VideoJS you're using, or what other plugins you're using with it. + +If you are unable to create an MCVE, you may still open a defect, but you must provide as much detail as possible. Defects opened without an MCVE have a much greater chance of being closed without investigation. Please remember: we are volunteers and do not have time to debug applications for every user that uses our plugins. If you show that you've put the effort into trying to debug it yourself and provide us with an MCVE and as much detail as possible, we will be much more interested in assisting you. + +Steps to reproduce the behavior: +1. Go to '...' +2. Click on '....' +3. Scroll down to '....' +4. See error + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Screenshots** +If applicable, add screenshots to help explain your problem. + +**Desktop (please complete the following information):** + - OS: [e.g. iOS] + - Browser [e.g. chrome, safari] + - Version [e.g. 22] + +**Smartphone (please complete the following information):** + - Device: [e.g. iPhone6] + - OS: [e.g. iOS8.1] + - Browser [e.g. stock browser, safari] + - Version [e.g. 22] + +**Additional context** +Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..ff85ca8 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,22 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: "[FEATURE REQUEST]" +labels: '' +assignees: '' + +--- + +Feel free to submit feature requests if you see something that you really think could be an enhancement to this project. However, please note: we do not promise to implement feature requests. We are volunteers working on this project for free. If a feature request seems beneficial for the project, we will work on it as time allows. We encourage you to consider implementing the feature request yourself. Well-written pull requests to add features that show that they have a high quality and are well tested will be accepted if they comply with our [coding standards](https://github.com/silvermine/silvermine-info/blob/master/coding-standards.md). + +**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. + +**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.