Active
Project:
Contribution Events
Component:
Planning
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2023 at 17:46 UTC
Updated:
12 Jan 2026 at 00:26 UTC
Jump to comment: Most recent
Problem/Motivation/Idea
Some contributed projects (modules/themes) have Drupal 10 patches that work fine and have been RTBCed, but the projects are not actively maintained, so the patches aren't getting merged. Others, had their patches merged, but there is still no official release.
Proposed resolution
Rally the community to adopt these projects to, at minimum, merge the patches and, ideally, to create a new release. For those that have D10-compatible dev branches, we should politely request the maintainer create an official issue and, if not done in a timely manner, consider going through the abandoned project process. If you decide to follow this process, make sure you PM all maintainers that can be contacted to make them aware of you offer to maintain, and put the details (when and who) in the issue summary.
Remaining tasks
This issue is for organizing all the pieces... tasks will get updated as needed and child issues will be created.
Recruit volunteersFind target projects and create spreadsheetCreate documentation for processStatus updates during #d10readiness meetings- Status updates via #d10readiness channel as appropriate
- Ideally, update spreadsheet with status at least every couple weeks
- Gather stats regularly and share in Slack channel
Comments
Comment #2
markdorisonI know of some projects that have committed D10 patches, but have not cut a release that includes those D10 commits. Would those be considered in scope here? I am hoping the answer is yes!
Comment #3
kristen polYes, I think we should also target those. At minimum to more directly (gently) ping the maintainers :) [I updated the summary]
Comment #4
kristen polAdded links to child issues.
Comment #5
kristen polLinked another child issue. First 3 tasks are "done" though can continue to be tweaked so chime in on the issue, ping us in Drupal Slack, or comment on the spreadsheet.
Comment #6
ressaI am not sure if this is the correct place to add it, but Permissions by Term is not ready for Drupal 10 and #3316032: Searching for co-maintainers.
Comment #7
heddn@ressa I added it just now to the spreadsheet.
Comment #8
ressaPerfect, thanks @heddn.
Comment #9
ressa@Anybody left a comment in #3290031: Automated Drupal 10 compatibility fixes
So perhaps Theme Switcher Rules can be added as well?
Comment #10
ressaLast commit to Flexfield was in November 2021, maybe it can be added as well?
Comment #11
kristen polThanks @ressa. These have been added to the spreadsheet: https://docs.google.com/spreadsheets/d/1jUv6jkLM9u49hqCcgf-4W9bIEKEhsfJ-...
Comment #12
ressaPerfect, thanks @Kristen Pol for maintaining the list.
Comment #13
markdorisonComment #14
ressaCould Glossify get added? #3297313: Automated Drupal 10 compatibility fixes for Glossify.
Comment #15
gisleThis is an important initiative as Drupal 9 is approaching EOL.
However, I've noticed that most of those following the abandoned project process by offering to help out fail to carry out all the steps required. In particular a notice about the required PM to the owner about an offer to maintain, is missing from the issue summary. If this notice is missing, the abandoned project process is stalled until this has been sorted out.
Changed the issue summary that this PM is mandatory if one is pursuing the abandoned project process.
Comment #16
kristen polWe won't be having more #d10readiness meetings going forward so please report status in the channel as appropriate. Thanks.
@gisle I updated the spreadsheet to be more explicit and to link off to more details, e.g.
https://www.drupal.org/project/contribution_events/issues/3342488#commen...
@ressa I added Glossify to the spreadsheet. Note that you can get edit access to the spreadsheet if you want to add more yourself.
Comment #17
kristen polI updated the task list.
Comment #18
kristen polLinking to child issue from issue summary.
Comment #19
kristen polAdding child issue for gathering stats.
Comment #20
rajab natshahAdded 2 child issues for 2 modules.
Following with Kristen's template.
Comment #21
kristen polThanks!
Comment #22
gisleCorrected small typo in the issue summary.
Comment #23
kristen polThe AI initiative has consumed me so unassigning