Meeting will happen in #d10readiness on drupal.slack.com.

Hello and welcome to this Drupal 10 readiness meeting!

This meeting:
➤ Is for core and contributed project developers as well as people who have integrations and services related to core. Site developers who want to stay in the know to keep up-to-date for the easiest Drupal 10 upgrade of their sites are also welcome.
➤ Now happens every Monday at 18:00 UTC.
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Has a public agenda anyone can add to: `https://www.drupal.org/project/drupal/issues/3303415`
➤ *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

0️⃣ Who is here today? Comment in the thread below to introduce yourself.

Kristen Pol (she/her) Kristen, California :wave:
andypost Andy, php82 pusher
Ilcho Vuchkov (vuil) Ilcho Vuchkov, Bulgaria (EU), Following the updates.
Björn Brala (bbrala) Late and on vacation :grinning:
longwave Dave, UK, late as usual
kimb0 Kim, AU much later
dww Derek @ TEN7. Even later. :joy:
shaal Ofer Shaal, very, very late
atul ghate Hello, Atul from India.
akshaydalvi212 Hello, Akshay from India.
omkar-pd Hello, Omkar from India

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.

Kristen Pol (she/her) https://drupal.slack.com/archives/C03FH8GTB1A/p1660585412685379
Kristen Pol (she/her) I tried to have a coworker help in this initiative a couple weeks ago but they didn't find anything “actionable” when looking for Drupal 10 tagged issues. How do you suggest people help who aren't regular initiative participants?
andypost on Aug 18 last PHP 8.2 beta 3 coming, still 110 failed tests and container serialization issue

2️⃣ Next Drupal 10 porting day is next week, we need more mentors! https://www.drupal.org/community/events/drupal-10-global-porting-day-aug...

Gábor Hojtsy (he/him) Raised by @Kristen Pol (she/her)
Gábor Hojtsy (he/him) cc @spleshka (he/him)
Björn Brala (bbrala) I'll be around again np, although perhaps a bit spotty regarding time
spleshka (he/him) that’s very nice, thanks @Björn Brala (bbrala)! Do you mind adding yourself as a mentor into our spreadsheet please through this form https://forms.gle/UX8e11jkXwGk9Ux29. We will provide information to attendees which hrs/timezones are covered by mentors
Björn Brala (bbrala) Sure
Björn Brala (bbrala) Need to check my calendar, but promise I'll fill in the form soon
spleshka (he/him) no worries :slightly_smiling_face: Thanks!
Björn Brala (bbrala) Submitted
Björn Brala (bbrala) More CET people though :stuck_out_tongue_winking_eye:
spleshka (he/him) :partyfrog:
spleshka (he/him) superb!

3️⃣ At contribution events, how to find actionable issues for someone who is not a regular contributor.

Gábor Hojtsy (he/him) Suggested by @Kristen Pol (she/her)
Kristen Pol (she/her) It wasn't at an event but that part doesn't matter since the answer is probably the same
Gábor Hojtsy (he/him) I think the easiest to target is to look at any site you care about (you own, your company’s, your customer, etc) and look at the projects running there. Basically run Upgrade Status there. If you find bugs in Upgrade Status, that helps already :smile: Second, you can update the projects that already have updates, and make sure your site runs fine. Then look at the projects that are not yet compatible and look for their issues.
Kristen Pol (she/her) I'm just trying to point coworkers at useful contribution opportunities
Gábor Hojtsy (he/him) I think its best if there is a personal connection interest and a growth opportunity.
Gábor Hojtsy (he/him) Its easy to see the benefit of your site becoming better / more up to date :slightly_smiling_face:
Gábor Hojtsy (he/him) And there are tools to help you find the connection to where you can also contribute to the community at the same time. Upgrade Status makes this very explicit.
Kristen Pol (she/her) I was trying to steer him towards core issues that were discussed at the initiative meeting. There's plenty to do in contributed projects which he's doing
Kristen Pol (she/her) I guess it's just harder to pop into these core issues?
Gábor Hojtsy (he/him) Core issues are always on the move yeah.
Gábor Hojtsy (he/him) So its more like who is available then to discuss with, bounce ideas off on slack I think.
Gábor Hojtsy (he/him) When I had extra time, I went to the deprecated API removals issues, those usually were fine to do randomly or mostly verify when people were done with them, but those are done now.
Gábor Hojtsy (he/him) Its always easiest to find these “issues generator” areas, where the same pattern applies to various things, so you don’t need to invent a whole new thing.
andypost ++ to deprecation, it's always challenging
andypost Also there's always phpcs and phpstan issues which is good starter
Kristen Pol (she/her) Thanks for the tips! I'll pass this along

4️⃣ PHP 8.2 beta3 is coming on Aug 18. Drupal still has 110 failed tests and the container serialization issue (edited) 

Gábor Hojtsy (he/him) Raised by @andypost
andypost there's small issue but it needs eyes about BC #3298731: Using ConstraintViolation::$arrayPropertyPath bugs on PHP 8.2
andypost primary blocker #2531564: Fix leaky and brittle container serialization solution
andypost also would be great to solve #2443351: Ensure that settings can't be serialized by not injecting them / replace stuff with container parameters. as few tests failing because of it

5️⃣ New upgrade status releases 3.15 and 3.16 from last week, highly suggest to upgrade to 3.16 :slightly_smiling_face:

Gábor Hojtsy (he/him) https://twitter.com/gaborhojtsy/status/1557824317718757378 :slightly_smiling_face:
Gábor Hojtsy (he/him) I followed up with 3.16 because there was an immediate problem with the DB version matcher class, my mistake. :see_no_evil:
Gábor Hojtsy (he/him) It is going to produce a lot better results because phpstan-drupal rule running was restored in this version, and its not been running in upgrade status for 4 months (also my mistake).
Gábor Hojtsy (he/him) I know set up more test environments for the module and email notifications of fails, so we can catch such problems in the future much earlier.
Gábor Hojtsy (he/him) That said, I think it would be good to make the bot go with the results from this weekend @tedbow :slightly_smiling_face:
tedbow I can run this tomorrow

6️⃣ 26 days to go until beta requirements need to be complete! :open_mouth:

Gábor Hojtsy (he/him) See the issue at #3118149: [meta] Requirements for tagging Drupal 10.0.0-beta1
Björn Brala (bbrala) I'll stay on the deprecation track, next week I'm home again and will keep pushing a little. Although @Spokje seems to be the main engine with @longwave
andypost I will tackle remains of 8.2 test failures
longwave yeah i am primarily picking up module and theme deprecations
Björn Brala (bbrala) Looked at the meta issue, pretty big list :sweat_smile:
catch It is a long list, but apart from PHP 8.2 and ckeditor, most of the meta issues have one remaining issue on them, so it is looking pretty close overall I think.
dww Thanks so much @longwave for helping out with the QE contrib split! I’m gonna do a final round of testing, then merge that MR and tag another release (if all goes well) tomorrow.
catch RDF is very close to being possible to deprecate, but doesn't have a contrib maintainer yet. I think I saw a thread about this, but can't find it now.
catch Handful of issues that would allow us to take some things off the list:#3303787: Move core/modules/help_topics/config/optional/block.block.seven_help_search.yml to Seven

Comments

Gábor Hojtsy created an issue. See original summary.

gábor hojtsy’s picture

Issue summary: View changes

Gábor Hojtsy credited dww.

gábor hojtsy’s picture

Issue summary: View changes

Saving notes.

gábor hojtsy’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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