As our team is expanding, and many people are contributing to the Drupal community, we've been attending a variety of Drupal Core meetings. After each meeting we put together an overview or recap of key talking points from each discussion. This article breaks down highlights from meetings this past week.
You'll find that the meetings, while also providing updates of completed tasks, are also conversations looking for community member involvement. There are many moving pieces as things are getting ramped up for Drupal 9, so if you see something you think you can provide assistance on, we encourage you to get involved.
Drupal 9 Readiness Meeting
October 14, 2019
Meetings are 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 9 upgrade of their sites are also welcome.
- Usually happens every other 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 Drupal 9 Readiness Agenda anyone can add to.
- The transcript will be exported and posted to the agenda issue.
- Transcript will be exported and posted to the agenda issue. For anonymous comments, start with a
emoji. To take a comment or thread off the record, start with a 
emoji.
During this week's meeting, the following items were discussed:
- Drupal 9 branch is open! Next steps on it especially in the next two weeks.
- Use new core_version_requirement in all module and theme info and yml files so that 9.0.x can be installed
- [META] Requirements for tagging 9.0.0-alpha1
- Install profiles do not support multiple core branch compatibility
- [Meta] Make 9.0.x branch pass testbot
- drupal 9.0.x-dev
- Remove test dependencies on localize.drupal.org
- Drupal 8.8.0-alpha1 commit freeze is nearly upon us! Update on D9 readiness issues that we need in 8.8. (jQuery, polyfills, Doctrine, others?)
- Fork jQuery UI components still used by core in 8.8, and provide them as backwards compatibility layers while we deprecate the remaining components. It is blocked on four issues, listed in the IS: Deprecating components core doesn't use (just needs some contrib module changes), PopperJS (RTBC and awaiting committer review), Sortable (ditto), and datepicker (currently undergoing a11y review). We are still targeting those four issues for 8.8.0-beta1 at least and alpha1 if it works out.
- Deprecate (in 8.8) and remove (in 9.0) polyfills that are no longer needed
- Doctrine no longer supports SimpleAnnotationReader, incorporate a solution into core. We're trying to figure out how we properly document the MIT license or copyright info when we're forking and modifying one of Doctrine's APIs into core.
- Fix 'The Drupal\migrate\Plugin\migrate\process\Migration is deprecated in Drupal 8.4.0 and will be removed before Drupal 9.0.0. Instead, use Drupal\migrate\Plugin\migrate\process\MigrationLookup'. This issue should be in 8.8 for surfacing deprecations.
- DrupalCon Amsterdam plans!
- Gábor Hojtsy will try to support a Drupal 9 contrib contribution event, looking for drupal.org projects. To apply for help with your project, do so via Twitter.
- We’ll be working on removing core deprecated APIs too. We’ll need to make sure not to step on toes for both. Also the ongoing novice work to make sure change records and trigger errors are correctly included for core deprecations
- Tooling for JS deprecations
- Core now triggers deprecation info to the JS console. Trigger deprecation notifications on JavaScript deprecations to notify developers that deprecated code is being used.
- Deprecated scaffold files
- We currently have two sets of scaffold files in core right now as per:Drupal "scaffold" files now duplicated in drupal/core and Add core scaffold assets to drupal/core's composer.json extra field.
- When contrib should specify `core_version_requirement` key?
Out of the Box Initiative Meeting
October 15, 2019
- Allow embedding media in CKEditor in Umami.
- Umami’s language-switcher as a drop-down menu.
- Configure Umami to use Layout Builder to deliver original recipe content type designs
- Use Media images in Umami demo meeds review.
- Keith Jay got few issues to resolve with recipe video, but he’s working on it.
- Ofer Shaal suggested to create an issue for a video as a placeholder, while it’s beig fixed.
- Ofer Shaal showed a quick demo about DIFFY and how to test patches there.
Migration Initiative Meeting
October 17, 2019
This meeting:
- Usually happens every Thursday and alternates between 14:00 and 21:00 UTC.
- Is for core migrate maintainers and developers and anybody else in the community with an interest in migrations.
- 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 migration meeting agenda anyone can add to.
- Transcript will be exported and posted to the agenda issue.
- For anonymous comments, start with a emoji. To take a comment or thread off the record, start with a emoji.
The following issues were reviewed at this week’s meeting:
- Migrate D6 and D7 node revision translations to D8
- Menu language not properly migrated from D7 localized menu links
- Hide and disable Drupal Migrate Multilingual
- Migrate D7 i18n taxonomy term field translations
- Add checkrequirements to VariableTranslation source plugin Primary tabs View(active tab)
- getHighestId() should not fail when there is a destination id with type string
- Migrate UI - use human-friendly module names on the Review form
- Benji volunteered to review this issue by next week, and bring it up in the Usability meeting if needed
- Optimizations to the substr process plugin
- Move existing assertions of IdConflict page to new test files
- migrate_drupal_migration_plugins_alter() should only alter definitions that exist
- Source count caching does not work for SQL sources
- Remove the "cckfield" plugin type from the migration system
- SQL source plugins: allow defining conditions in migration yml
- Show migrate plugins on the Migrate UI lists
The Migrate maintainers were pretty happy that we will be able to remove some long-deprecated APIs now that Drupal 9 is really here (in the sense that the branch has been opened).
Drupal Core Cross Initiative Meeting
October 17, 2019
UX + Admin UI
Status:
- Claro just got into 8.8 (congrats!!!)
- Views UI issue was resolved (yayyy)
- Initial Roadmap defined
- All alpha/beta criteria met for 8.8 and reviewed/approved/committed.
Blockers:
There are currently no blockers for UX / Admin UI.
Next steps:
- Planning Drupalcon sprints
- Next design/development goals for Claro (for stable roadmap and release)
Workflow
Status:
- Workspaces just got into 8.8 (congrats!!!)
- Framework / PM review completed
- Still working on sub-workspace capability, needs review & validation (last issue prior to the stable release)
Next steps:
- One remaining issue, adding sub-workspace capability to be completed
- Final issue to be filed for stable review
Media
Status:
- We discovered a Stable blocker last week on a front-end issue which needed immediate attention on a large patch (in a good state currently, main concerns addressed)
- Issue: Presentation items were in the module code
- All other issues are resolved
Blockers:
Only Stable blocker left is Move some representational classes in Media Library to Classy and others to Seven and/or Claro, as appropriate.
Next steps:
- Complete work on last blocker issue.
- FE Sign off
- Commit to 8.8
AutoUpdates
Status:
- A button added that will automatically update your drupal to the next recommended version
- Identified an issue: Module requires installation via composer will break the ability to update the next time.
Blockers:
- Must resolve installation issue referenced above
- Build test framework
Next steps:
- 3 issues need help:
- BuildTestBase->copyCodebase overly aggressive in exclusions needs commit.
- Add access rules for build tests needs commit.
- BuildTestBase->standUpServer always starts new server needs review.
CMI2
Status:
- Added the ability to exclude modules from core, contrib modules can now use this new API.
- Didn’t make quite enough progress on the use cases for config environment module. (This being in Alpha makes the cmi2 ineligible for core 8.8 release, it’ll be in the queue for 9.1 as a result.)
Blockers:
Config env module
Next steps:
Continue working on the config env module and its plan.
Drupal 9
Status:
- D9 branch now has 7.2 php version
- Need vendor updates & reroll the symfony 4 patch (later today)
- Continuing discussions on Twig dependencies related to Symfony ⅘ versions
- Multilingual migration path needs review on 2 key issues:
- Drupalcon Contribution Day: #ImadeDrupal9! Spread the word to use the hashtag.
- Portions of doctrine and jQueryUI have been forked into core due to the fact that we couldn’t get everything deprecated.
- Working on a tutorial.
Blockers:
- Resolve dependency issues for twig, php, symfony, etc.
- D9 cannot be installed on a non-english language for now
- Resolve must-have blockers in multilingual migration upgrade path.
Next steps:
- Reviews for the vendor patch, twig2, & symfony patch
- Removing all the deprecations that have piled up in RTBC queue
- Confirm the alpha requirements
- Need review on Migrate D6 and D7 node revision translations to D8.
- Need review on Migrate D7 entity translation revision translations to D8.
- Continue working on must-haves.
- Hide/Disable module.
- Need your help to promote the contribution event at Drupalcon!
- Share Gábor's post.
- Promote via Twitter!