Improvements around LOGS, errors, crashes, reports

1. Want suggest to change philosophy with logs to collect the logs

• not in %TEMP%\blender\debug_logs or optional - Temp dir can be deleted and cleared by disc optimizations process then after bug report in next step hard to add right file
• but in \blender_dir\logs\debug_logs as optional in this same place where is blender
• alternative \blender_project\logs\debug_logs as optional to better see whats happen under project

devtalk.blender.org/t/how-to-report-complex-production-bugs/19998/3

2. The second issue around logs is that can be overwrite by different versions of blender , also proposal it to save it with timestamp , eg.

• \blender_\blender_debug_output_202108130001
• \blender_\blender_system_info_202108130002

3. With this idea work with logs can going more around addons, to log needs data in this dirs

• \blender_project\logs\addons\
• \blender_project\logs\addons\addon_name\log_blender_system_info_202108130103
• \blender_dir\logs\addons\addon_name\log_blender_system_info_202108130104

4. In case blender have Spreadsheet the logs can be read in this as some feature, logs can be more like tables with comma like .csv files but .txt

• I'm not sure about logs in Python console as alerts, etc. (should be write in operation logs as system logs - coz sometime easy to omit some issues) maybe: log_blender_system_log
• \blender_dir\logs\debug_logs\system\log_blender_system_log_202108130116
• after crash or something (hanged, especially by Script) alerts, warning disappear

5. Crashed file should be protected before changes to add for issue/bug report (eg. as file .blend_crashed) with special icon ( Icon for .blend1 and fiter for extensions in file manager )

6. The logs can be deleted from blender

7. Sometimes we want be sure about blender version with working now, especially if using more around testing problems.

• for this we can't click "Report a bug" that opening whole system on web with information

• we need simple popup window like in VSC with selectable fields, ang good if can be printed this info with revision version in Script workspace or by some button (or as in other feature request, where can be Script collections explorer window [like: Scenes, View Layers, etc.] - then dir for logs for scripts is important and needed, eg.

• now exist many blender versions like UPBGE-EEVEE, K-Cycles, E-Cycles, Cycles-X (it be good to well identify this aps, on some other boards around blenders community I see tests this all and misunderstandings about some details)

• \blender_project\logs\scripts\script_name\log_blender_system_info_202108130105

• \blender_dir\logs\scripts\script_name\log_blender_system_info_202108130106

• other script results as computed data in .csv can be saved there or assets (eg. AI/ML) [hvr it's time to organize this type problems IMHO]

8. Data format for logs, eg. (% %..etc.)

_202108130106 _2021-08-13_01-06

9. Anonymization the private information paths (place where is blender), usernames - due work, companies hardware, etc. before add logs to developer.blender.org I must modify the data, coz including private (eg. project name, dirs, etc.) - this limiting time to spent time around prepare this without problems

• I think it's not so big problem to turn option for Anonymization to save .txt files without possible sensitive informations

10. Include upper features inside Python API, eg. managment for logs for add-on's, scripts.

11. Feature request as Report bug can be ok to linking to RCS, to cut feature from bug in developer.blender.org

• the info about blender version and revision can be useful with info that user using old version when in new something is implemented (I hope can be implemented in RCS option to handle info about version/revision like for bug)

blender.stackexchange.com/questions/145223/where-does-blender-store-log-information docs.blender.org/manual/en/dev/troubleshooting/crash.html