Performance Chat Summary: 14 January 2025

The full chat log is available beginning here on Slack.

Announcements

Future meetings will be held fortnightly, following a set agenda laid out in this document
With the start of 2025, we are looking for new Team Reps to represent the Core Performance Team within the overall WordPress project. If you have someone to nominate or you would like to volunteer yourself, please leave a comment!
https://make.wordpress.org/performance/2025/01/13/core-performance-team-rep-nominations-for-2025/

Bug scrub cadence proposal from @flixos90
- Bug scrub meetings can be inefficient because the people who need to weigh in on tickets are usually not there. So they sometimes end up mostly as a “monologue”.
- There’s also the overhead of commenting on the ticket but also sharing what happens in Slack, which makes scrubbing the bugs slower.
- Scheduled bug scrubs are important also for the fact that otherwise there’s a chance nobody will do it.
- We could consider a format where we have regular bug scrubs, but it’s always one person doing it (rotating per meeting). They would always share a report on Slack when they start and then go over the tickets on their own and comment on each ticket with whatever update they think makes sense (checking in with reporter or PR author, changing milestone, changing priority, …).
After discussion, it has been agreed that the cadence of these meetings will remain fortnightly, and will be led by one person
- The recommended process has been captured in this document which we invite people to review and comment
- The rotation of bug scrub leads can be found in this spreadsheet – we welcome volunteers to help here