Adding upstream version 0.38.0.upstream/0.38.0upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

7 files changed, 68 insertions, 59 deletions

diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md b/.github/ISSUE_TEMPLATE/2_bug_report_linux.md
index 6faaf85..e8e30d1 100644
--- a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md
+++ b/.github/ISSUE_TEMPLATE/2_bug_report_linux.md
@@ -15,7 +15,7 @@ Provide following Information:
 - Source of the mpv binary
 - If known which version of mpv introduced the problem
 - Window Manager and version
-- GPU driver and version
+- GPU model, driver and version
 - Possible screenshot or video of visual glitches
 
 If you're not using git master or the latest release, update.
@@ -26,6 +26,10 @@ Releases are listed here: https://github.com/mpv-player/mpv/releases
 Try to reproduce your issue with --no-config first. If it isn't reproducible
 with --no-config try to first find out which option or script causes your issue.
 
+If the issue is performance-related, try to reproduce it with --no-config
+--profile=fast, which is designed to work on lower-end mobile devices.
+Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
+
 Describe the reproduction steps as precise as possible. It's very likely that
 the bug you experience wasn't reproduced by the developer because the workflow
 differs from your own.
@@ -36,14 +40,16 @@ differs from your own.
 
 ### Log file
 
-Make a log file made with -v -v or --log-file=output.txt, paste it to
-https://0x0.st/ or attach it to the github issue, and replace this text with a
-link to it.
+Make a log file made with -v -v or --log-file=output.txt, attach it to
+the issue, and replace this text with a link to it.
+
+Without the log file, this issue will be closed for ignoring the issue template.
 
-The issue will be closed for ignoring the issue template.
+In the case of a crash, please provide a backtrace.
 
 ### Sample files
 
-Sample files needed to reproduce this issue can be uploaded to https://0x0.st/
-or similar sites. (Only needed if the issue cannot be reproduced without it.)
+Sample files needed to reproduce this issue can be attached to the issue
+(preferred), or be uploaded to https://0x0.st/ or similar sites.
+(Only needed if the issue cannot be reproduced without it.)
 Do not use garbage like "cloud storage", especially not Google Drive.
diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_macos.md b/.github/ISSUE_TEMPLATE/2_bug_report_macos.md
index 809ea39..470b4a0 100644
--- a/.github/ISSUE_TEMPLATE/2_bug_report_macos.md
+++ b/.github/ISSUE_TEMPLATE/2_bug_report_macos.md
@@ -24,6 +24,10 @@ Releases are listed here: https://github.com/mpv-player/mpv/releases
 Try to reproduce your issue with --no-config first. If it isn't reproducible
 with --no-config try to first find out which option or script causes your issue.
 
+If the issue is performance-related, try to reproduce it with --no-config
+--profile=fast, which is designed to work on lower-end mobile devices.
+Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
+
 Describe the reproduction steps as precise as possible. It's very likely that
 the bug you experience wasn't reproduced by the developer because the workflow
 differs from your own.
@@ -34,18 +38,20 @@ differs from your own.
 
 ### Log file
 
-Make a log file made with -v -v or --log-file=output.txt. If you use the Bundle
-from a version later than 0.32 a default log is created for your last run at
-~/Library/Logs/mpv.log. You can jump to that file via the Help > Show log File…
-menu. Paste the log to https://0x0.st/ or attach it to the github issue, and
-replace this text with a link to it.
+Make a log file made with -v -v or --log-file=output.txt, attach it to
+the issue, and replace this text with a link to it.
+
+If you use the Bundle, a default log is created for your last run at
+~/Library/Logs/mpv.log. You can jump to that file via the
+Help > Show log File… menu.
 
-In the case of a crash please provide the macOS Crash Report (Backtrace).
+Without the log file, this issue will be closed for ignoring the issue template.
 
-The issue will be closed for ignoring the issue template.
+In the case of a crash, please provide the macOS Crash Report (Backtrace).
 
 ### Sample files
 
-Sample files needed to reproduce this issue can be uploaded to https://0x0.st/
-or similar sites. (Only needed if the issue cannot be reproduced without it.)
+Sample files needed to reproduce this issue can be attached to the issue
+(preferred), or be uploaded to https://0x0.st/ or similar sites.
+(Only needed if the issue cannot be reproduced without it.)
 Do not use garbage like "cloud storage", especially not Google Drive.
diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_windows.md b/.github/ISSUE_TEMPLATE/2_bug_report_windows.md
index b42c385..d936593 100644
--- a/.github/ISSUE_TEMPLATE/2_bug_report_windows.md
+++ b/.github/ISSUE_TEMPLATE/2_bug_report_windows.md
@@ -14,6 +14,7 @@ Provide following Information:
 - Windows Version
 - Source of the mpv binary
 - If known which version of mpv introduced the problem
+- GPU model, driver and version
 - Possible screenshot or video of visual glitches
 
 If you're not using git master or the latest release, update.
@@ -24,6 +25,10 @@ Releases are listed here: https://github.com/mpv-player/mpv/releases
 Try to reproduce your issue with --no-config first. If it isn't reproducible
 with --no-config try to first find out which option or script causes your issue.
 
+If the issue is performance-related, try to reproduce it with --no-config
+--profile=fast, which is designed to work on lower-end mobile devices.
+Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
+
 Describe the reproduction steps as precise as possible. It's very likely that
 the bug you experience wasn't reproduced by the developer because the workflow
 differs from your own.
@@ -34,14 +39,16 @@ differs from your own.
 
 ### Log file
 
-Make a log file made with -v -v or --log-file=output.txt, paste it to
-https://0x0.st/ or attach it to the github issue, and replace this text with a
-link to it.
+Make a log file made with -v -v or --log-file=output.txt, attach it to
+the issue, and replace this text with a link to it.
+
+Without the log file, this issue will be closed for ignoring the issue template.
 
-The issue will be closed for ignoring the issue template.
+In the case of a crash, please provide a backtrace.
 
 ### Sample files
 
-Sample files needed to reproduce this issue can be uploaded to https://0x0.st/
-or similar sites. (Only needed if the issue cannot be reproduced without it.)
+Sample files needed to reproduce this issue can be attached to the issue
+(preferred), or be uploaded to https://0x0.st/ or similar sites.
+(Only needed if the issue cannot be reproduced without it.)
 Do not use garbage like "cloud storage", especially not Google Drive.
diff --git a/.github/ISSUE_TEMPLATE/3_bug_report.md b/.github/ISSUE_TEMPLATE/3_bug_report.md
index 60df58d..e33a003 100644
--- a/.github/ISSUE_TEMPLATE/3_bug_report.md
+++ b/.github/ISSUE_TEMPLATE/3_bug_report.md
@@ -13,6 +13,9 @@ Provide following Information:
 - mpv version
 - Platform and Version
 - Source of the mpv binary
+- If known which version of mpv introduced the problem
+- GPU model, driver and version
+- Possible screenshot or video of visual glitches
 
 If you're not using git master or the latest release, update.
 Releases are listed here: https://github.com/mpv-player/mpv/releases
@@ -22,6 +25,10 @@ Releases are listed here: https://github.com/mpv-player/mpv/releases
 Try to reproduce your issue with --no-config first. If it isn't reproducible
 with --no-config try to first find out which option or script causes your issue.
 
+If the issue is performance-related, try to reproduce it with --no-config
+--profile=fast, which is designed to work on lower-end mobile devices.
+Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
+
 Describe the reproduction steps as precise as possible. It's very likely that
 the bug you experience wasn't reproduced by the developer because the workflow
 differs from your own.
@@ -32,12 +39,16 @@ differs from your own.
 
 ### Log file
 
-Make a log file made with -v -v or --log-file=output.txt, paste it to
-https://0x0.st/ or attach it to the github issue, and replace this text with a
-link to it.
+Make a log file made with -v -v or --log-file=output.txt, attach it to
+the issue, and replace this text with a link to it.
+
+Without the log file, this issue will be closed for ignoring the issue template.
+
+In the case of a crash, please provide a backtrace.
 
 ### Sample files
 
-Sample files needed to reproduce this issue can be uploaded to https://0x0.st/
-or similar sites. (Only needed if the issue cannot be reproduced without it.)
+Sample files needed to reproduce this issue can be attached to the issue
+(preferred), or be uploaded to https://0x0.st/ or similar sites.
+(Only needed if the issue cannot be reproduced without it.)
 Do not use garbage like "cloud storage", especially not Google Drive.
diff --git a/.github/ISSUE_TEMPLATE/4_bug_report_build.md b/.github/ISSUE_TEMPLATE/4_bug_report_build.md
index e8697f0..8370a30 100644
--- a/.github/ISSUE_TEMPLATE/4_bug_report_build.md
+++ b/.github/ISSUE_TEMPLATE/4_bug_report_build.md
@@ -7,7 +7,12 @@ assignees: ''
 
 ---
 
-### mpv version and platform versions
+### Important Information
+
+Provide following Information:
+- mpv version
+- Platform and Version
+- meson version
 
 If you're not using git master or the latest release, update.
 Releases are listed here: https://github.com/mpv-player/mpv/releases
@@ -24,7 +29,7 @@ differs from your own.
 
 ### Log file
 
-Upload meson-logs/meson-log.txt or meson setup build output to https://0x0.st/ or attach
-it to the github issue, and replace this text with a link to it.
+Attach meson-logs/meson-log.txt or meson setup build output to the issue,
+and replace this text with a link to it.
 
-The issue will be closed for ignoring the issue template.
+Without the log file, this issue will be closed for ignoring the issue template.
diff --git a/.github/ISSUE_TEMPLATE/5_feature_request.md b/.github/ISSUE_TEMPLATE/5_feature_request.md
index 2fba2ba..a280622 100644
--- a/.github/ISSUE_TEMPLATE/5_feature_request.md
+++ b/.github/ISSUE_TEMPLATE/5_feature_request.md
@@ -17,6 +17,5 @@ https://github.com/mpv-player/mpv/labels/meta%3Afeature-request
 ### Log file
 
 Even if you think it's not necessary at first, it might help us later to find
-possible issues. Make a log file made with -v -v or --log-file=output.txt, paste
-it to https://0x0.st/ or attach it to the github issue, and replace this text
-with a link to it.
+possible issues. Make a log file made with -v -v or --log-file=output.txt,
+attach it to the issue, and replace this text with a link to it.
diff --git a/.github/ISSUE_TEMPLATE/6_question.md b/.github/ISSUE_TEMPLATE/6_question.md
deleted file mode 100644
index b6131f3..0000000
--- a/.github/ISSUE_TEMPLATE/6_question.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-name: 'Ask a Question'
-about: 'Ask a question about mpv'
-title: ''
-labels: 'meta:question'
-assignees: ''
-
----
-
-Don't ask questions about issues, errors or problems you have and instead open
-a proper issue with the right template from the previous selection.
-
-This template is meant for questions about the workings of mpv, to clarify about
-unspecified behaviour of options or command, or anything else that is not well
-described and needs clarification.
-
-Before asking a question make sure it hasn't been asked or answered yet.
-https://github.com/mpv-player/mpv/labels/meta%3Aquestion
-
-### Log file
-
-Even if you think it's not necessary at first, it might help us later to find
-possible issues. Make a log file made with -v -v or --log-file=output.txt, paste
-it to https://0x0.st/ or attach it to the github issue, and replace this text
-with a link to it.