This is a page to (1) let me forget what needs to be done, (2) maybe find someone else to do this for me...

Human Resources

1. Announcement that it would be nice if someone helped us: https://invent.kde.org/tymond/dev-scripts/blob/master/Notes/user_support_annoucement_ideas.txt

Other Resources

1. Guide for reddit flairs - https://www.reddit.com/r/krita/comments/ctewwd/krita_subreddit_flair_guide/

2. Introduction to user support: manual page

3. Explanation how tablet drivers work (with pictures) - so that we can dodge all the accusations of Krita not being able to communicate with some cheap brands
   
   Link to the current explanation: https://docs.krita.org/en/user_manual/drawing_tablets.html
   
   What I expect, more or less: something along the lines of "It's not Krita's job to support tablets, it's tablets job to support standards" - https://www.reddit.com/r/krita/comments/c1drjb/cursor_freezes_when_i_try_to_draw/erciuhv/?utm_source=share&utm_medium=web2x
   • [Tiar] Finish writing of two "frequently asked questions" about tablets and make a merge request
   • Find a brilliant idea which, after writing and illustrating, will convince anyone that all the tablet bugs are because of XP Pen/Genius/MacOS/corporations/reptillians so we can stop being targeted by various individuals demanding their money back.

4. Crash log gathering guide: https://invent.kde.org/websites/docs-krita-org/merge_requests/92
   • Windows (right now it's hard to follow; instruction how to get the debug symbols is on the bottom of the page)
   • Linux -- https://community.kde.org/Guidelines_and_HOWTOs/Debugging
   • MacOS -- https://www.reddit.com/r/krita/comments/ck6alb/krita_crashes_when_saving/evlbr95?utm_source=share&utm_medium=web2x

5. Resetting configuration is difficult for non-technical users
   • • Better explain (with screenshots?) how to do it in FAQ or User Support page
     • Maybe it would be possible to make a program or something that would reset the configuration for the user? In the worst case, just "Open Resource Folder" equivalent just for configuration, so we can tell users "click here and here in Krita, it will open the folder; close Krita, it will reset the configuration". Keep in mind it would be nice to have something that would work even if Krita doesn't start...
   • Keep in mind there is a new button somewhere to reset configuration; add it to the FAQ

6. (in progress) (https://invent.kde.org/documentation/docs-krita-org/-/merge_requests/106) Explanation how different versions of Krita (stable, Krita Plus, Krita Next, alpha/beta/user testing releases... ) work and where to get debug symbols for them
   • how to install Krita Plus flatpaks: https://www.reddit.com/r/krita/comments/ctsfai/krita_plus_flatpak_builds/
   • Krita releases vs. Krita Plus vs. Krita Next vs. special testing versions
   • Portable versions for Windows!
   • dmg vs .zip vs setup.exe vs appimage vs from repository vs flatpak
   • Android!
   • Steam vs Store vs others
7. Write a guide "How to install ffmpeg on Windows" properly, with screenshots. Issues users have:
   • downloading the source code .tar.gz file (hence we need screenshots)
   • downloading the development version instead of a stable one (hence... again)
   • not knowing how to unzip it or that they should do it
   • not knowing how to provide a path to Krita

8. (in progress) Color Managment easy fix guide for less technical users - ask tiar/tymond for details how to help with images

9. Write a guide "How to use bugzilla even if it's ugly and so 95'"
   • must be structured: (1) for non-technical users, just reporting a bug, (2) for bug-triagers, (3) for developers (shortest section, must contain BUG:# mention)
   • at the beginning: big warning to not use bugzilla for issues (similar to what is on "Reporting a bug" page)
   • it should link to Reporting a bug and Bug triaging pages and not repeat the information (except for the warning, there is never enough warnings)
   • must contain: 'wishlist' importance (and to not use 'grave'; just 'wishlist', 'normal' and 'crash'); different states of bug reports (check out existing bugs to see which states are used) and the flow between them; that NEEDS INFO / WAITING FOR INFO will close itself in 1 month unless there is an interaction.
   • must contain this link: https://bugs.kde.org/enter_bug.cgi?product=krita in the section for users - it will find 'krita' as a product automatically. Maybe even three options: one for Windows, one for Mac users, one for Linux? This is something users struggle with, too.

10. (more for contribution, but it's my task (since no one else contributed yet), so I can write what I want) List of easy tasks from wishlist to do

11. Write a good guide about DPI vs pixel size vs real life size - it must contain good pictures

12. Better FAQ section in Krita (visually) - ask tiar/tymond for details

13. (---) List of coverage errors