Agenda items

Standing items

  • Who is here
  • Any other suggested topics
  • Wins / Thanks / Blockers
  • Statistics and functionality update. X new bugs created in last two weeks. Y closed by the initiative.
  • The bug I would most like to see fixed
  • Update on target items from last meeting
  • What should be the initiative focus for the next 2 weeks?

Statistics

Statistics graph

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.

larowlan :wave:
Griffyn Heels Griff, Aus :wave:
ambermatz :wave:
Michael (g-brodiei) Michael, Taiwan :wave:
quietone Hi
akshaydalvi212 :wave: Akshay Dalvi, India
lendude Mornin’
catch :wave:
Kristen Pol (she/her) Kristen, California, catching up :wave:
dww Derek catching up way late...

0️⃣ . 5️⃣ What talk are you most excited for at DrupalSouth next week?

larowlan code sprint! :beetle: :hammer:
Griffyn Heels https://drupalsouth.org/events/drupalsouth-wellington-2023/schedule/2716 for me.It’s about contrib & getting more people onboard which really overlaps Bug Smash!
Kristen Pol (she/her) Do you know when the recordings will be made available?

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

Griffyn Heels Who’s going to be attending DrupalSouth next week?
ambermatz I’ll be presenting (remotely) about #bugsmash and #needs-review-queue-initiative at DrupalCon as part of the Community Initiatives Keynote with a special focus on how folks can participate that day by triaging issues. If you will be at DrupalCon, could you let me know? I will be pointing the audience to the Slack channels but also want to point people to appropriate tables at the contribution event if someone will be there in-person.
ambermatz Also, related to the DrupalCon Community Initiatives Keynote, I was thinking of a doing a mini-lesson on issue triage, since the point of the keynote is to help people participate in the initiatives. Yes, there will be a quick overview of Bugsmash and Needs Review but the rest of the (short) presentation will be about how to do issue triage. Do you think that makes sense? Or do you have other ideas (that would help people know how to help with bugsmash or needs review that day)?
Griffyn Heels Sorry Amber, I missed those, opened threads.
quietone We are reaching the 3 year anniversary. Can we get updated stats?

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 got in the way of your issues / goals

Kristen Pol (she/her) Shingles :disappointed: nearly 8 weeks now... get your vaccine! it's not fun
dww Client work. Busy life.

2️⃣.4️⃣ :loudspeaker: If you helped with the triage since the last meeting then don’t forget to post a comment to triage issue on d.o.

Michael (g-brodiei) The date seems wrong, should it be this post to comment within?#3353600: Meeting of the Bug Smash Initiative 2023-05-09
Griffyn Heels You’re right, thanks for that, I’ve deleted my message and updated the link in the bookmarks (edited)
Michael (g-brodiei) Thanks!
Kristen Pol (she/her) I'm confused... are we no longer using a separate triage issue?
Kristen Pol (she/her) i.e. are we posting our triaged issues on the meeting issue instead?
Kristen Pol (she/her) Also I'm seeing several old open triage tickets, is it okay if I go mark them all fixed?
Kristen Pol (she/her) Actually... I can't because I can't give them credit

2️⃣.5️⃣ Approve last fortnight’s minutes

Griffyn Heels The following are ready for review:#3350987: Meeting of the Bug Smash Initiative 2023-04-11

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

quietone Priority (goal): actual
Critical (50): 47
Major (1000): 899
Normal (6000): 4398
Minor (300): 311
Total: 5655
quietone From: 2023-04-25 to 2023-05-09

All bugs
Open: 52, including 22 fixed
Closed: 43
Age Count
00 21
01 02
02 03
03 06
04 02
05 03
06 03
07 02
12 01

Status Count
closed (duplicate) 8
closed (won't fix) 3
closed (works as designed) 5
closed (outdated) 6
closed (fixed) 20
closed (cannot reproduce) 1

Approximately 162 yr reduction in total number of years of all open bugs.

Only bugs tagged Bug Smash Initiative
Open: 9, including 7 fixed
Closed: 14
Age Count
00 02
01 01
02 03
03 03
04 01
05 02
06 01
12 01

Status Count
closed (won't fix) 1
closed (outdated) 2
closed (fixed) 10
closed (cannot reproduce) 1

Approximately 87 yr reduction in total number of years of all open bugs.

Griffyn Heels Wow we are close on the overall goals of the initiative.
lendude Wow! 11 minors to go! Sounds doable :slightly_smiling_face:
catch Is that the first time critical have been under?
Kristen Pol (she/her) WHOA! Nice! 11 minors and goal met :heart_eyes:
Kristen Pol (she/her) wouldn't that be fantastic to do by DrupalCon and keep all the others under the line???
quietone It very likely this is the first time Criticals have reached the goal. But I don't keep records to prove that. If anywhere, it would be in the minutes.
dww Fantastic progress, everyone!  This is amazing.

4️⃣ Lets check back on our targets and set some new ones (edited) 

Griffyn Heels I’m going to take this thread out of the template moving forward, the targets haven’t proven too effective.

5️⃣ Help me - Is there anything you could use a :hand:

6️⃣ Let’s look back at PMNMI issues that we can close this fortnight

7️⃣ What are you learning / planning to learn this fortnight?

8️⃣ @darvanen “Seems to me this initiative is suffering from fatigue (I know I am). What if we paused the triage notifications for a little while or reduced them to once a day?”

larowlan I think half the issue is we've been too successful and the amount of low hanging fruit has dwindled
larowlan the issues that are showing up just need someone to work on them, rather than 'oh this is a duplicate'
darvanen I wouldn't disagree with that
darvanen Except to remove "too" :wink:Success is good
Griffyn Heels I wonder what the BugSmashers in the other timezones think of the 2nd issue of the day. is it useful?As the main goal of it was to give them something to work on.
Griffyn Heels Also, could we change this from triage to something else to make it a bit more fresh?
ambermatz I would find it useful to cycle through subsystems each month, to get a chance to get familiar with bugs in that area. For example, one month we focus on multilingual bugs, next month, Views, the next month Migrate. These are just examples. Maybe these “themed” bugs could be the 2nd issue of the day.
darvanen That sounds useful, would help with memory of duplicates?
larowlan yeah I like that idea, we 'swarm' on a module
ambermatz Yeah, I’m always amazed how people can recall duplicates, but that just comes from frequency and exposure. So if we can focus on a subsystem, maybe we can build up some familiarity with it and be more effective.
Michael (g-brodiei) I like the idea too, plus we may involve contributors from other channels as well. Personally I find it hard to attend more on bug smash due to the lack of time and knowledge to write testing for unfamiliar area, which I may need more time to explore.
larowlan with the exception of criticals, we've basically met the goals for this initiative
larowlan so perhaps we frame new goals focussed on a subsystem
larowlan e.g. we say 'reduce views bugs by 10%' and then when we achieve that we pick a new subsystem and a new goal?
lendude The low hanging fruit is probably still around, but it used to be 80% of all issues, where now it feels like 20%, so instead of getting 4 out of 5 good triage issues every week with random, we now get only 1 every week :shrug:I thought the move to ‘active’ issues with no ‘bug smash’ tag would have made the selection a bit better, but it didn’t change much in the ‘getting good triage issues’ sense
lendude I still like it, it adds some activity to the channel and keeps you coming back even though not a lot are actionable. It still gives you a sense of what lives in the issue queue
Kristen Pol (she/her) Although I don't really help with the group triage, I like the idea of the subsystem approach to get some familiarity with an area for a bit before moving on...
Kristen Pol (she/her) Given that the goals would be met with 11 more minors... any way we can do a "minor push" before DrupalCon to see if we can meet all the goals before then? That would be a fantastic announcement to make there :slightly_smiling_face:
darvanen Seems like a worthy pursuit to me
DanielVeza Big fan of the subsystem target idea! Menu would be another candidate. There is a ton of issues from the early D8 days that can probably be closed or at least need to be re-evaluated
dww +1 for the subsystem focus / smarming concept.-0.25 for a "minor push" -- they're minor.  We don't need to care. :sweat_smile:  Even if it is technically close to meeting our (somewhat arbitrary goal).  That said, meeting the goal would be nice, so I'm not strongly opposed.  :joy:

9️⃣ @Griffyn Heels “Who’s going to be attending DrupalSouth next week?”

Griffyn Heels :wave:  I’ll be there, no presentations for me this time.
larowlan :raising_hand:
darvanen o/
Michael (g-brodiei) Can only show support online!!
Kristen Pol (she/her) I thought I heard/saw there was going to be an online aspect for contribution but I'm not seeing that on the website (though maybe I missed it)... if there is remote participation for the contribution event then I can likely "attend" for part of that
dww Not I. :sad-panda:  I might be able to do a little remote contribution, but probably not much...

🔟 @ambermatz DrupalCon attendees

Gábor Hojtsy (he/him) I would expect folks at the mentored tables will also be able to participate in bugsmash and needs review, assuming some issues are triaged for them :slightly_smiling_face:
Gábor Hojtsy (he/him) So its worth brining this topic into the mentoring meetings too IMHO.
Kristen Pol (she/her) Thanks @ambermatz :pray:
dww Yes, thanks @ambermatz!  If you need help working on the keynote, feel free to ping me.  I'd be happy to review slides, be a sounding board, whatever.  I'll also try to be available for online #bugsmash mentoring / support around then.

1️⃣ 1️⃣ @ambermatz Ideas for a 'how to do issue triage' keynote

lendude I think that makes perfect sense. Triage is a great way to get people involved.
Kristen Pol (she/her) Many people don't know what triaging is/means or how it would work so this would be very valuable IMO

1️⃣ 2️⃣ @quietone “We are reaching the 3 year anniversary. Can we get updated stats?”

larowlan I will ask drumm

Participants:

larowlan, Griffyn Heels, Kristen Pol, ambermatz, quietone, dww, Michael (g-brodiei), lendude, catch, darvanen, DanielVeza, Gábor Hojtsy

Comments

griffynh created an issue. See original summary.

griffynh’s picture

Title: Meeting of the Bug Smash Initiative 2023-04-25 » Meeting of the Bug Smash Initiative 2023-05-09
griffynh’s picture

Issue summary: View changes

larowlan credited catch.

larowlan credited darvanen.

larowlan credited dww.

larowlan credited Lendude.

larowlan’s picture

larowlan credited quietone.

larowlan’s picture

larowlan credited mstrelan.

larowlan’s picture

larowlan’s picture

g-brodiei’s picture

Hi @larowlan, thanks for crediting everyone, just wanted to check if there is a mis-credit between the two Michaels? (@mstrelan) and me (@g-brodiei)?

larowlan’s picture

Yeah I added mstrelan by mistake, but had already credited you

g-brodiei’s picture

Haha, it must be confusing, thanks for spending the effort double checking, cause I still didn't see it on my account page, probably it's a cache problem.

Will wait and see, cheers!

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

amber himes matz’s picture

Status: Active » Reviewed & tested by the community
amber himes matz’s picture

Status: Reviewed & tested by the community » Fixed

Sorry for the noise, I should have marked these as "Fixed".

Status: Fixed » Closed (fixed)

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