0️⃣ Who is here today? Comment in the thread to introduce yourself. We’ll keep the meeting open for 24 hours to allow for all timezones.

griffynh Griff :wave:
akmalfikri Akmal. Hello.

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.

2️⃣.1️⃣ Wins - what wins have you had since the last meeting? Share your successes!

2️⃣.2️⃣ Thanks - a space for callouts to other contributors who’ve helped you.

2️⃣.3️⃣ Blockers - what’s getting in the way of your issues / goals

3️⃣ Core bug statistics - current state of open bugs

quietone All Bugs
Critical 73
Major 803
Normal 4,619
Minor 297
Total 5,792

Bugs Tagged Bug Smash
Critical 15
Major 235
Normal 1,117
Minor 105
Total 1,472

All issues tagged Bug Smash, all versions
Open 1,852
Closed 5,116
Total 6,968

All issues tagged Bug Smash, all versions. all projects
Open 1,966
Closed 5,208
Total 7,174
quietone All issues tagged Bug Smash, all versions = 73.4 % closed

4️⃣  Bug Smash Initiative - Next Steps Discussion

griffynh Following on from: https://drupal.slack.com/archives/C014QES6HSQ/p1768270470620199
griffynh Thanks for the feedback on the Bug Smash Initiative.Here’s my read on the previous thread:We’ve met our original initiative goalsRTBC bottleneck is a key barrier (150+ issues waiting)Interest in refocusing rather than shutting downPotential to shift from “bugs fixed” to “bugs triaged” as the metric?Coordinate with #stale-issue-cleanup or operate independently?Do people agree with those? What can we do to tackle them?New goal? Triage remaining 4,304 untagged bugs vs. tackle RTBC queue vs. both? (edited)
quietone I would prioritize the RTBC queue. There are currently 45 bugs in that queue. Making sure they are really ready for commit is a big help. For me, that means the Issue Summary is up to date and any questions for a committer or a maintainer are clearly identified. And the change record is correct and has been reviewed.
quietone Chasing up change records isn't fun.
quietone Since there will always be bugs in the RTBC queue maybe there is a way to work through both. Some days of a weel the target issue is an RTBC one and other days not an RTBC one.
smustgrave Could always add it as a daily itemRandom issue (last updated)PMNMIReview a RTBC
smustgrave Only question would be is if leaving a confirmation message will  it moving to the top of the list actually hurt the issue getting in next
smustgrave making the assumption committers work off the end of the queue
mohit_aghera +1 for focussing on RTBC queue as well.
smustgrave @griffynh @quietone should we add a reminder?
griffynh I think i’d rather it take the place of the Last Updated focus that’s there currently. Adding an additional daily objective will probably limit the engagement we get with Bug Smash.
smustgrave What do you think about one more lap of last updated. By then we may get through everything that hasn't been touched in 7 years
griffynh So one more month and then update?
smustgrave Sounds good to me
smustgrave But up for what the group agrees with
acbramley sounds good to me!
larowlan I've been out of core for a while, but made my first commits since Nov this month. I'll pick up RTBC bugs again - it was always my first list to check when looking at RTBC queue
griffynh Sounds like we're settled then, next from next month we'll focus on RTBC to bring that down, then go from there.

Participants:

quietone, griffynh, smustgrave, mohit_aghera, acbramley, larowlan

Comments

griffynh created an issue. See original summary.

griffynh’s picture

griffynh commented
Title: Meeting of the Bug Smash Initiative 2026-01-13 » Meeting of the Bug Smash Initiative 2026-02-10
smustgrave’s picture

smustgrave commented
Status: Active » Fixed

Assigned credit

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.