2024-05-30 Triaging module meeting

[lichtwerk]

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

Links

• Video call google meet for now, we can try jitsi as well if people prefer
• #module-triaging chat channel
• live meeting notes

Attendees

• @Alaska
• @ThomasDinges
• @modmoderVAAAA
• @lichtwerk

Topics

• followups from last meeting

  • improve upon issues with unavailable hardware
    • Admins have been pinged about possible funding renting servers:
      • For Windows ARM, we do have a machine here that could be sent to someone in the triaging team.
      • NVIDIA/NVLink: could ask Patrick Mours
      • Let admins know if we need a specific hardware setup, in some cases it’s easy to ask nvidia, amd, intel or apple
      • Generally: would expect a specific list of CPU/GPUs that are difficult to test now, and then we figure out what is even available for that
    • Anthony-Roberts has repeatedly offered me remote access to his work station
  • feedback regarding our triaging infrastructure
    • #122166 - Adjust "Report a bug" wording on Gitea issue template - blender - Blender Projects “Adjust “Report a bug” wording on Gitea issue template” has been merged
    • #122191 - WIP: Add a script to collect system information when Blender isn't opening - blender - Blender Projects “WIP: Add a script to collect system information when Blender isn’t opening” is in review
    • #122462 - WIP: Update bug report template version info - blender - Blender Projects “WIP: Update bug report template version info” is in review
    • FYI Alaska/blender-activity-subscriber: A python script to automatically subscribe a user to the tasks they're interested in. - blender-activity-subscriber - Blender Projects
    • Admins have been pinged about age restricted content (legal concerns):
      • new bug reporting form would already communicate our guidelines
      • wrt. legal concerns, it’s fine if we remove it when we encounter it, and nothing more needs to be done for the time being
    • ongoing work for the wizard, see #78 - Triaging Wizard - blender-projects-platform - Blender Projects
    • remaining design issues discussed in #121260 - Issue template design discussion - blender - Blender Projects
    • PR Add guides on how to manually collect bug report system information is in review
  • Admins have been pinged about the timeline to drop Cycles AMD Metal support:
    • Probably for Blender 4.3, but not officially announced yet. We’ll still try to fix performance issues for 4.2 LTS.
  • Proposal to add more labels : draft for devtalk thread , feedback ?
  • Discussion how to handle floating point precision issues #60 - Bug Reports: Floating point precision bug handling - blender-developer-docs - Blender Projects
  • other news?

• recent important issues that are somehow hard to triage

  • if time permits, go over specific issues

Meeting Notes

• Quality Project

  • If there is a field that frequently recieves bug reports that triagers know about, we should let modules know about these to help give a pointer on where to focus in the Quality Project.
  • More information about what information the triaging module can provide will be gathered in a meeting tomorrow.

• Followups from last meeting

  • Improve upon issues with unavailable hardware
    • Admins would prefer we contact hardware manufacturers to get access to specific hardware.
    • Triaging module should create a list of hardware specific issues we can’t reproduce to assist with these requests for hardware.
  • Feedback regarding our triaging infrastructure
    • Alaska will continue working on their pull requests to improve the tools and information surrounding bug reporting. Others will review it when they have the time.
    • Bart (devops) might be the person to reach out to wrt. gitea custom dev (maybe invite him to next meeting?)
  • Proposal to add labels
    • Before progressing, we need feedback from developers.
      • TODO: Review draft for devtalk thread and turn it into a devtalk thread to start recieving feedback.
    • Adding more labels could make the label system harder to navigate.
      • We could request adjustments to the Gitea UI to improve this (E.g. Grouping labels together in sub-menus in the label picking UI).
  • Discussion how to handle floating point precision issues #60 - Bug Reports: Floating point precision bug handling - blender-developer-docs - Blender Projects
    • Iliya will re-work their pull request to better incorporate the opinions of different modules/developers.

Following meeting

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