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
Agenda
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 | :wave: Griff, Aus |
| mohit_aghera | Mohit, India :blob_wave: |
| larowlan | lee, Aus |
| jibran | Jibran, AU |
| quietone | Hi |
| lendude | Len, NL |
0️⃣.5️⃣ The Oscars was on yesterday, what was your favourite movie of last year?
| Griffyn Heels | Probably Petit Maman or Titane - Both :flag-mf: |
| larowlan | don't even think I saw a movie that was released in 2021 (edited) |
| darvanen | Same |
| lendude | Just saw Netflix and Disney+ stuff that was released this year, didn’t go to the movies, I think those are oscar eligible now too? Dunno :shrug: |
| dww | I really loved Soul, although hah, I lost track of the years and that was 2020. :stuck_out_tongue_winking_eye: If you like clever, uplifting, consciousness-raising animated films, Encanto is great from 2021. |
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 | Update on committed but open issues, from https://drupal.slack.com/archives/C014QES6HSQ/p1629173648115400 |
| quietone | PMNMI issues |
| dww | Whoops, forgot to raise these in advance. Hope y'all don't mind that I opened these 2 bonus threads:https://drupal.slack.com/archives/C014QES6HSQ/p1648601366282699https://d... |
2️⃣.1️⃣ Wins - what wins have you had since the last meeting? Share your successes!
| larowlan | i actually had time to look at two BS issues |
| dww | Most wins have been in the realm of tasks for the past 2 weeks, but happy that #3266308 landed for :bug: :hammer: |
2️⃣.2️⃣ Thanks - a space for callouts to other contributors who’ve helped you
| larowlan | quietone for tireless effort, lendude for updating the stats |
| larowlan | spojke and bbrala for work on d10 module removals (which help with debt in core) |
| Griffyn Heels | thanks to jibran and kimb0 for support running recent BS meetings. |
| quietone | benjifisher for work on migrate critical bug |
| Spokje | spojkeThanks laworlan... :innocent: |
| larowlan | Sorry for the typo |
| dww | All of the above. And @danflanagan8 for working on #3268932 to help unlock tests from classy for removing more tech debt. Also tasks, but also a win for us to make writing tests easier/better. |
2️⃣.3️⃣ Blockers - what’s getting in the way of your issues / goals
| darvanen | Launch deadlines looming, I've been pretty quiet here lately and that's unfortunately going to continue for a few months I think. |
| lendude | Busy getting ready for Drupal Dev Days, taking up my contribution time for now, but its next wek, so hoping to do a lot of triage and roping in new people then! |
| dww | The usual: time. Exacerbated by #d10readiness eating a bunch of my available contribution effort. |
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 | #3269826: [Meta] Bug Smash Initiative triage fortnight commencing 2022-03-15 |
| Griffyn Heels | I think it's that one |
2️⃣.5️⃣ Approve last fortnight's minutes
| Griffyn Heels | #3267290: Meeting of the Bug Smash Initiative 2022-03-15 |
| lendude | Took a look, looks good, RTBC’ed |
3️⃣ Core bug statistics - current state of open bugs
| quietone |
|
| lendude | That is looking a little better :slightly_smiling_face: |
| lendude | And I added a new data point to https://lendude.gitlab.io/bug-smash-initiative/ for those that missed it |
4️⃣ Lets check back on our targets and set some new ones
| quietone | Critical - [#3211992]changed to Major with new small patch by alexpott. It is waiting for review |
| quietone | Major - https://www.drupal.org/node/2834250A small IS update was done |
| quietone | Normal - [#2978024]Minor IS updates |
| quietone | Normal - [#2845571]Got some work and waiting review. |
| lendude | RTBC’ed the last normal, thanks so much @quietone for the work on that one |
| dww | This is a great thread. When some dust settles down, I hope to come back here and review some/all of these. Thanks! |
5️⃣ Help me - Is there anything you could use a :hand:
| darvanen | Don't know how to progress this RTBC bug[#3258321]Am I just being too impatient? (edited) |
| lendude | Yeah, to quote Axl Rose: all you need is a little patienceOnce something is RTBC, it’s out of your hands |
| darvanen | Cool, thanks. |
| lendude | But to quote Dexter Holland: I would be patient but it takes so long(sorry I’m a lyric nut :wink: ) |
| dww | #3097907-71: Active toolbar tray has weak affordance and fails WCAG color criteria Major bug fix was RTBC, then potentially scope derailed. I explained my reasoning and tagged for release manager and product manager reviews. Hoping that can return to RTBC as-is.
Moved to https://drupal.slack.com/archives/C223PR743/p1648602421586229 and resolved. #3255809 (new toolbar nightwatch tests) are failing. (edited) |
5️⃣ @quietone - https://drupal.slack.com/archives/C014QES6HSQ/p1648530118044749?thread_t...
| quietone | I got a bee in my bonnet about this list of 115 issues awhile back. So I decided to go through the whole list. |
| quietone | Many were reverted so nothing to do on those. Some were already fixed in another issue. |
| quietone | For some I decided to close the issue with the commit and make a new one, with whatever work was still remaining. I was hoping that would help focus on what needs to be done and not some long winding discussion of other points. There is still the link in the related issue, so easy to find if it needs to be read. |
| quietone | There are now 10 left that are more challenging. Well, 11 but one is RTBC. |
| quietone | To finish the remaining one I'll likely start posting them in the coming weeks. |
| quietone | oh, the spreadsheet is https://docs.google.com/spreadsheets/d/16P7m6IlLWgez0Q79UDT14MC-hJYlssQj... |
| dww | This is all great, thanks for doing this, @quietone! |
6️⃣ @quietone - PMNMI issues
| quietone | Just a reminder really that these are often easy to triage and have a high possibility of being able to close. |
| Griffyn Heels | What does PMNMI mean? |
| quietone | PMNMI - Postponed Maintainer Needs More Information |
| quietone | For example, this has been waiting 6 years for a reply. #1394480: Improve granularity of theme registry cache clearing |
7️⃣ Check-in on the "triage your own issues" initiative.
| dww | This was a thing from many meetings ago. We were all encouraged to go back and triage all open bug reports that we each opened as the original reporter. |
| dww | I still have a bunch to do, but it was fun and rewarding to go back through it. |
| dww | 2. I'd love to hear updates from other folks on their experiences. |
| dww | 3. Seems like a good thing we could document on our initiative page as a way to contribute to the effort. |
| quietone | And any time someone presents about bugsmash this should be included |
| quietone | I've got some time now, I'll add it to the initiative page (edited) |
| quietone | It is added but the link shows the number of issue, which I wish it didn't. Maybe someone else can make it nicer.https://www.drupal.org/community-initiatives/bug-smash-initiative/workin... |
| dww | For starters, any link that includes class .no-issue-count will opt-out of the auto JS count thingy. I'll add that. I also think there's a better link to send folks to. Something based on https://www.drupal.org/project/issues/user but filtered for core bugs. Stay tuned. |
| dww | Yeah, how's this?https://www.drupal.org/project/issues/user?projects=Drupal+core&categori... |
| quietone | But that isn't limited to the issues that I submitted. Can it be just the ones I created? |
| dww | Oh, right... 1 sec. |
| dww | Yeah, drat. There's no good way to do that, you're right. |
| dww | Well, I'll at least add the no-issue-count class... |
| dww | Normally, I'd open a feature request for project_issue to allow a placeholder for submitted=-me- or something, but since project_issue is going to die, probably not worth it anymore. |
8️⃣ Trying to recruit any of the more active bug fixers to tag their work for #bugsmash.
| dww | E.g. folks like longwave, andypost, phenaproxima, benjifisher, et al. If more of them were self-identified bug smashers, we'd probably see a noticeable bump in our overall impact. |
| dww | 2. I don't believe that's "cheating". If folks like lendude and I tag every bug we see for smashing, why not other prolific core contributors? To the extent they're helping to spread the word, talk about their work through this lens, etc, it's helping to build / grow our work... (edited) |
| dww | 3. I agree it's a little more murky with core committers. If all of them tag all bugs they see for this initiative, the stats become meaningless. Curious to hear larowlan's perspective on this part, and how they handle this... (as an initiative co-founder, etc). But curious what any/all committers think... (edited) |
| larowlan | I tag stuff I work on, but I generally only review the RTBC bugs list |
| catch | I tag stuff as bug smash if I triage it, or in the hope that it'll get picked up by this channel. I don't tag bugs that I commit from the RTBC queue but otherwise haven't worked on though. |
| dww | That’s a great distinction for committers: if you triaged it or worked on the code, you tag. But if you just commit it, you don’t. Makes sense. |
| dww | So, I guess my original question still stands: does anyone else agree with the “recruit more heavy-hitters” approach? :wink: |
Comments
Comment #7
quietone commentedComment #8
quietone commentedComment #9
larowlanComment #10
dwwSeems good, other than the priority. Thanks!