From c6fe09753539dd60b6653ae8b0fa35bf93638585 Mon Sep 17 00:00:00 2001
From: Camila <hello@camila.codes>
Date: Tue, 12 Jan 2021 17:56:21 +0100
Subject: [PATCH] Update Github issue template with the new 3.1 option to
 "Create Debug Archive".

Also:
- cleaned up some of the text: nobody read that and it was mostly
from a time when this team was only one person.
- remove references to e2ee known issues. Not relevant anymore.

Signed-off-by: Camila <hello@camila.codes>
---
 .github/issue_template.md | 23 ++++++++---------------
 1 file changed, 8 insertions(+), 15 deletions(-)

diff --git a/.github/issue_template.md b/.github/issue_template.md
index 7a8f1664f..b9f19485b 100644
--- a/.github/issue_template.md
+++ b/.github/issue_template.md
@@ -1,11 +1,7 @@
 <!--
 Thanks for reporting issues back to Nextcloud!
 
-Note: This is the **issue tracker of Nextcloud**, please do NOT use this to get answers to your questions or get help for fixing your installation. This is a place to report bugs to developers, after your server has been debugged. You can find help debugging your system on our home user forums: https://help.nextcloud.com or, if you use Nextcloud in a large organization, ask our engineers on https://portal.nextcloud.com. See also  https://nextcloud.com/support for support options.
-
-Nextcloud is an open source project backed by Nextcloud GmbH. Most of our volunteers are home users and thus primarily care about issues that affect home users. Our paid engineers prioritize issues of our customers. If you are neither a home user nor a customer, consider paying somebody to fix your issue, do it yourself or become a customer.
-
-Please understand that at the moment, we are very busy with customer issues and some high priority development work. A lot of issues are getting reported. We can't always keep up and timely respond to all of them, but we try!
+This is the **issue tracker of Nextcloud**, please do NOT use this to get answers to your questions or get help for fixing your installation. You can find help debugging your system on our home user forums: https://help.nextcloud.com or, if you use Nextcloud in a large organization, ask our engineers on https://portal.nextcloud.com. See also  https://nextcloud.com/support for support options.
 
 Guidelines for submitting issues:
 
@@ -14,9 +10,9 @@ Guidelines for submitting issues:
     - You can also filter by appending e. g. "state:open" to the search string.
     - More info on search syntax within github: https://help.github.com/articles/searching-issues
     
-* Please fill in as much of the template below as possible. We know it is a pain sometimes, but especially without logs there is often not much we can do: really, if we would have seen the issue you encoutered before, we would already have fixed it. So we did NOT see it, and we will need YOUR help to find out what is wrong and fix it. The logs are absoutely crucial for that. Expect us to quickly close issues without logs or other information we need. If you don't have time to gather the required information, we don't either.
+* Please fill in as much of the template below as possible. The logs are absolutely crucial for the developers to be able to help you. Expect us to quickly close issues without logs or other information we need. 
 
-Please also note that we have a https://nextcloud.com/contribute/code-of-conduct/ that applies on Github. To summarize it: please, be kind. We try our best to be nice, too. If you can't be bothered to be polite, please just don't bother to report issues as we won't feel motivated to help you. Remember, we don't get paid to help you!
+* Also note that we have a https://nextcloud.com/contribute/code-of-conduct/ that applies on Github. To summarize it: be kind. We try our best to be nice, too. If you can't be bothered to be polite, please just don't bother to report issues as we won't feel motivated to help you. 
 -->
 
 <!--- Please keep the note below for others who read your bug report -->
@@ -33,9 +29,7 @@ Tell us what should happen
 
 ### Actual behaviour
 Tell us what happens instead
-<!--
-Did you try end-to-end encryption before version 3.0? Following the instructions from this post might solve your problem since you might need to clean up the keys as that can break the functioning of >3.0 if you had a malformed key: https://help.nextcloud.com/t/help-test-the-latest-version-of-e2ee/87590
--->
+
 
 ### Steps to reproduce
 1.
@@ -47,7 +41,6 @@ Client version:
 <!---
 Please try to only report a bug if it happens with the latest version
 The latest version can be seen by checking https://nextcloud.com/install/#install-clients
-In the case of end-to-end encryption bug reports the client must be at least 3.0 and the server at least 19 with the end to end encryption app version at least 1.5.2.
 --->
 
 Operating system:
@@ -70,15 +63,15 @@ Nextcloud version:
 Storage backend (external storage):
 
 ### Logs
+<!-- desktop client logs are a hard requirement for bug reports because we don't know how to do magic here :) -->
 
 Please use Gist (https://gist.github.com/) or a similar code paster for longer
 logs.
 
 1. Client logfile: 
-<!-- desktop client logs are a hard requirement for bug reports because we don't know how to do magic here :) -->
-Output of `nextcloud --logdebug --logwindow` or `nextcloud --logdebug --logfile log.txt`
-(On Windows using `cmd.exe`, you might need to first `cd` into the Nextcloud directory)
-(See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)
+Since 3.1: Under the "General" settings, you can click on "Create Debug Archive ..." to pick the location of where the desktop client will export the logs and the database to a zip file.
+On previous releases: Via the command line: `nextcloud --logdebug --logwindow` or `nextcloud --logdebug --logfile log.txt`
+(See also https://docs.nextcloud.com/desktop/3.0/troubleshooting.html#log-files)
 
 2. Web server error log: