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
ToDos
anyone from US/NZL - send a reminder about Thu/Friday triage session this week.
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.
| Indrajith KB | Hi.. Indrajith From India:wave: |
| Griffyn Heels | Griff, Aus :wave: |
| mohit_aghera | Mohit, India :wave: |
| Suresh Prabhu | Suresh, India |
| larowlan | Lee, AU |
| quietone | Vicki, NZ |
| jibran | Jibran, AU. |
| kimb0 | Kim, AU |
| Spokje | Frank, NL |
| mansoor20 | Mansoor, India :wave: |
| Paulo Henrique Cota Starling | Paulo, from Belo Horizonte :flag-br: |
| catch | Nat, UK |
| dww | Derek, US |
0️⃣ .5️⃣ Last helpful article/video you have read/watched on the internet?
| Griffyn Heels | I've been working on a Python Course recently and have found this site invaluable: https://www.programiz.com/python-programming |
| larowlan | https://www.youtube.com/watch?v=dsTXcSeAZq8&pp=sAQA |
| quietone | https://www.thelancet.com/journals/landia/article/PIIS2213-8587%2821%290... |
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 | Approve the previous minutes, checking the credit as well. #3222714: Meeting of the Bug Smash Initiative 2021-07-20 |
| jibran | We have weekly group triage session scheduled and we are are not utilizing those slots. Given that @Kristen Pol (she/her) posted this last week https://drupal.slack.com/archives/C014QES6HSQ/p1627674236002000, how can we be more active during those slots. |
| Kristen Pol (she/her) | :slightly_smiling_face: |
2️⃣.1️⃣ Wins - what wins have you had since the last meeting? Share your successes!
| mohit_aghera | #1822440: "Content access" filter should check for node_grants implementations before adding node access grant queries |
| Indrajith KB | #2886816: When the "Breadcrumb" block is removed, there's no top padding for the main content |
| kimb0 | These bugs are resolved as duplicate of an issue I have been working on. :tada:#1048114: file_copy(), $destination cannot be NULL |
| Spokje | Not (really) related to BugSmash, but I've been chipping away at Coding Standards and making (test-)code more readable with stuff like this: #3221312: ->willReturn(...) would make more sense here Bonus not (really) related to BugSmash: Being back in the working saddle again on actual websites I'm (finally) back at posting patches for Contrib Modules. Stuff learned in here make them whizz through to RBTC/Fixed way more faster compared to times I wasn't involved in BugSmash. So there's a hidden shoot-out with Thank You All! in there somewhere :) |
2️⃣.2️⃣ Thanks - a space for callouts to other contributors who’ve helped you
| kimb0 | Happy birthday for tomorrow @jibran :birthday: |
| jibran | Thank you! Big 35! |
| kimb0 | :dancerwookie: |
| dww | Thanks @kimb0 for working on the big gnarly file system patches! I hope to have time to get back into the saddle with those again in the coming weeks... |
| kimb0 | Legend! :muscle: Thanks! |
| dww | (although I guess they're not exactly bugs...) :wink: But still, thanks! |
2️⃣.3️⃣ Blockers - what’s getting in the way of your issues / goals
| larowlan | working on contrib |
| quietone | Sooo many bugs .. |
| Spokje | Working in general |
| dww | Life is tricky right now. In the process of moving, which is taking up a lot of time/energy. Family stuff. Health stuff. Since I'm already at reduced capacity for $day_job, it's been hard to eek out upstream contribution time... I'm barely staying on top of my "real" commitments as it is. |
| larowlan | know that feeling |
| larowlan | take care of yourself |
3️⃣ Core bug statistics - current state of open bugs
| quietone | Today: 2021-08-03
From: 2021-07-20 to 2021-08-03 All bugs Status Count Approximately 378 yr reduction in total number of years of all open bugs. Only bugs tagged Bug Smash Initiative Status Count Approximately 278 yr reduction in total number of years of all open bugs. |
| mohit_aghera | Thanks @quietoneJust curious, how do you create these reports? |
| quietone | It is another script in https://gitlab.com/Lendude/bug-smash-initiative but I haven't pushed it a long while. |
| larowlan | Thanks for these, another good fortnight |
4️⃣ Nominate your pet issue for a bug-smash target for the next fortnight
| quietone | Fix the 2038 year problem,#3215062: Update hook_schema for Y2038 |
| Paulo Henrique Cota Starling | #3186834: Sorting nodes by title aren't returned in correct order. |
5️⃣ Help me - Is there anything you could use a :hand:
| dww | It'd be nice to know if https://www.drupal.org/project/drupal/issues/139015 is viable for a D7 commit, or if I should close it. That's my oldest open bug report. ;) |
| jibran | Maybe post in #contribute and ping D7 maintainers. |
| dww | Done, thanks for the suggestion, @jibran! |
6️⃣ @quietone Approve the previous minutes, checking the credit as well.
| mohit_aghera | Issue: #3222714: Meeting of the Bug Smash Initiative 2021-07-20 |
| Spokje | I'm normally the one "moaning" about something but this looks perfect to me |
| dww | RTBC'ed ;) Thanks, @quietone! |
| dww | I was expecting to find the sample meeting agenda at #3153713: Bug Smash Initiative meetings - next: 2025-12-09 but lo, that summary doesn't contain our meeting agenda template. Do we always just cut/paste from the previous meeting's "Standing items" section? We should add this as a standing item so we always remember to open a thread for it so @quietone doesn't have to be there to remind us. :smile: |
7️⃣ @jibran: How can we effectively use the triage session timeslots.
| mohit_aghera | https://drupal.slack.com/archives/C014QES6HSQ/p1627674236002000 |
| larowlan | good question |
| quietone | Some thoughts and ideas that come to mind, not in any order.Advertise before hand a set of related issues that will be discussed. This may help folks to prepare for that topic.I lean towards a video call for these but not necessary.Have one person lead the triage on an issue and usually the same person to write the comment. So that while they are writing the comment someone else can lead the next issue.Then the facilitator shouldn't be leading any triage, they need to keep the meeting flowing. |
| dww | Point 1 there would also help by simply letting #bugsmash know there's going to be a triage session at all. ;) I keep meaning to join one and never know if/when they're happening. Like we do with the "hey, next meeting starting in 3 hours" sorts of pings, would be lovely to see a "next triage in 3 hours" or whatever. If possible. Is the info at https://www.drupal.org/community-initiatives/bug-smash-initiative/workin... accurate?We have weekly group triage sessions on Google Meet, alternating between two times.... |
| larowlan | they're in the core calendar yeah |
| jibran | If someone from US/NZL will send a reminder about Thu/Friday one this week then I'm happy to send a reminder for Tues one. |
Participants:
quietone, jibran, Kristen Pol, mohit_aghera, Indrajith KB, kim.pepper, Spokje, dww, larowlan, Paulo Henrique Cota Starling
Comments
Comment #2
quietone commentedComment #12
quietone commentedComment #13
quietone commentedReady for review.
Comment #14
spokjeAdded a space to make a [#issue_id] link work
Comment #15
larowlan