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.

Griffyn Heels Griff, AU :wave:
quietone Hi
kimb0 Hey there!
larowlan moi :wave:
marcvangend Yours truly :man-raising-hand:
Paulo Henrique Cota Starling Paulo Henrique, Brazil!
dww Derek, US, catching up late...
Kristen Pol (she/her) Kristen, California, catching up late too
lendude Len, Amsterdam, very late to the party

0️⃣.5️⃣ What's your favourite Christmas song? (edited)

Griffyn Heels My favourite is Don't Shoot Me Santa by The Killers
quietone David Bowie & Bing Crosby - Little Drummer Boy/Peace On Earth
larowlan how to make gravy by paul kelly https://www.youtube.com/watch?v=iYqIF2XkqKU (edited)
darvanen Don't really have a favourite but this is fun:https://open.spotify.com/track/23odYnrpoTNoBUYQMtpB72?si=2cda4e37a3fe4eca
Kristen Pol (she/her) Hmm... not sure but used to sing all the classics as a kid... Rudolph, Jingle Bells, Frosty the Snowman, etc... I'm interested in listening to Griffyn's favorite as I like that band

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 First Bugsmash for '22
quietone Make a policy recommendation for Bot usage on GitLab to aid issue management
Kristen Pol (she/her) Any events in 2022 that we might have a contribution event?

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

quietone #2975461: Convert query string to array for d6 menu_link migration

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

quietone @darvanen with GitLab
larowlan griff for picking up the triage of the day a lot of late
dww @quietone for dealing with meeting issues, notes, so many issues, #coding-standards, and much, much more. :thankful:

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

larowlan $dayjob
darvanen Same, bit snowed at the moment. Might get into it a bit over the break, might not. January looks pretty full from here too :confused: (edited)
dww $dayjob, $holidays, death in partner's family + related fallout/drama, etc. I know this is basically all a volunteer effort and I shouldn't feel bad, but I do, anyway. Wish I had more time for this, since it's so important!
Kristen Pol (she/her) Pretty much the same... fortunately my big project should wrap up next week and I'll have more sponsored time (though hope to take some much needed rest over the holidays) (edited)
lendude Not much getting in the way! Sprint is drying up a bit, usual end of year stuff, so got some contrib time ahead!

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

quietone Today: 2021-12-07

From: 2021-11-23 to 2021-12-07

All bugs
Open: 40, including 9 fixed
Closed: 66
Age Count
00 27
01 10
02 10
03 05
04 09
05 03
06 01
07 01

Status Count
closed (duplicate) 23
closed (works as designed) 7
closed (cannot reproduce) 6
closed (outdated) 12
closed (fixed) 18

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

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

Status Count
closed (duplicate) 9
closed (works as designed) 4
closed (cannot reproduce) 3
closed (outdated) 9
closed (fixed) 4

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

quietone I need to update the script to add issues for 10 and remove 8

4️⃣ Nominate your pet issue for a bug-smash target for the next fortnight

dww Heh, I guess the :cricket: s in this thread means either a) folks are too busy for #bugsmash or b) don't really care about manually selecting targets. Seems I've once again over-engineered a solution to a problem that doesn't exist. :wink:
Kristen Pol (she/her) I think people are good about getting help in the channel so not sure this is necessary... especially given the random targets

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

dww a. I'm not sure what else I can do to get an accessibility signoff on #3097907: Active toolbar tray has weak affordance and fails WCAG color criteria -- we've tagged it for that, I've pinged the #accessibility channel a few times, etc. Would love to get that back to RTBC and committed someday.
dww b. Would love help with triage and reviews in the update.module component.

6️⃣ Approve last fortnight's minutes

Griffyn Heels Here are the minutes from the last meeting: #3249032: Meeting of the Bug Smash Initiative 2021-11-23
dww Basically looks good. Thanks, y'all!However, there was some additional (relevant) discussion in thread 1️⃣ 0️⃣ (from after the 24 hour mark) to clarify some things. Not sure what the policy is/should be about this. Perhaps it doesn't matter and "no one" reads these issues and the minutes. But wondering if it's worth adding more to the notes for that thread?More generally, wondering if/how we should handle this in the future. Is it worth waiting a week or something before creating the minutes, to give all the threads time to completely quiet down before we save them?
dww cc @quietone (only because you seem to be the one that "always" takes care of this task, not because you "should" have to deal with it). :wink:

7️⃣ "First Bugsmash for '22"

Griffyn Heels I suggest that the next/first BS for '22 is the 18th of January - any issues with that?
darvanen No issue here.
quietone Fine with me.
kimb0 cool :sunglasses:
dww In the US, that'd fall on the evening of MLK day (1/17). Probably doesn't matter. But curious why wait so long into January before restarting meetings. Any problem with doing it the previous week? Jan 10/11? ¯\_(ツ)_/¯
Kristen Pol (she/her) Lots of people will be on holiday so seems fine to me
lendude 18th sounds fine, if we want to fill up the time we can run triage sessions if time permits

8️⃣ @quietone "Make a policy recommendation for Bot usage on GitLab to aid issue management"

quietone More info from #gitlab https://drupal.slack.com/archives/CGKLP028K/p1638398635123900
quietone I think we have agreement on 'a bot should not close issues'.
quietone What else ?
quietone There is already an issue #2328093: Establish policies for external bots or tools that post or modify content on drupal.org
larowlan I'd like to see a freshness bot
larowlan drops in and says, things are quiet - is this issue still relevant etc
larowlan but I think we could also write a bot to say 'you're missing the template'
larowlan e.g. a bug without a steps to reproduce section
larowlan we could also add one that sets RTBC issues back to NR if they are tagged with 'Needs {x}' where x is certain things like tests, screenshots, issue summary update, {x} manager review, performance testing, a11y testing, change record
quietone When/how to define when things are quiet?
larowlan yeah
quietone 1 year for a bug?
larowlan in an ideal world, much less
larowlan but we have 6k of backlog to get through
quietone A large backlog implies, to me, that 1 year is too short. It may make unwanted noise?
larowlan yeah it might need us to do some maths on how noisy it would be
darvanen Start ten years out, do $x (five?) days worth every day until you reach a lower limit like 3 months. (edited)
quietone I too have thought about an incremental approach.It will impact less people to start and allow feedback on the message etc as it grows to impact more people.
quietone I was thinking that the first group would be all in the long tail on the graph on https://lendude.gitlab.io/bug-smash-initiative/ which is 7years, then start reducing by 6 months.
darvanen If we start at 7 years we'll still instantly "bot" nearly a thousand issues (edited)
darvanen Oh wait, no that graph is by date opened, not last activity.
quietone Good point. Doing a gross visual assessment the tail for last updated is at 6 years and is less than 10 pages of 50, so 500 issues, roughly.
dww If we do this at all, I like the idea of a phased approach so we don't ping too many issues all at once.
dww I'm also not sure a "freshness" bot is all that useful, TBH. But I don't really know, and I don't want to stand in the way if people are inspired to try to make this work.
Kristen Pol (she/her) I like the freshness bot if it's not super chatty... starting with large gap first sounds good
Kristen Pol (she/her) YES PLEASE FOR THIS ONE!!! Especially if it's a bug without steps to reproduce https://drupal.slack.com/archives/C014QES6HSQ/p1638851650014200?thread_t...

Participants:

Griffyn Heels, quietone, Kristen Pol, larowlan, dww, darvanen, lendude, kim.pepper

Comments

quietone created an issue. See original summary.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

griffynh’s picture

Issue summary: View changes

quietone credited Lendude.

quietone credited darvanen.

quietone credited dww.

quietone credited larowlan.

quietone’s picture

Adding credit

lendude’s picture

Status: Active » Reviewed & tested by the community

Looks good, links work, credits make sense.

quietone’s picture

Status: Reviewed & tested by the community » Fixed

@Lendude, thanks.

Status: Fixed » Closed (fixed)

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