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 2025-03-20T12: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 matrix chat room on chat.blender.org
- #module-triaging matrix chat room link for other matrix clients
- live meeting notes
Attendees
Topics
- Announcements
- 4.4 is out, do we have bad regressions?
"Pending TODOs/followups (wont get an active topic if no news have to be announced)"
- talk about Proposal - Label Changes
- Alaska has made a tool to automatically notify people of old
Needs information from userreports: Issues - needs-information-reports - Blender Projects - Feedback regarding our triaging infrastructure
- We use a script to help write our weekly reports. There have been a few issues with it’s output recently (E.g. Duplicate data, missing data from PRs merged by others)
- Yimming was planning to look into this
- We use a script to help write our weekly reports. There have been a few issues with it’s output recently (E.g. Duplicate data, missing data from PRs merged by others)
- Wizard
- Gather a list of two or three examples from “out there” that work similar to what we want to achieve (add that to #78 - Gitea: Triaging Wizard - blender-projects-platform - Blender Projects) is still pending, some more discussion in #121260 - Issue template design discussion - blender - Blender Projects though regarding Richards experiments
- 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?
- There has been progress on the crash window pull request
- Discussion about exposing dependency cycles to the end user (an idea we have discussed in previous meetings)
- Discussion about Tests:
- reply in devtalk
- Usage of LLMs
Meeting Notes
-
Announcements
- 4.4 is out, do we have bad regressions?
- There appears to be some issues with Cycles HIP. It is currently being investigated.
- Startup crashes #132968 - ERROR (gpu.shader): gpu_shader_2D_widget_base FragShader - blender - Blender Projects
- 4.4 is out, do we have bad regressions?
-
TODOs/followups
- Usage of LLMs
- Germano has been working on this.
- They have been exploring the process of fine tuning smaller LLM models for some of their triaging extensions.
- It’s still just in the experimentation stage. So there’s no clear consensus on if it’s working out or not.
- 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?
- Development is currently on hold due to a issue that Germano and LazyDodo are unsure how to reproduce and resolve.
- #129974 - Windows: Show popup after crash - blender - Blender Projects
- poke Ray about this again
- talk about Proposal - Label Changes
- Since Thomas was at the meeting, we asked them for input. All current notes are just intial thoughts. Opinions can change.
- If a module believes new labels would be useful to them, then they don’t see a downside to adding it. For example if the Cycles module wants a
Interest|HIPlabel, then it can be added. - However if there’s a label that should be used by everyone, then it should be coordinated with modules first before additions are made.
- But ideally things should be kept as simple as possible (as few labels as possible).
- If a module believes new labels would be useful to them, then they don’t see a downside to adding it. For example if the Cycles module wants a
- Since Thomas was at the meeting, we asked them for input. All current notes are just intial thoughts. Opinions can change.
- Usage of LLMs
Following meeting
The following meeting will be on 2025-04-03T11:00:00Z. Again it will be open for everybody who’s interested.