Streamline issue reporting

[forthrin]

Expected behavior of the wanted feature

The issue templates have grown very wordy (surely after many "Haz no workz" reports and annoyed developers).

Sadly, this befalls everyone alike with the opposite effect, causing trudged reports and annoyed reporters.

If there is interest in improving this, a proposal for such has been developed and can be presented here.

1. It is (currently) written as a shell script
2. It automates many steps of the process
3. It is interactive and can make decisions from input and environment
4. It will integrate with and hugely simplify the online tracker issue
5. It requires from mpv at most an option to call the script

Alternative behavior of the wanted feature

A) Simplify current issue template (loses the automation)
B) Convert script to Lua (if consistency is paramount)

Log File

No response

Sample Files

No response

[Akemi]

so a variation of your previous request #13968.

[forthrin]

Yes, but with a pondered and quite well working sketch this time.

[N-R-K]

I don't think "open a bug from the cli" is a good thing to be encouraging. But some of the things that the bug template asks for can be tedious to fill out while being easy to automate. Something like mpv --system-info which will output all the relavant stuff that can be copy pasted into the bug report would be a good thing.

[kasper93]

Something like mpv --system-info which will output all the relavant stuff that can be copy pasted into the bug report would be a good thing.

We could just add those things to log. Some things are already printed, like Mesa version, unless it completely doesn't work, in which case, probably the version is not that relevant.

[N-R-K]

We could just add those things to log.

That also works. Downside would be needing to open log to view these compared to now where you can see it in the issue directly. If it's enough of a issue then it can also just be solved with some CI runner that takes the system info from the attached log and comments/edits it into the thread.

The main point is to removing having to manually fill up most of these which can be easily automated:

mpv/.github/ISSUE_TEMPLATE/2_bug_report_linux.yml

Lines 32 to 41 in 09900a0

	Provide following information if applicable.
	- Linux Version: `cat /etc/os-release | grep "NAME"`
	- Kernel Version: `uname -a`
	- GPU Model: `lspci -nn | grep VGA` or `lshw -C display -numeric`
	- Mesa/GPU Driver Version: `glxinfo -B | grep "OpenGL version string"` or `vulkaninfo | grep driverInfo`
	- Window Manager and Version
	- Source of the mpv binary
	- Latest version of mpv you know without the problem
	- The time when the problem started to happen (after updating mpv, system, driver, etc.)
	- Possible screenshot or video of visual glitches

Whether it's done by adding them to the log or by some separate --system-info flag isn't all that relavant. Either way is just a means to an end.

[forthrin]

I'm reading out of his a very understandable desire for BLUF. If there is actual interest and traction for this now, the preliminary script will be posted here so people can test it, and give feedback on its structure and focus, hopefully to end up with something optimal for both reporters and users.