2024-10-17 Triaging module meeting

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-17T11:00:00Z. It is open for everybody interested to join the video call (link below).

Links

Attendees

Topics

  • Announcements

    • request by @pragma37 to handle issues in the NPR branch on the bugtracker. No “real” triaging involved, just adding a (to-be-added) “NPR-Prototype” label and CCing @pragma37 in the issue, done.
    • Philipp on holiday the comming two weeks
  • 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
    • Simple debugging tools
    • 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?
      • 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.

Meeting Notes

  • NPR branch: ask Miguel if he could use the tracker on their repo (pragma37/blender: The official Blender project repository. - blender - Blender Projects). The “Help > Report a Bug” operator could also be tweaked to point to the repo. If that has objections for some reason, we could use the official tracker.

  • Discuss posting the list of “Needs Info from User” on a weekly basis in the chat. (From this script: .profile/collect_old_needs_info_reports.py at main - .profile - Blender Projects)

    • Posting the list directly to chat doesn’t seem particularly useful, as this information can be become outdated very quickly.
    • Instead maybe just post the number of issues that need attention once a week or fortnight. Currently accepted proposal.
  • TODOs/followups

    • Ideas for ways to include “Bug Fixes” from older releases in the release notes
      • Philipp is away during 4.3’s release. So we probably won’t do that for this release.
    • Simple debugging tools
    • Could we add a feature that lets users know the location of crash logs after Blender crashes?
    • Wizard
      • Richard experimented with a design and didn’t fully like what they created.
        • Even though it may not be up to their liking, it’s useful to know what’s not useful for future iterations/designs.
      • Richard’s experiment was with adding popups to help users figure out what information they need to input into the relevant fields.
        • Their main concern was that the popups weren’t in a great spot.
        • Their code is fragile to changes in Gitea (And Gitea does change a bit with each release)
        • To proceed Richard will share their concept on Triaging Wizard task for future discussion.

Following meeting

The following meeting will be on 2024-11-07T12:00:00Z. Again it will be open for everybody who’s interested.

7 Likes