fidzu : cms

The 2025 Annual Maintainer Check-In is now complete, a huge thank you to everyone who responded and to all the maintainers who continue to keep Drupal core moving forward.

As part of this process, we've confirmed that a number of Drupal Core subsystems and topic areas are currently without an active maintainer.

If you've ever thought about stepping into a maintainer role, or co-maintaining alongside others, now is the perfect time to get involved.

Why maintainers matter

Maintainers play a key role in ensuring the quality, stability, and momentum of Drupal core.

Maintainers help shape the direction of their subsystem or topic area, guide contributors as well as triage issues and review merge requests.

You don't need to be a long-time contributor, if you've been active in a related area or are keen to grow your involvement, we'd love to hear from you.

Learn more about the maintainer role:

• Drupal core maintainer roles and responsibilities
• Core governance and subsystem overview

Areas currently without an active maintainer

Subsystems

• Authentication and Authorization
• Automated Cron
• Ban
• Bootstrap
• Content Moderation
• Content Translation
• Cron
• Database Update API
• Filter
• Image
• Inline Form Errors
• Installer
• Language
• Lock
• Mail
• Markup
• Menu UI
• MySQL DB driver
• Options
• Path
• PostgreSQL DB driver
• Request Processing
• Settings Tray
• Sqlite DB driver
• System (module)
• Token
• Workflows

Topics

• Documentation

How to express interest

If you'd like to maintain or co-maintain one or more of these areas:

• Comment on the Seeking subsystem and topic maintainers for open positions issue.
• Include your name, Drupal.org username, and a short note about your experience or interest area.
• Or, reach out directly via Drupal Slack to @griffynh.

What happens next

Once interest is expressed:

• A public issue is opened in the Drupal core issue queue for each applicant so the community can provide feedback.
• The Leadership Team reviews each application, discusses any concerns with the applicant directly, and offers support where needed.
• Following this, a member of the Core Leadership Team updates the issue with the outcome and adjusts the issue metadata.

Thank you to everyone who contributes as a Drupal maintainer, your work is what keeps Drupal core secure, stable, and evolving.