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-04-17T11: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
- LLM for triaging
- please review this doc so we can justify the project to HQ planning
- LLM for triaging
"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
- 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 quickly went over the LLM document
- Probably best to put a “plan” section (at the end?), shifting the database to HQ, also generally stating we are in tryout phase… and also put a date there for re-evaluation of goals/status etc.
- Open question: how often do we (as Triaging) need to download new models and how is the current process of doing it (requires Arnd/Bart each time?)
- Are there other things we can do to reduce the impact on the people at the head quarters (Time needed to maintain the machine, and the network impact for people at the head quarters while downloading large models)?
- At the moment there are some issues with with the LLMs (Germano mentioned they can get confused about who they’re responding too).
- Their proposed solution was to fine tune the model. But could we explore some other ideas (Adjusting system prompts, adding more databases and more tools to the LLM, etc, to create “agents”) to see if we can resolve these issues without having to resort to finetuning?
- We quickly went over the LLM document
- We didn’t talk about other topics since the people incharge of them were away.
- LLM for triaging
Following meeting
The following meeting will be on 2025-05-08T11:00:00Z. Again it will be open for everybody who’s interested.