Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.:zero: 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.
| griffynh | Hola :wave::skin-tone-2: (edited) |
| Luke Stewart | Kia ora :wave: |
| mohit_aghera | Hello :wave: |
:one: Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.
:two:.:one: Wins - what wins have you had since the last meeting? Share your successes!
:two:.:two: Thanks - a space for callouts to other contributors who’ve helped you.
:two:.:three: Blockers - what’s getting in the way of your issues / goals
:three: Core bug statistics - current state of open bugs
:four: Focusing on RTBC
| griffynh | We discussed this in the last meeting https://drupal.slack.com/archives/C014QES6HSQ/p1770687319590119 |
| griffynh | When we say that do we mean this? https://www.drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&proje[…]tus%5B%5D=14&version%5B%5D=main&issue_tags_op=%3D&issue_tags= |
| griffynh | What’s the goal here, to get everything to RTBC so that the core committers can review and merge if approved faster? |
| catch | For me I’d try to look at it this way (only bugs, status change ascending) https://www.drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&proje[…]D&issue_tags=&&&order=field_issue_last_status_change&sort=ascIdea would be to triage what’s in there to make sure it’s ‘actually RTBC’ then either move it to needs work if it’s not, or if it needs minor things like issue summary updates (especially for steps to reproduce or proposed resolution) try to fill those in. Then when a committer looks at it, it’s more likely to get committed rather than moved to needs work. |
| catch | An example of one that’s stuck is[#2486267]#comment-16450028 where it’s possible it will break something else and I tagged it for FEFM review. In this case it would be worth someone pinging the FEFMs since it’s been in that state for a while. But also a fresh set of eyes on it might be able to think through what the implications are a bit more too. |
| smustgrave | FYI with regards to that I’ve pinged the frontend framework managers many times but maybe someone else would have luck |
| Luke Stewart | Is there a good checklist that we can work through to help us address what’s ‘actually RTBC’ |
| and perhaps we should bookmark that? | |
| Is this still most recent -> https://www.drupal.org/community/contributor-guide/task/review-a-merge-r... | |
| smustgrave | @griffynh what if we do both? There are only 27 bugs in RTBC (2 we’ve already looked at). Problem with RTBC is not everyone can close threads, assign credit, or some small stuff. PMNMI we may slowly pause as we’ve done through almost all that are 3 months or older so those may skip a few days.So one notification can be for last updated 2nd notification 12 hours later for RTBC |
| smustgrave | Everyone can still review RTBC just mentioning some limitations. And those that can do that stuff can’t rerun random failures |
| griffynh | Sure, so what’s the proposed alternative to RTBC? |
| smustgrave | I liked the last updated one personally |
| smustgrave | But if we wanted to pivot to something else not opposed. One day I want to try and do new bugs thinking the reporter is actively around |
| griffynh | I’m open to updating the daily notification to be 1x RTBC review and 1x Latest Updated? |
| smustgrave | +1 from me |
Participants:
griffynh, catch, smustgrave, Luke Stewart,
Comments
Comment #2
smustgrave commented