Agenda items

Standing items

  • Who is here
  • Any other suggested topics
  • Wins / Thanks / Blockers
  • Statistics and functionality update. X new bugs were created last month. 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 month?

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 :wave: Hola, Griff, Aus
larowlan hey
ambermatz Hello
jibran What is "here"? In the grand scheme of thing does "here" matter? I'm here but am I "here"? Or "here" is just a construct of our imagination to let us believe that we are present "here" in this moment right now.
urvashi_vora Hello :wave:
lendude Morning
quietone Hi
Sourabh Jain Hello
catch :wave:
dww Derek :wave:  Feliz Carnaval / Happy Mardi Gras :tada: :drum:

0️⃣.5️⃣ If you could wave a magic wand and have one thing added-to or fixed in drupal what would it be?

Griffyn Heels One that comes up a lot for my clients is being able to duplicate layout builder pages/configurations. So probably that.
larowlan For me it would be time to finish Field Union (aka fieldable fields)
jibran Get rid of core/lib folder in favor of core/src folder. :smile:
jibran Allowing core ER field to support multiple entity types so that i don't have to maintain DER anymore :stuck_out_tongue:
quietone #3319843: [Meta] Fix coding standards in core
dww This is such an impossible question :joy:  I don't even know where to begin...

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 How do we feel ‘The One’ idea is going?

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

dww We smashed a major in 6.5 hours: https://drupal.slack.com/archives/C014QES6HSQ/p1706828395783309?thread_t...

2️⃣.4️⃣ Approve last fortnight’s minutes

Griffyn Heels We’ve got a few to close:#3408347: Meeting of the Bug Smash Initiative 2024-01-09(edited)
ambermatz For credit, are we crediting anyone who says “they are here” or just those who participate in a discussion?
Griffyn Heels The user needs to have participated in a thread other than the hello thread.
Griffyn Heels Did I miss any credits?
ambermatz Makes sense. I don't think so, but I had just started to check and wanted to be sure of the policy. (I'm dusting off my bugsmash help skillz. :slightly_smiling_face:
ambermatz Ok, I closed all of those, and added credit to @Griffyn Heels on 2 because creating these meeting issues is a task in and of itself. Thanks all!
Griffyn Heels Cheers mate :clap:

4️⃣ Update on the one :o:

larowlan Status is needs work after a new review

6️⃣  PMNMI issues that we can close this fortnight

larowlan Would be good to have a table working on just this at the DrupalSouth code sprint, should be able to clean up a chunk of issues
quietone Good idea!

7️⃣ @Griffyn Heels “How do we feel ‘The One’ idea is going?”

Griffyn Heels It seems to be getting some traction in threads, but is it doing what we were aiming?
Griffyn Heels Started from this thread: https://drupal.slack.com/archives/C014QES6HSQ/p1699934660328839
larowlan The problem is this one is a hard one
larowlan we're making progress each week, but this is a really old issue
Griffyn Heels Is it worth staying with a hard one or moving on?
larowlan Good question
Griffyn Heels On one hand, it’ll likely just sit there, but it limits ‘The One’ to senior Drupal contributors
larowlan Sorry, should clarify, its not hard technically, its hard because of the age and the number of comments/reviews
larowlan And to be honest its not a but, its a feature request
larowlan And that could even be our resolution here but it just lobs it over the fence
ambermatz IMG_0185
lendude And it’s a feature that has a contrib module :shrug:I like the idea of the one, but not very motivated to work on this oneBut I think the nature of picking the oldest issue will always lead to hard issues one way or another, if they were easy and worth doing, they would be in by now
quietone I didn't realize there was a contrib module. Still, to me, this seems like something core should be doing.
catch I think it's fine to move it to a feature request especially after significantly moving it on.
catch If we don't want to move it to a feature request, should we consider making 'the one', 'the two'?
catch That would bring in https://www.drupal.org/project/drupal/issues/92944, based on https://www.drupal.org/project/issues/search/drupal?project_issue_follow...…]xt=&assigned=&submitted=&issue_tags=&&&order=created&sort=asc
larowlan Based on the conversation here it feels like there's broad support for making it a feature request, I'll do that today and record the participants here
dww Yeah, a feature request is more accurate.  It'd still be great to finally fix/add it!  It'd be a pity if we got this close and then lost momentum by recategorizing it...

Participants:

Griffyn Heels, larowlan, jibran, quietone, dww, ambermatz, lendude, catch

Comments

griffynh created an issue. See original summary.

kostyashupenko’s picture

Kind of old problem (since 2017) which is quite important and still not fixed https://www.drupal.org/project/drupal/issues/2856572#comment-15395620

griffynh’s picture

Issue summary: View changes

larowlan credited catch.

larowlan credited dww.

larowlan credited jibran.

larowlan credited Lendude.

larowlan credited quietone.

larowlan’s picture

Version: 10.2.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

amber himes matz’s picture

Status: Active » Fixed

Thanks all for your participation in the Bug Smash meeting.

Status: Fixed » Closed (fixed)

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