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-02-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
- any?
"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 user
reports: Issues - needs-information-reports - Blender Projects - Updates on revisiting “bottom 50” (at least) Needs Triage reports
- Ideas for ways to include “Bug Fixes” from older releases in the release notes
- 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)
- Yimming will discuss exposing dependency cycles in the UI with other developers and create a design task for it.
- Discussion about Tests:
- reply in devtalk
Meeting Notes
- Discussion about exposing dependency cycles to the end user
- Yiming has created a design task 134659 and a prototype PR 134659
- Yiming has been trying to implement this feature into the info editor with existing Blender UI elements. This has brought various design limitations.
- Yiming will talk to other developers to see if there are some insights they can share here.
- Talk about Proposal - Label Changes
- Previous thread Discussion around adjustments to Blender issue labels
- Adding Crash labels
- The triaging module doesn’t mind a crash label if developers want it.
- Complexity
- This area doesn’t really impact the triaging module.
- Pratik and Yiming suggested maybe this could be handled with columns in module workboards instead of labels. But this reduces discoverability/visibility and may not align with how the modules use their workboards.
- Will modules add these tags consistently? If they don’t then it’s not that useful.
- Interests
- More granular interests aren’t a bad thing.
- But if they’re not used consistently, they’re not that useful.
- The ~6000 old reports won’t have these granular interests.
- We had a similarish idea a while ago with Discussion around adjustments to Blender issue labels
- We may want to look at this again.
- Status
- Doesn’t really impact the triaging module.
- Generally Philipp would be interested in learning how modules/developers use the current infrastructure (workboards and labels), and could this help make decisions?
- Could we ask development coordinators (Fiona or Thomas) to ask modules for input here?
- Alaska has made a tool to automatically notify people of old
Needs information from user
reports: Issues - needs-information-reports - Blender Projects- Alaska proposed combining everyone’s outputs onto a single issue for various reasons:
- Triagers can help each other clean up the list when someone is away or unwell.
- Triagers can see the list of
Needs info from users
reports that don’t have a triager subscribed to it (occasionally happens when a developer triagers a report). - If triagers change (volunteers joining and leaving), it’s all in one place and easier to adjust.
- (contact Bart/Brecht if this can also run in the “real” infrastructure)
- Alaska proposed combining everyone’s outputs onto a single issue for various reasons:
Following meeting
The following meeting will be on 2025-03-06T12:00:00Z. Again it will be open for everybody who’s interested.