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-05-08T11: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
"Pending TODOs/followups (wont get an active topic if no news have to be announced)"
- Open PR list growing, can Triagers help in that?
- Usage of LLMs
- please review this doc so we can justify the project to HQ planning
- is the setup at the HQ up and running as expected?
- 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
Meeting Notes
- TODOs/followups
- LLM for triaging
- We went over our planning document, clearing up the last bits of uncertainty to prepare to actually present it to people at HQ.
- After that we had some more general chats about LLM use, both inside triaging with this initiative, and with people using LLMs for coding, and potentially LLMs for patches to Blender.
- Within the triaging initiative context, we haven’t used LLMs much yet. But with everything setup now, we will continue to explore it’s usage.
- With regard to using LLM for coding, we talked about: Do triaging members use LLMs for programming? Have we seen community members use LLMs for programming?
- At the moment triaging’s usage of LLMs for programming has been limited to personal projects, or as “quick reminders” of how to do some stuff.
- We have seen some community members use LLMs for programmings, including for Blender extensions. It’s quite impressive how much it can do, but at the same time it’s still a bit messy.
- As for LLMs for patches to Blender, Triaging’s general stance is we need to be careful about that. We don’t want to end up in a situation where someone without programming knowledge, but uses a LLM, becomes the primary maintainer for a feature.
- Open pull request numbers are quite high (1000+)
- Pratik has currently been going over older pull requests, assigning reviewers or poking contributors to get the current status or get them going.
- Could more members of the triaging module help out with this?
- LLM for triaging
Following meeting
The following meeting will be on 2025-06-05T11:00:00Z. Again it will be open for everybody who’s interested.