Added note to not ask for GUI changes

[jakjakob]

Maybe it prevents all the (useless) issues asking for a new/bloated GUI.
(added a line in the future request template saying that the tool is meant to be be minimalistic and to not ask useless/big GUI features/changes)
Should I also add something into the readme?
Maybe a good project for the future is making a Q&A page, that also says that there aren't bi GUI changes in mind. If you think this is a good idea I could make it.

(btw love this tool, keep the good work up)

[Tokarak]

Funny that a "minimalist" app needs 85mb...

[actuallymentor]

Hey @jakjakob!

My apologies for responding so late. The tragedy of open source side projects is that I only check in periodically.

Your PR is very much appreciated. I have mixed feelings about merging it. One the one hand I am 100% on board with the sentiment. On the other hand, I want to leave the space for people to build on the project if they have the time for it.

A recent case study is the battery calibrate functionality. To my mind that doesn't need to be a feature, and those who really care should just script it. On the other hand, if people care enough to make the functionality themselves in a nonobtrusive way (like @KyrosWeb did in #169) then I have no problem merging it.

How would you feel about rephrasing it a bit to include something like "if you really care about a feature, be prepared to built it yourself, and check in beforehand whether it would be merged" or so?

Also, @Tokarak, you are completely unhelpful and needlessly snarky. The CLI is 17KB, and nobody who uses a GUI cares about 85mb of drive usage. If you want a smaller GUI, I genuinely hope you build it.