Hi, and welcome to the monthly meeting of the Bug Smash community initiative!This meeting:Is for contributors who are interested in helping reduce the number of open bugs against Drupal 11 core.Usually happens every second Tuesday at 02:00 UTC.Is done over chat.Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!Transcript will be exported and posted to a core issue for this meeting. For anonymous comments, start with a 👤 emoji. To take a comment or thread off the record, start with a 🚫 emoji.

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 :wave: Hola, Griff

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!

smustgrave both NR and RTBC queues are at all time lows (at the same time) so issues are landing

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 Open Bugs
Critical 68
Major 802
Normal 4,601
Minor 297
Total 5,767

Open Bugs Tagged Bug Smash
Critical 13
Major 237
Normal 1,113
Minor 104
Total 1,467

All issues tagged Bug Smash, all versions
Open 1,837
Closed 5,181
Total 7,018

All issues tagged Bug Smash, all versions. all projects
Open 1,957
Closed 5,271
Total 7,228

4️⃣ Previous meetings

smustgrave @griffynh just fyi I close[#3578672]
smustgrave And started[#3584747]

Participants:

smustgrave, quietone, griffynh

Comments

smustgrave created an issue. See original summary.

smustgrave’s picture

Status: Active » Fixed

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.