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.
➤ Usually happens every other Monday at 19: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/3189403`
➤ *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.| catch | Nat, core committer, from the plague island. |
| xjm | :wave: |
| baddysonja | Hi - i’m only here to listen and learn as I’m curious about what is being worked on :slightly_smiling_face:. Hi from Germany :flag-de: |
| Neslee | Neslee and happy new year |
| shaal | Ofer Shaal :sunglasses: :wave: |
| Gábor Hojtsy (he/him) | Hey :slightly_smiling_face: Drupal 10 coordinator from Hungary :slightly_smiling_face: (edited) |
| fathershawn | Hi :wave: |
| moshe | hiya :wave: |
| larowlan | :wave: |
| hansa11 | Hello! :wave: |
| joshmiller | Hello :wave: Just lurking and hoping to find something I can do to help out. |
| catch | Symfony 5/6 compatibility: #3161889: [META] Symfony 6 compatibility |
| shaal | Drop IE11 support from Drupal 10.0.xIt seems like it's going to happen, where and how do we manage the work involved removing IE11 ?(removing polyfills? updating libraries? utilizing newer css? etc.) |
| Matroskeen | I’m probably late, but I was wondering if it’s allowed to apply changes like this in Drupal 10: [#2991232]Otherwise, we should probably mark that issue as “Won’t fix”. |
| Gábor Hojtsy (he/him) | https://dri.es/drupal-10-target-release-date-and-drupal-9-end-of-life is still accurate from July |
| Gábor Hojtsy (he/him) | the catch is that we are targeting feature development for Drupal 10 to finish up by Drupal 9.3's alpha release, so we can get people test and make contrib projects compatible with things like the replacements of jQuery UI components, CKEditor 5, etc. |
| Gábor Hojtsy (he/him) | https://www.drupal.org/about/core/policies/core-release-cycles/drupal-co... is the release cycle dates |
| Gábor Hojtsy (he/him) | that has Drupal 9.3.0-alpha1 released on week of October 25, 2021 (edited) |
| Gábor Hojtsy (he/him) | which is practically the date we are looking at for feature additions like CKEditor 5, etc. |
| Gábor Hojtsy (he/him) | Also I posted my DrupalCon slides at https://twitter.com/gaborhojtsy/status/1337358597685211137?s=20 with more details |
| Gábor Hojtsy (he/him) | @xjm proposed this topic on the meeting issue :slightly_smiling_face: |
| Gábor Hojtsy (he/him) | Related issues are:#3039047: Adopt php-http/guzzle6-adapter 2.x to get PSR-18 support without losing Guzzle's async supporthttps://github.com/guzzle/psr7/issues/327https://github.com/guzzle/psr7/...(edited) |
| xjm | So the latest status here is that I think we are waiting for them to review the merge of 1.x into main |
| xjm | Because at least as far as I understand (and this could use confirmation) we cannot replace Diactoros without the PSR-17 support. |
| xjm | Can't even begin to, really |
| xjm | It could be useful for someone to try to prototype against the main branch of their PSR-7 repo, but OTOH we had such trouble even with an RC of Symfony |
| Gábor Hojtsy (he/him) | @catch suggested this topic |
| Gábor Hojtsy (he/him) | #3161889: [META] Symfony 6 compatibility |
| catch | I think at the moment it's mostly a case of the sub-issues needing reviews. |
| xjm | Any particular priorities or blockers? |
| Gábor Hojtsy (he/him) | Anyone interested to write tests for #3185603: [Symfony 5] Symfony Constraint plugins are not strictly Drupal plugins? :slightly_smiling_face: |
| catch | Maybe #3187074: [Symfony 5] Services are private by default too |
| Gábor Hojtsy (he/him) | This team now has a channel at #ckeditor5 and meeting every other Thu (next one on Jan 14th at 15:30 UTC) |
| Gábor Hojtsy (he/him) | I am not aware of progress here since the last Drupal 10 meeting we had (edited) |
| xjm | https://drupal.slack.com/archives/C01GWN3QYJD/p1609750533031000 looked of interest |
| Gábor Hojtsy (he/him) | Piotr is the tech lead of CKEditor 5, and he promised to work with us, so looking forward to these discussions :slightly_smiling_face: |
| Gábor Hojtsy (he/him) | All of these have prototyped replacement libraries. In case of Backbone even a Vue.js based and a vanilla JS |
| Gábor Hojtsy (he/him) | #3067261: [Plan] Remove jQuery UI components used by Drupal core and replace with a set of supported solutions has links to issues for jQuery UI |
| Gábor Hojtsy (he/him) | #3051766: Deprecate and replace jQuery Joyride (for tours) is for tours |
| Gábor Hojtsy (he/him) | #3145958: [META] Re-evaluate use of Backbone.js in core is for backbone |
| Gábor Hojtsy (he/him) | all of them need feedback and more people being involved :slightly_smiling_face: |
| Gábor Hojtsy (he/him) | https://docs.google.com/document/d/1OBOZQxHA1qTXqLwVke6lX7PWJiQrpGc2Hxa1... is a good index of all the JS issues |
| xjm | We could definitely use more reviews on the Dialog and Autocomplete replacements |
| xjm | Really thorough manual / UX / a11y testing and really thorough code review |
| xjm | Anyone can help with those ^ #3076171: Provide a new library to replace jQuery UI autocomplete |
| xjm | Then for the Backbone issues, the next step is to have consensus and signoff on which approach to use, from stakeholder maintainer groups. (E.g. folks +1 on Vue, for example.) |
| xjm | (With the specific scope of using Vue to replace Backbone as a dependency, not anything related to decoupled frontends or such) |
| Gábor Hojtsy (he/him) | @shaal raised this |
| Gábor Hojtsy (he/him) | #3155358: [policy, no patch] Drop IE11 support from Drupal 10.0.x |
| catch | I think we're at the point where we can open sub-issues for this one, although it is still awaiting sign-offs (but afaik those people all agree we should do it). |
| xjm | The a11y team asked for longer to give feedback on it |
| xjm | So I think that's what we're blocked on still -- @lauriii might have more up-to-date info |
| Gábor Hojtsy (he/him) | Discussions continued on the database front |
| Gábor Hojtsy (he/him) | in particular #3109340: [policy] Decide whether to require json support for all database drivers for Drupal 10 |
| Gábor Hojtsy (he/him) | @daffie went ahead and opened issues for all specific databases Drupal 9 supports |
| daffie | @Gábor Hojtsy (he/him) I have a question to you about setting the new minimum version for support in D10. For how long will we have D10? a.k.a when will D11 be released. If we have D10 for just 2 years then I am more willing to set the minimum versions for databases not as high as possible, then when we will have D10 for 5 year or longer. Hoping you understand my point. |
| Gábor Hojtsy (he/him) | @daffie good question, it depends on our dependencies primarily :slightly_smiling_face: we aim to update to Symfony 6 compatibility if at all possible, in which case November 2027 would be for the sake of Symfony (https://symfony.com/releases/6.4) — however its hard to imagine other dependencies would also be supported that long … |
| daffie | @Gábor Hojtsy (he/him) Could you make a guess? |
| Gábor Hojtsy (he/him) | @daffie based on November 2027 it will not be longer than 5 years at least :smile: Since we are just replacing various frontend libraries (jQuery, etc), it really depends on what we replace them with and their support |
| Gábor Hojtsy (he/him) | also its really hard to tell what kind of changes will be in Symfony 6 and how breaking they will be |
| daffie | ok. We shall just have to wait how it turns out. |
| daffie | @Gábor Hojtsy (he/him) I have also an other policy question. It is about #3190516: [Policy] For PostgreSQL require that the pg_trgm extension is not only installed, but also created.. If it gets the ok for D10, then can we also do it for D9? |
| Gábor Hojtsy (he/him) | @daffie that would be a release manager question IMHO :slightly_smiling_face: we regularly schedule PHP version requirement updates as PHP moves very fast now, but databases are a bit of a different question especially if data migration is involved |
| daffie | My apologies. I thought that were a release manager. |
| Gábor Hojtsy (he/him) | catch and xjm are :) |
| Gábor Hojtsy (he/him) | I don’t believe there was any movement on this recently, if you are interested in the concept #3050384: Provide a starterkit theme in core has a video from @lauriii :slightly_smiling_face: basically themes would not inherit live from a base theme but fork a starterkit theme |
| lauriii | Planning to work on this soon. Let me know if you’re interested in helping |
| hansa11 | @lauriii I'd love to help :slightly_smiling_face: |
Comments
Comment #2
xjmTopic to discuss: Guzzle 7 and PSR-17 (not PSR-18 which is purportedly already adopted in Guzzle 7). Related issues:
Comment #3
gábor hojtsyUpdate time to 19:00 UTC which it is in fact.
Comment #4
andypostAnother topic to discus - blocker for help topics #3087218: Help searches fail if site is not fully indexed, and users do not know why
TL'DR Help topics duplicates approach from locale module to run batch after module install (search indexing if the core's search module enabled at the moment of help topics install)
Maybe for D10 better to introduce a common approach to run post-install batch jobs and new batch builder #2875151: [META] Implement Batch API as a service
Comment #11
gábor hojtsyAdding logs.