2024-10-04 Triaging module meeting

Meetings
1

Triaging Module Meeting

Biweekly Triaging module meeting for planning and coordination.
Folks on the payroll should attend if possible, others are invited as well.
In these meetings, we can keep us up-to-date on everything triaging, discuss recent important issues and see if we can bring the module forward.
I believe it is also good to see human faces once in a while :), so there is always room for some personal stuff if appropriate.

The meeting will be on 2024-10-04T12:00:00Z. It is open for everybody interested to join the video call (link below).

Links

Attendees

  • Philipp
  • Pratik
  • Richard
  • Alaska

Topics

  • Announcements

  • Pending TODOs/followups (wont get an active topic if no news have to be announced)

    • Ideas for ways to include “Bug Fixes” from older releases in the release notes
    • Feedback regarding our triaging infrastructure
      • 126039 is still open. We may want to make adjustments (add more links?) depending on how Alaska’s documentation of the script turns out.
    • Wizard
    • It was brought up that there have been recent reports of failing physics involving dependency cycles, typically related to this dependency cycle change.
    • Simple debugging tools
      • Philipp has Addon with wrapped mesh validation, wrapped user_map (both accessible for all meshes/IDs or in the Outliner based on selection) and batch opening blend files in multiple blender versions, still need to put up on gitea
      • there is also Core Debug Tools — Blender Extensions
    • Could we add a feature that lets users know the location of crash logs after Blender crashes so they can more easily provide it in a bug report?

Meeting Notes

  • Suggestion (by Nika Kutsniashvili) to add more “Good First Issue” labels to confirmed issues if appropriate to attract new developers.

    • We discussed what type of report gets the “Good First Issue” label
      • Philipp suggested that if there are simple issues that are easy to fix, we could leave small notes about what’s causing it to help a new developer figure out the issue and get into Blender’s source code.

  • Pending TODOs/followups

    • Simple debugging tools
      • Philipp has created their addon and will upload it to their Gitea repo soon.
      • Jacque’s Core Debug Tools addon can also be useful, but it can provide “too much information” some times. We will ask if it’s possible to limit the information shown to just the objects/IDs we’re interested in.
    • Triaging Wizard
      • Richard has started writing up their idea of the triaging wizard.
        • Add restrictions to certain fields (Don’t allow users to delete certain details, force users to add certain details, limit formatting or length of certain inputs)
        • Provide popups/tooltips to notify people of useful information. E.g. If they’re writing in the system information manually, then notify them that this can be automatically filled out with Help -> Report a bug
      • It was suggested that Richard approach Bart (Devops) once the design is more polished to see what can be done with them.
      • Richard will check on our previous tasks on this subject blender/blender#121260 and infrastructure/blender-projects-platform#78 for more information.
    • Could we add a feature that lets users know the location of crash logs after Blender crashes?
      • Alaska will ask in the Blender coders chat to see if we can get information on that.
      • Could the feature be a menu item in Blender? (E.g. Help -> Show Logs). This can probably be it’s own separate feature.

Following meeting

The following meeting will be on 2024-10-17T11:00:00Z. Again it will be open for everybody who’s interested.

6 Likes