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

Links

Attendees

  • TBA

Topics

  • followups from last meeting

    • improve upon issues with unavailable hardware
      • news?
    • feedback regarding our triaging infrastructure
    • other news?
    • generally: would be good to move some discussion out of the meeting and into Design/Todo issues in gitea (to keep the meetings shorter and have places for followups other than the meeting itself)

  • recent important issues that are somehow hard to triage

    • if time permits, go over specific issues

Meeting Notes

  • Many EEVEE to EEVEE Next regressions have been set to high priority to try and get as many as possible fixed before switching to EEVEE Next as default.
  • Some reports containing adult/explicit content have started to appear.
    • Our goal is to minimize this type of content on the bug reporting platform by asking for simplified files avoiding the explicit content if possible.
    • Phillip will update the various bug reporting information pages (Making good bug reports, Triaging playbook, etc) with guidelines for this type of content.
    • Phillip will also check with the admins about this and their opinions.
  • followups from last meeting
    • Improve upon issues with unavailable hardware
      • Sergey will ask at the next admin meeting for opinions about when to remove AMD GPU Metal Cycles support.
      • There are a few bug reports for 3D mouse issues, but we don’t have much hardware for testing this.
      • Alaska investigated what hardware we could rent from cloud service providers for bug testing.
        • The main devices we could gain access too are NVLinked NVIDIA GPUs, server architecture NVIDIA GPUs, and WoA (Windows on ARM) CPUs for when Blender gets official WoA support. There are other devices avaliable, but most aren’t supported by Blender/Cycles, or we have similar hardware already.
        • Some testing on rented servers can be a bit limited by what the cloud service provider offers (mostly Linux CLI with limited Windows and limited to no GUI support).
        • Philipp will ask about the potential for funding for this.
      • We may need to get a Qualcomm equipped WoA computer in the future to test Qualcomm GPU drivers.
    • feedback regarding our triaging infrastructure
      • issues from previous meeting have been reported in #12 - Issues and triaging features - blender-projects-platform - Blender Projects
      • Author filter (e.g. in Issues is case-sensitive – unlike mentions with “@”)
      • Unable to add certain users as reviewers (think this is a group membership issue, Philipp needs to double-check)
      • Unable to assign non-devs to issues (e.g. on Good First Issues)
      • Unable to remove reviewers from PRs (which group membership is required?)
    • We plan to make more TODO/Design tasks to keep a track of topics from the meeting and to encourage discussion out of the meeting.
    • Triaging Wizard
      • As an intermediate step there is the proposal to update the Gitea issue template to hopefully get better bug reports.
        • We are still sorting out some of the details for this (Are the limitations too large? Are some of the features being added in future Gitea versions enough to deal with these limitations and should we wait for them?)
        • Alaska will create a document to help explain the features and to get opinions on them.
    • Developing Issues: There is no direct answer on the question if we should close/redirect such issues direct in the chat to related module/developers or keep such report as it is on the tracker and handle with bug-fix PR’s and related process (for example, backport).
      • in case of static analysis of the code, issues can be in really old part of blender or external parts without active maintainer.
      • Some such reports can be completely unrelated with final users due to the fact that they are related with unused code (if this is related with new features from fork’s) or be invisible (like UB or CLI).
  • recent important issues that are somehow hard to triage
    • meeting went over a couple of issues that have been sitting in the queue for quite some time
      • there is potential to still make progress on them, goal is to get at least the ones brought up in the meeting out of the “Needs Triage” status

Following meeting

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

5 Likes