2025 - Seeking subsystem and topic maintainers for open positions

@larowlan keeps nudging me about the token system but I just don't think I have the capability for that right now. I'm starting to get my head around how TypedData fits into it but honestly I already see @berdir as the pseudo maintainer of that subsystem because of the token module and his extensive coverage of that.

I've been looking at menu_ui because I have some ideas for performance improvements for large menus. Maintaining it for while might help those ideas solidify.

I've been using and contributing to Drupal since about 2010 and have a few modules I look after, the biggest of which (by install count) is token_filter. I'm a tech lead/solution architect in my day job and I attend local conferences (Drupal South), I'm reasonably well known and (I hope) approachable.

Name: Max Pogonowski
d.org username: darvanen

I'd be interested in helping out as co-maintainer for:

• Markup and/or
• Settings Tray

I'm currently maintainer for:

• Stable9 (which will probably move to contrib) and
• Umami (which will probably become a contrib recipe or site template)

I could probably take on menu_ui and options as they appear to be smaller components with less then 40 issues in each.

I currently help maintain

1. Telephone = gets maybe 1 issue every 5 years at best
2. Text = low issue count and half will go away when text_with_summary is finally deprecated
3. block_content = co-maintainer with acbramley and larowlan who are both very active

So definitely have capacity for more.

I can cover Workflows. I'm already a topic maintainer for a few other subsystems :)

Tentatively willing to raise my hand for content_moderation. Used it on a few sites and submitted some fixes. About to adopt it for another regular client, so I’ll have at least some paid time to work on fixes and changes that site might need.

Currently the only active maintainer for update.module, and unofficial co-maintainer for a bunch of other parts of core (views, date*, etc).

If anyone else is in a better position, happy to let them take it. But willing to put my name in, since I believe an over-committed and intermittently available human is better than a ? 😂

I'm happy to "adopt"

• Content Translation
• Language

I was part of the D8MI team, spoke about it a different DrupalCamps and DrupalCons, and worked on a translations service provider that had a Drupal integration I maintained for 7+ years. Currently collaborating with the teams behind the Multilingual track for Drupal CMS + Drupal Canvas.

Thanks to those who have raised their hand so far!

There are also two new positions in the process of being created and thus are not listed in the issue summary that xjm and I want to raise awareness of. One is a "dependency coordinator" maintainer and the other is a "developer tooling" topic maintainer. The titles are self-explanatory but there is more detail in the issues for those, which are added as related here. Your thoughst and interest are welcome on both of those issues.

Over the past 6 months or so I've triaged 150+ issues in the system.module queue. Many of these were incorrectly categorised, so have been relocated to other components. Others have been closed as duplicates, postponed for more info, or where possible I've tried to help to move them along, either by reviewing or working on MRs. I'm happy to volunteer to maintain this component, with the primary goal of keeping it as lean as possible.

I'd be happy to help out with:
- Authentication and Authorization
- Image

The former I've done a lot with IdMS over the years, including assisting with the transition for d.o to managed keycloak.
The later is of interest because of my performance tuning. I've stepped into that space several times in the past 4 or 5 years with lazy loading images, responsive images and image styles.

Would be good to have @heddn taking over "Authentication and Authorization", even if I feel that there should be a new initiative to rip out the current authentication system and replace it with a plugin-based system that could allow Drupal to leave Web 2.0 behind and join the modern web of MFA (!?), SSO and passkeys.

Happy to put myself forward as "dependency coordinator" maintainer, I've been doing that already with my release manager hat on, but please don't let that stop anyone else who also wants to step up here.

Just wanted to note if we got 2-3 per component that would be a dream come true.

Hi all,

I’d be interested in helping out with Cron and Automated Cron.

I've managed a couple of Drupal SaaS platforms that made heavy use of various cron-driven processes. This feels like an area where I could contribute meaningfully without overcommitting.

Hello, I'd love to take on the Documentation topic. I've been over a few documentation platforms, contribution management, and tech writing projects and think I could really help there.

Hello,

Name: Kuldeep Mehra
Drupal.org username: kuldeep_mehra27

I’m interested in helping maintain Inline Form Errors. I’ve used this functionality in multiple projects and would like to contribute to its ongoing maintenance.

Hello,

My name is Saurav Shrestha and my drupal.org username is zaurav and I would be interested in helping co-maintain the Filter subsystem. I have experience upgrading from ckeditor 4 to 5 that we did recently and feel I have a decent understanding of the filter system (and / or am willing to put in some hours to learn or be mentored about it).

Thanks!

I want to help with the documentation topic. I wrote some technical tutorials for drupalize.me https://drupalize.me/guide/layout-builder. There is more, but I don't have the links handy. I have a full-tack experience,e and I am an Acquia Triple Certified expert.

Hey There: I'm @cosmicdreams aka: Chris Weber. I'm interested in being a maintainer for the Settings Tray subsystem. My previous experience with the set of concerns that settings tray shares is my work on the Same Page Preview module. I have an interest in spending more time in this area and hopefully guide it towards having less complexity while being a more complete solution.

I think modern solutions like:

• Popover APi
• View Transitions
• HTMX

...give us an opportunity to improve. I'm eager to see that come to pass.

Name: Rodel Duterte
Username: rduterte

I work with Drupal 9/10 day to day and have been digging into core cron behavior.
I’m interested in co-maintaining the following areas, and while I haven’t maintained a module in these yet,
I’m eager to learn and help with triage, testing, and reviews:

• Automated Cron
• Cron
• Language
• Content Moderation
• Content Translation

Hi @rduterte: Thanks for your offer! I don't think the core committers would make you a subsystem maintainer without you having more history contributing to core. But don't let that discourage you! You've gotta start somewhere. 😅 If you're eager to learn, there's no better way than by doing. The core issue queue always needs help with triage, testing and reviews, in any/all components! You don't need to formally be a subsystem maintainer for that. Simply start doing it. The more (detailed, helpful) reviews you post, the more triage you perform, the more testing you do (and automated tests you write, etc), the more the core committers (and the wider Drupal community) will begin to recognize your username as someone who is positively contributing. Building up that reputation is what it takes to eventually be given the responsibilities, burdens and privileges of being a core subsystem maintainer.

Since I'm newly "in charge" of Content Moderation, I'm excited to see your help on those issues in particular. Looking forward to working together soon!

Thanks again,
-Derek

p.s. A great place to get more intimately involved in core development is via Slack. In particular, these channels:

• #core-development
• #bugsmash
• #needs-review-queue-initiative

@rduterte, thank you for the offer!

Your offer and others have pointed out that the next version of this issue should include the details about the prerequisites for taking on a maintainer position. The related links in the Issue Summary are a start learning about the expectations. What @dww suggests though is correct, that working on issues in your areas of interest is a good first step. Also, participating in Slack discussions in the #core-development channel helps.

Cheers

Hi @dww and @quietone — thank you both for the guidance and encouragement.

I appreciate the clarity on expectations.

I’ll continue contributing through triage, testing, and reviews in different core components, starting with Content Moderation, and I’ll join the suggested Slack channels!

Thanks again — looking forward to contributing and learning along the way.

Cheers,

By my count, 13 Subsystem maintainer positions have been filled. Thank you!

There are 3 outstanding child issue left here. One is for longwave to fill a proposed new role of Dependency coordination topic maintainer. This one will take more time because there are related issues to complete, such as approving the creation of the position. And two of them are for darvanen who has asked for more time. While these are child issues I think this issue should be closed for the reasons following.

This issue was a follow up to the 2025 Annual Maintainer Check-in process. The intention was for a 'short duration' issue that advertised the positions with no maintainer after the check in. That has happened and community members raised there hands, issues created and we have more maintainers. But, since we were developing this process as it ran it required additional time to document and consult on each step to help make sure we acted appropriately. We are now well into 2026, so let's close this. Hopefully, the 2026 check-in will be completed in the same year.

Therefor, setting this to RTBC.

Contributors are welcome to discuss becoming a subsystem or topic maintainer with any member of the Core Leadership Team. Nominations can be made at any time, they do not have to be part of an issue like this.

Great.

I've given credit to all commenters here because it either helped us improve this new process or lead to an appointment.

Going ahead and marking this fixed. Good to have MAINTAINERS.txt more closely reflect reality.

In summary, 8 contributors have taken on positions in 11 subsystems.

@penyaskito contacted me that the credits were not saved. I have done that now. Thanks.