2024-11-07 Triaging module meeting

[lichtwerk]

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-11-07T12: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

• @lichtwerk
• @mano-wii
• @PratikPB2125
• @ChengduLittleA
• @Alaska

Topics

• Announcements

  • Philipp suggests to have meetings consistently every two weeks (no matter his own availability), discuss how to organize things

• Pending TODOs/followups (wont get an active topic if no news have to be announced)

  • Ideas for ways to include “Bug Fixes” from older releases in the release notes
  • NPR branch: Miguel went with the option of using the branch repo tracker
  • Posting the number of “Needs Info from User” issues on a weekly basis in the chat
    • Alaska posted this now (You're invited to talk on Matrix)
  • Feedback regarding our triaging infrastructure
    • 126039 is still open. We may want to make adjustments (add more links?) depending on how Alaska’s documentation of the script turns out.
  • 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?
    • Design task in #128621 - Design for popup after crash - blender - Blender Projects, needs further input

Meeting Notes

• Have meetings consistently every two weeks (no matter Philipps availability), no conclusion on how to organize this yet

• TODOs/followups

  • 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?
    • Design task in #128621 - Design for popup after crash - blender - Blender Projects
    • @mano-wii created a working prototype. They are encouraged to create a pull request we can provide feedback on.
  • @mano-wii has tuned a large language model based on triager replys to help create a web browser extension to assist triaging.
    • It currently uses OpenAI services and thus has a API cost (Roughly $2 per month).
    • It would be ideal if we could tune a free, open source model that triagers, or the Blender foundation could run locally.
  • @mano-wii also showed off a few web browser extensions that are useful for the triaging team. They can be found on their Chrome and Firefox extensions page. (Note: Chrome is their main focus and the Firefox alternatives may be missing features)

Following meeting

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

[Anthony_Gibbs]

@lichtwerk

has tuned a large language model based on triager replys to help create a web browser extension to assist triaging.

Well that’s interesting. Not so much from a triage point of view, but the fact such a thing has been done.

What I would love is also a LLM, that one could download and run locally, that is tuned for the Blender Python API. It’s easy enough to find and download a coding LLM that one can write a sentence or two and how it spit out the python code to run in Blender.
The biggest problem is that they are all general coding LLM’s (so bloated with training for a range of languages other then just Python) and they are all (the open source ones) a fair bit out of date with the Blender API.
Resulting in either code that has errors and takes a number of goes to get working. Or, it has no idea about current Blender (think Bone Collections for example) and hence one can’t get it to work at all.

So if you are going to being up the subject in general with the Blender Foundation, then maybe could you consider an open source LLM other then just triage.