Our lead community developer, Alona Oneill, breaks down highlights from Drupal Core Initiative Meetings this past June. 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 insights on, we encourage you to get involved.
CMI 2 Initiative Updates
Status of CMI 2
Major patches are being reviewed and hopefully will land after it gets a change record.
Next steps for CMI 2
- A final review from Lee to be completed.
- The config environment module, different configuration in different environment, is in production.
- At a stage where nothing is needed from Core Cm or FM’s.
Status of Composer
A patch went in to use composer as a dev requirement and we're on the road to making core test builds and upgrades. The scaffolding patch was reviewed and moved to RTBC.
Next steps for Composer
- Need core maintainers to review the testing framework from miles 23.
- Need core team to help with the scaffolding issue.
There are two major patches being worked on at the moment:
- Track the workspace of a revision in a base field and convert the workspace_association entity type to a custom index:
- Changing workspace associations to field from entity.
- Adding custom indexing.
- This patch will remove an entity type from core.
- Add the ability to create sub-workspaces in order to enable the dev -> stage -> live workflow for content:
- The ability to create sub workspaces is required for implementing workspace merging. Workspaxe merging needs an issue/patch.
Would also like to see the issue to allow 'syncing' content to be updated in content moderation without forcing the creation of a new revision be updated. Content moderation is working with this as it allows people to moderate any content within the workspace via the user interface.
Upgrade path is on hold until this approach is validated or approved. Workspace merging is currently in need of an issue.
Next Steps for Workflow
Get release managers and fm review is needed on issue #3062434. Get FM review on issue #2803717 because it currently needs additional input. An issue for workspace merging also needs to be created. We're trying to get the first 2 issues into 8.8 (and 8.7).
Drupal 9 Updates
- Drupal check got a release last week by mglamman with all deprecation error messages.
- Upgrade Status has new features in dev that categorizes error messages on actionability. The action items are, supported, deal with it now, not supported, deal with it later, or deprecated for Drupal 9.
- Explaining in the UI of the module to help them engage with contribution maintainers.
- There is low-level planning in the works to:
- Identifying work to manage dependencies and defining the process to do this work.
- Issues related for info:
- We are asking for investment from Acquia to complete some of the work.
- Core jQuery UI discussions are continuing.
- Symfony 5 branch is now open! The branch requires a min php 7.2. For Symfony 4 the php requirement is 7.1.
Drupal 9 Blockers
Cannot complete deprecation list for 8.8 because November is when we’ll get the list from Symfony for the SF5 release.
Next steps for Drupal 9
- Continue to keep tabs on what is happening with Symfony 4 and 5 changes.
- Review the list of items being deprecated for 8.8 with RM/FM.
- Make a decision on if the team goes with Sf4 or Sf5.
- Confirmation on the resourcing ask for Drupal 9 work.
- Confirming the front end deprecation process.
- Identifying critical path items and sequencing for Drupal 9 work.
We have one group working on admin ui theme, Claro. There is a lot of contribution progress from both front-end developers and designers. The Alpha 3 release of Claro was released in the middle June.
Another team is working on react-based decoupled admin ui, however there is not much momentum at the moment. So far, a component library has moved forward with limited resources.
The team is on track for getting in 8.8, likely as a beta. This will address open issues with designers, address changes that developers need to make which have already been found, and work on get approval from RM/FM on moving the theme toolbar CSS to the Seven theme.
- At Devdays++ accessibility improvements and fixes were worked on and signed off by RM/Media team consensus.
- Drag and drop zone for file uploads was discussed at the UX meeting as the current design was causing accessibility issues.
- The plans for WYSIWYG are complete and ready to be worked on moving forward.
- Media metadata issues are now unblocked.
- Continue prototyping on the accessibility solutions to be compatible with drag/drop zone for file uploads.
- Keep working with contributors and community members to find solutions that could incubate there.
- Keep working on WYSIWYG.
- Resource and allocate people to work on metadata.
The current migration is not as user-friendly as we’d like. We need a better user experience.
There is a large list of things generated from Angie Byron on the experience:
- Running a pre-flight check will reveal if your data has an issue. We need a better way to check that issues you’d run into are uncovered and fixed before they migrate.
- Solution needs to not mess with the command line and be more intuitive.
- Working with UX to find an appropriate solution.
- Currently have 4 migration maintainers with limited additional resources. We need more people writing code!
We will continue with the multilingual upgrade path and keep working on preflight check to improve the migration experience.
It Takes A Village
Thank you for being involved in the community, we're happy to be helping spread the word about the progression of a great platform. Please check back for frequent meeting recaps to gather insights on the latest Drupal Core developments and find ways to get involved. Our community thrives when we all come together!