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: Lee
quietone Kia ora!
Griffyn Heels Griff :wave: (edited)
ambermatz Amber :wave:
Meeni Meeni:wave:
jibran Jibran, AU
mohit_aghera Mohit :wave:
lendude Len, :banana-dance:
smustgrave Stephen
Kristen Pol (she/her) Kristen, California, catching up

0️⃣.5️⃣ What module would you most like to see ready for d10?

quietone The one I maintain, Commerce Migrate.
ambermatz Help Topics
Meeni Lingotek Translation
jibran DER which already is I just have to tag a release.
lendude The porting day got me thinking I might actually need to port Simpletest :scream_cat: (edited)
darvanen field_group
smustgrave Bootstrap layout builder
Kristen Pol (she/her) I looked at the top 50 and I like Linkit so that one

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

quietone What to do with tags when closing an issue
Griffyn Heels Need someone that’s a maintainer to go through the fortnightly meta triage threads and issue credit/close
Kristen Pol (she/her) From #contribution-events meeting: https://drupal.slack.com/archives/C03FH8GTB1A/p1661880033508319

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

quietone Group triage of PMNMI issues went well
Kristen Pol (she/her) Not bugsmash but 2nd D10 porting event went well last week :thumbsup:
Kristen Pol (she/her) Just did a big round of triage :thumbsup:

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

lendude @quietone for everything, but let’s highlight the group triage running this time, thank you for that!

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

larowlan very busy at work, 4 weeks till project launch :crossed_fingers: for more free time for smashing bugs
quietone My husband working from home most days is proving to be disruptive.
ambermatz I’ve had some time off this month which was good, but not really enough time. It’s been hard getting back into the swing of things mentally.
lendude Summer vacation makes it hard to get into a steady groove, vacation is over, but not sure that is a good thing :wink:
Kristen Pol (she/her) Competing initiatives (and work and life)... lots of #d10readiness and #contribution-events stuff lately

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.

Griffyn Heels #3304218: [Meta] Bug Smash Initiative triage fortnight commencing 2022-08-16
kimb0 oops
kimb0 I need to re-read the instructions of how to triage

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

quietone #3301995: Meeting of the Bug Smash Initiative 2022-08-16

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

quietone Priority (goal): actual
Critical (50): 61
Major (1000): 952
Normal (6000): 4910
Minor (300): 361
quietone All of those are less than the results from the last meeting. :smile:
quietone Today: 2022-08-30

From: 2022-08-16 to 2022-08-30

All bugs
Open: 44, including 14 fixed
Closed: 66
Age Count
00 24
01 13
02 04
03 02
04 01
05 04
06 08
07 04
08 04
10 01
12 01

Status Count
closed (duplicate) 13
closed (cannot reproduce) 18
closed (fixed) 13
closed (won't fix) 5
closed (outdated) 16
closed (works as designed) 1

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

Only bugs tagged Bug Smash Initiative
Open: 4, including 3 fixed
Closed: 29
Age Count
00 03
01 07
02 02
03 01
04 01
05 02
06 06
07 03
08 04

Status Count
closed (won't fix) 1
closed (cannot reproduce) 10
closed (outdated) 12
closed (fixed) 5
closed (duplicate) 1

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

quietone Not reaching the around 250yr mark but the total bug count will be less, in part because issues for extensions that are being removed from core are being moved to the contrib project.
lendude I usually take a new datapoint every 2 months or so, so probably round the time of the next meeting it’s time for a new one

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

Griffyn Heels Existing critical: #2611872: JS exceptions are thrown each time a multiple-valued text field with a CKEditor instances is being rearanged(edited)
Griffyn Heels Is everyone happy with these? (edited)
ambermatz For the Existing Critical, there is an Aug 12 issue summary update which concludes with “Therefore, this issue is now fixed, and there's no further effort needed here.”
ambermatz So maybe this issue can be closed?
ambermatz Although it does look like some discussion is still ongoing (as of 2 weeks ago).
Griffyn Heels Yeah it does looks like it’s pretty much closed.
Griffyn Heels I’ll see if anyone else has any feedback over the next 24 hours. I can try and pull another if need be.

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

ambermatz Does anyone have a link to this handy?
Griffyn Heels Here’s all the PMNMI issues: https://www.drupal.org/project/issues/drupal?text=&status=16&priorities=...
ambermatz Thanks. I added some filters and sorted by by Last Updated to try and find ones that we’ve commented on but haven’t had any activity, that we could perhaps close. https://www.drupal.org/project/issues/search/drupal?text=&assigned=&subm...
ambermatz This one might be able to be closed. See comment #4: #3203709: Call to a member function getId() on null#comment-14132549
ambermatz In which he says “this issue could probably be closed” :wink:
Griffyn Heels That’s a good sign
Griffyn Heels Gonna add your PMNMI list into the bookmarks
ambermatz Ok I closed it..

7️⃣ What have you learned in the last fortnight?

lendude Not related to this initiative but wrote my first custom cache context, which was nice. And have needed to dive back deep into node access grants, which is less nice :smile:
darvanen BaseFieldDefinition::setDefaultValue != BaseFieldDefinition::setInitialValue
Kristen Pol (she/her) Been coding a bit for a change so used _custom_access on routes for the first time (I think) which came in handy rather than doing the Deriver thingy for hide/show of actions/tasks based on some logic

8️⃣ “What to do with tags when closing an issue” from @quietone

quietone When closing an issue (outdate/won't fix/cannot reproduce) should we remove the tags that no longer needed. Say, the 'needs something' tags.
larowlan good question, I guess there's no harm in keeping them, as you can filter out other listings via status
quietone I should be clear too. That some 'needs' tags must be dealt with before closing an issue. 'Needs followup is one'
quietone True, no harm but can be a lot of clutter.
quietone For the other tags, I do work to remember to remove tags of no value. Like a tag that duplicates the component.
borisson_ Yes, there are a lot of tags without any value being added. I have this text that I frequently add when removing tags, mainly when doing it on my own modulesPS: It seems you (like many others – it's really easy to misinterpret) are confused by the "Issue tags" field. As the guidelines state, they aren't meant for free text tags related to the issue, but only for specific categorization purposes, usually by module maintainers.So, if you aren't sure your current usage is correct, please just leave the field empty.
quietone I like that.
lendude I tend to leave the ‘Needs … ’ tags on when closing because you never are 100% sure it will stay closed, and if somebody opens it back up, you want those tags back on as well
Kristen Pol (she/her) Thanks for this... I'll try to remember to remove unnecessary tags

9️⃣ “Is there a maintainer with some free time available to go through the previous fortnightly meta triage threads and issue credit/close?” from @Griffyn Heels

Griffyn Heels For example: #3301984: [Meta] Bug Smash Initiative triage fortnight commencing 2022-08-02 from last fortnight needs credit given and then marked for closure.
Griffyn Heels There’s quite a few parents that this applies to, but shouldn’t take too long
ambermatz I’m happy to take a look tomorrow at it. It’s getting late for me. I’ll set a reminder.
Griffyn Heels Thanks!
ambermatz I could only find the one you mentioned above.

Participants:

quietone, ambermatz, Meeni, jibran, lendude, darvanen, smustgrave, Kristen Pol, Griffyn Heels, larowlan, kim.pepper, borisson_

Comments

griffynh created an issue. See original summary.

griffynh’s picture

Issue summary: View changes
griffynh’s picture

Issue summary: View changes

larowlan credited darvanen.

larowlan credited jibran.

larowlan credited Lendude.

larowlan credited quietone.

larowlan’s picture

larowlan’s picture

larowlan’s picture

smustgrave’s picture

Status: Active » Reviewed & tested by the community

Looks correct

lendude’s picture

Status: Reviewed & tested by the community » Fixed

Agreed, looks good

Status: Fixed » Closed (fixed)

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