Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.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
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 | Lee AU |
| darvanen | Max :wave: |
| quietone | Hi |
| Griffyn Heels | Griff Syd :wave: |
| mohit_aghera | Mohit, India :wave: |
| jibran | Jibran, AU. |
| kimb0 | Kim, AU |
| lendude | Len, NL |
| marcvangend | Marc, NL |
| Paulo Henrique Cota Starling | paulocs - BH, Brazil |
| dww | Derek US |
| Kristen Pol (she/her) | Kristen, California, catching up late |
| ambermatz | Amber, US |
0️⃣.5️⃣ What's your plans for the holiday period?
| darvanen | Go to Port Macquarie, see family :slightly_smiling_face: |
| Griffyn Heels | I'm off to the UK with my partner, been a long time since long international travel! (edited) |
| quietone | Unknown |
| larowlan | nothing planned |
| mohit_aghera | Not defined!! |
| kimb0 | sleep |
| lendude | Going to Texel |
| marcvangend | Still planning, but it will surely involve Family, Friends and Food. |
| Paulo Henrique Cota Starling | my host brother from Germany will visit me and i go to Rio de Janeiro with him and some friends |
| dww | About to be offline for the rest of the week. Going to an amazing intentional gathering of friends for food, merriment, music-making, and connecting with nature. It’s my “chosen family”. Super excited... |
| Kristen Pol (she/her) | Haven't figured it out yet but my "boys" (16 and 18) haven't had a Christmas tree in 3 years because of everything so we are going to do that for sure... I get to be Santa :santa: ... otherwise I am itching to travel but we have to figure out locations later as we see life unfold... this week is Thanksgiving for us so lots of food and family in 2 days |
| ambermatz | nothing planned, might pick up some steaks and figure out the whole steak in a cast iron pan in the oven thing. tips welcome. |
| jibran | I'll watch Witcher, new Spiderman movie, finish reading Dune and then watch the movie. :smile: |
| kimb0 | @jibran great movie, even better book |
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 | Automated messages for stale issues. |
| quietone | Adding a request to search for duplicate issues to https://www.drupal.org/node/add/project-issue/drupal |
| quietone | Selecting target issues for this fortnight |
| kimb0 | https://www.drupal.org/project/drupal/issues/360057 |
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 was committed |
| marcvangend | #3049408: Allow select query without a table is now RTBC thanks to a review swap here. |
2️⃣.2️⃣ Thanks - a space for callouts to other contributors who’ve helped you
| lendude | Nice to see @marcvangend getting involved in this channel, welcome mate! :wave: |
2️⃣.3️⃣ Blockers - what’s getting in the way of your issues / goals
| larowlan | mostly time |
| lendude | COVID…. |
| Kristen Pol (she/her) | Work, life, usual |
3️⃣ Core bug statistics - current state of open bugs
| quietone | Today: 2021-11-23
From: 2021-11-09 to 2021-11-23 All bugs Status Count Approximately 186 yr reduction in total number of years of all open bugs. Only bugs tagged Bug Smash Initiative Status Count Approximately 136 yr reduction in total number of years of all open bugs. |
| lendude | I’ll see if I can find some time to take a new data point for the stats page |
4️⃣ Nominate your pet issue for a bug-smash target for the next fortnight
5️⃣ Help me - Is there anything you could use a :hand: with?
| darvanen | There are conflicting opinions (mine and anothers) on the direction of https://www.drupal.org/project/drupal/issues/85494 so it has stalled. It comes down to whether "notify the old email address" means "notify the old email address regardless of whether validation is required" or "notify the old email address only when validation is required".I don't know what to do about it. |
| larowlan | perhaps ask in security-questions? |
| darvanen | Ok, can do that |
| jibran | I can review some patches if someone is looking for reviews. |
7️⃣ Action items from last meeting
8️⃣ @quietone "Automated messages for stale issues."
| quietone | It is clear that the community does not want issues closed by bot. Instead, how about having a bot add a comment to stale (to be defined) issues that sets the status to PMNMI and includes the message that the issue may be closed in 3 months. |
| darvanen | I see no reason not to automate that now that we've defined the process. |
| darvanen | The challenge will be figuring out how to define 'stale' of course |
| quietone | And the text of the message. |
| darvanen | Yeah, when I first read this I thought you meant the kind of issues we already have a process (and therefore a message) for. |
| darvanen | but even those would be difficult to define for a machine. |
| quietone | The process was for issues already PMNMI but had no response for, I think, 3 months. At least, that is what is on the initiative template page. |
| darvanen | Well that one should be easy enough to automate, I definitely support not having to go back and find those issues manually to close them after 3 months. |
| quietone | I think we have a misunderstanding. The issue still needs to be closed by a human. We did this in migration system. I added the 3 month message to PMNMI that were stale. 4 month later benjifisher reviewed those issues and marked most of them closed. Some he did not because, as I recall, he thought they were valid for some reason and needed further work. |
| quietone | I think, at best, we hope that someone following the issue will get the message and take a moment to respond. |
| larowlan | I think 'hey its gone quiet here, is this still an issue' type message is great, doesn't close things, but might prompt more activity |
| dww | As with the thread on a “hey, search for existing issues before submitting a new one” thread, I fear the more effort we sink into our bespoke tool chain, the more sad we’ll be when we move to Gitlab. I think we need to stop thinking “these are our tools, let’s optimize them for what we need”. We need to start lowering our expectations and learn to live with “that’s how the tool works”. |
| Kristen Pol (she/her) | I was very much in favor of this but then read what @dww wrote... very good point :/ |
| Kristen Pol (she/her) | I don't know the timeline for cutting things over to gitlab for issues... it's a cost benefit thing... if it'll take years then I'd like this automated... if things will be moved in 6 months then it might not make sense (edited) |
| quietone | They are valid points and yet lowering our expectations is not going to improve the drain a growing issue queue has on the community.
I don't know how/if the bulk update to issues will be done after the move to Gitlab. I did not find an issue for it at https://gitlab.com/drupal-infrastructure/gitlab-acceleration/user-storie.... I'd like to explore that and learn what is planned. |
9️⃣ @quietone "Adding a request to search for duplicate issues to https://www.drupal.org/node/add/project-issue/drupal"
| quietone | With a link to https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett... |
| larowlan | I think that's a good idea. There's a feature request somewhere to add an autocomplete like you see on stack overflow |
| dww | In principle, I’m in favor. This has been an ongoing thing for a long time. Years ago, we changed it so project pages only link to their issue queues, not a direct “submit new issue” link. Etc.
However, we’ve already got a rainbow wall of messages on that form. I doubt people read any of it as is. I fear if we add more, it’ll only contribute to the “notice overload” |
| dww | The other problem is we’re probably moving to Gitlab issues in the “near” future, and we’ll probably have less control over anything like this. I’m reluctant to put energy into optimizing / improving this tool that’s slated for the trash can... :wink: |
| Kristen Pol (she/her) | Even with the cutover I'm in favor of this one assuming gitlab issues will be at least a few months out which I assume is the case but I agree we probably need to tighten the message up... IMO less text and numbers are good, e.g.
It can link off to more thorough instructions for those who are inclined to read it (edited) |
| quietone | Yes, keep it very simple for both the developer making the change and the reader. Even if it a small percentage that search and find a duplicate to use - it saves the community the time of the person doing the triage. |
| quietone | FYI, about Gitlab templates, https://gitlab.com/drupal-infrastructure/gitlab-acceleration/user-storie... |
| larowlan | can you edit the title? not sure 'crap' is appropriate - suggest %s/cut down on crap/increase the quality of/ (edited) |
| quietone | Yea, I didn't like it either but I was following directions of others so left it Because of your prompt I have changed it. (edited) |
1️⃣ 0️⃣ @quietone "Selecting target issues for this fortnight"
| quietone | Following on discussion #8 #3246131: Meeting of the Bug Smash Initiative 2021-11-09 |
| quietone | What do we agree on in that thread? |
| quietone | Option 5 by dww was 'to pick no more 4 targets in the period' and lendude liked that if the issues were random. A random critical, a random major and 2 others to create a list of 4 to focus on for the fortnight. I think that is worth trialing. |
| larowlan | I agree |
| lendude | So try the random? When should we do the drafting of issues? During the meeting as one of the points? |
| dww | Sorry I didn’t follow up on any of this until now. The proposal was to use the “nominate pet issues” thread to gather nominations during the meeting. Then there was the idea of a poll to formally vote on the candidates and narrow it down. Perhaps run the poll after the meeting closes for the following 24 hours? |
| dww | Len was concerned that voting would lead to hard feelings and wasted effort. My sense is that participants in this channel are good natured and collaborative. I doubt there’d be weirdness and anger. But who knows? |
| dww | However, reflecting on all this a bit more, I wonder if this whole thing would be a waste of effort. :wink: |
| dww |
|
| Kristen Pol (she/her) | I like the random targets so it's less overhead |
| quietone | Responding to dww above
Like everything we are experimenting to find what works. I think a trial run is worth doing. |
| dww | (Sorry, been offline since shortly after I posted the above, just replying now)...Re: 4 I meant specifically the time spent picking targets, not working on the targets themselves. I totally agree smashing a target is still bug smashing. I meant the metawork of picking, voting, etc.All that said, I'm in favor of both experimenting and having targets. I'm just afraid I'm over-complicating things. So I'm trying to own that fact and make it clear I'm a) not attached to any particular approach and b) don't expect other folks to have to spend too much overhead on this... |
| quietone | @dww, thanks for the clarification. I didn't get your intention. |
Participants:
quietone, kim.pepper, marcvangend, lendude, darvanen, larowlan, dww, Kristen Pol
Comments
Comment #2
griffynh commentedComment #9
quietone commentedComment #11
quietone commentedComment #12
quietone commentedComment #14
quietone commentedIn the following meeting dww pointed out missing comments from discussion #10. As he points out this raises a topic for discussion at a meeting about how to handle comments post the 24 hours of the meeting. But, for now, since we have no agreed practice I am adding the comments referred to.
Comment #15
dwwThanks for adding that. Looks great. RTBC.
Comment #16
griffynh commentedThere was no further request for changes at the next meeting.