From ce8a7f9a8ca70c73f8ecefca8309e412c36b8880 Mon Sep 17 00:00:00 2001 From: Mark Whiting Date: Wed, 6 Dec 2017 10:24:06 -0800 Subject: [PATCH] Added security email and made instructions more clear --- issue_template.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/issue_template.md b/issue_template.md index 50ebf469..d1f8aa6f 100644 --- a/issue_template.md +++ b/issue_template.md @@ -1,9 +1,11 @@ -### The problem -1. Replace this text with a clear statement of the problem (e.g. #1017) including any relevant supporting files. If its a software abnormality, explain how it should act, how it does act, and how to reproduce it. + +1. Replace this text with a clear statement of the problem that needs to be solved including any relevant supporting files. +- If its a software abnormality, explain how it should act, how it does act, and how to reproduce it. +- **If you are reporting a security related problem,** DO NOT report here. Email support@daemo.org instead. 2. Add a title in the field above that consisely summarizes the problem. -### The proposal -3. If you have a solution to this problem and you will implement it, continue, otherwise remove the **proposal** section. +### My proposal +3. If you have a solution to this problem and you will implement it, continue, otherwise remove the **my proposal** section. 4. Replace this text with a clear statement of the solution you propose to implement, including any relevant supporting files. It can strengthen your proposal to include *pros* and *cons* and your thoughts about the *implications* (short and long term) of it being executed.