Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
As part of our continuing efforts to manage Drupal 8+ for each release, we're trying to make sure that every current Drupal core component has at least one active comaintainer. The first step is to identify component maintainers for those components that don't already have one listed.
Component not listed
- datetime_range.module
Component listed with no maintainer
- asset library system
- base system
- batch system
- bootstrap system
- browser system
- cron system
- postgresql db driver
- sqlite db driver
- extension system
- install system
- lock system
- mail system
- request processing system
- routing system
- token system
- action.module
- ban.module
- content_translation.module
- filter.module
- help.module
- menu_ui.module
- node system
- options.module
- system.module
- views_ui.module
- workspaces.module
- Stable theme
- Starterkit theme
- composer
- user interface text
- documentation
- other
Component listed with maintainer
There are 80 components with maintainers.
Related issues
Sub-issues
- #1823042: Add maintainers and d.o components for all field type modules
- #2048925: Add JohnAlbin as a component maintainer for CSS
- #2045901: Add Wim to MAINTAINERS.txt for editor.module and ckeditor.module
- #2050511: [Policy, no patch] Remove the "Node system" component; it is redundant with node.module
- #2050815: Update XML-RPC entry for 8.x in MAINTAINERS.txt
- #2054181: Add andypost as a component maintainer for history.module
- #2054499: Add toolbar maintainers
- #2057173: Add Mark Carver to MAINTAINERS.txt for the Color module
- #1892270: Add serialization system to Maintainers.txt
- #2474677: Add Mac_Weber to MAINTAINERS.txt for the link.module
Other related issues
- #2050451: Formalize the role of core component maintainers
- #2046081: Add issue queue integration to formalize the role of core component maintainers
- #2046091: Add a view of issues per component
- #1854480: Remove inactive maintainers from MAINTAINERS.txt
- #2050763: Refine "base system" component
- #2050821: Add larowlan as a component maintainer for comment.module
- #2056625: Recruit pwolanin and jhodgdon as official search.module maintainers
Comments
Comment #1
jhodgdonThere are also a few modules with outdated maintainers. Really, we need to go through all the maintainers in MAINTAINERS.txt and see:
- if they are willing to fulfill the role
- if they are actually fulfilling the role
For instance, I know that search.module has a maintainer listed who has not done anything for that module in a couple of years, and I've been unable to get my supposed co-maintainers for the Transliteration component to review my patches, despite repeated inquiries (and without anyone to review patches I may be unwilling to continue as maintainer of that component either).
I also just marked #2042309: MAINTAINERS.txt does not have entry for several modules as a duplicate of this issue, since this one is more complete, better organized, etc.
Comment #2
xjmThanks @jhodgdon! We actually have plans to contact every single component maintainer listed to get the file up to date, but that's something we want to do directly first (rather than over the issue queue). But it's something I've been working on for the past week or so. Watch for an email. :)
Comment #3
xjmLooks like XML-RPC is listed as a "system" instead of a module in the component listing and in MAINTAINERS.txt, which is why it looks like it's unlisted. @fgm is the maintainer there. Does XML-RPC have component-level stuff in core as well, or is it all contained in the module? If the latter, we should rename the component and fix MAINTAINERS.txt.
Comment #3.0
xjm.
Comment #3.1
xjmUpdated issue summary.
Comment #4
tim.plunkettxmlrpc.inc is D7, xmlrpc.module is D8
Comment #4.0
tim.plunkettUpdated issue summary.
Comment #5
xjmComment #6
larowlanI'm happy to put my hand up to help with comment module if _dixon will have me, a lot of comment will be moved about with #731724: Convert comment settings into a field to make them work with CMI and non-node entities so it makes sense that I stick around to deal with any fall out :)
Comment #7
xjm@larowlan, I was going to suggest you do so actually, so +1! :)
Comment #7.0
xjm.
Comment #8
xjm#2050821: Add larowlan as a component maintainer for comment.module filed. :)
Comment #8.0
xjmUpdated issue summary.
Comment #9
andypostI could take a history module because following from begining
Also I could recommend @claudiu.cristea for image module
Comment #10
xjmThanks @andypost! Can you file issues for those?
Comment #11
andypostJust one #2054181: Add andypost as a component maintainer for history.module for second issue suppose better to ping claudiu in IRC
Comment #11.0
andypostUpdated issue summary.
Comment #11.1
xjmUpdated issue summary.
Comment #11.2
nod_Adding toolbar maintainer issue
Comment #12
jhodgdonpwolanin indicated today in IRC that he would be willing to maintain search.module. Unfortunately he also nominated me for co-maintainership... which I might be convinced of but I am unsure after my 7.x experience with same.
Comment #12.0
jhodgdonNow with the right issue number
Comment #12.1
xjmUpdated issue summary.
Comment #13
larowlanNote also #1203886: Remove the PHP module from Drupal core might remove php with any luck
Comment #14
markhalliwellI've been wanting to #445990-24: [META] Refactor color module for a while now. Granted I know it probably won't change in D8 at all since there's really no time. But I'd be willing to take it on so we can move forward in D9.
Comment #14.0
markhalliwellUpdated issue summary.
Comment #14.1
xjmUpdated issue summary.
Comment #14.2
xjmUpdated issue summary.
Comment #14.3
xjmUpdated issue summary.
Comment #14.4
xjmUpdated issue summary.
Comment #14.5
markhalliwellUpdated issue summary.
Comment #14.6
xjmUpdated issue summary.
Comment #14.7
linclark CreditAttribution: linclark commentedRemoved serialization module since that was committed.
Comment #14.8
xjmCopy of the revision from August 3, 2013 - 16:03.
Comment #14.9
xjmUpdated issue summary.
Comment #15
nod_Missing datetime module
Comment #16
andypostWilling to support and fix comment module #2099977: Add andypost as a component maintainer for comment.module
because core accepted #731724: Convert comment settings into a field to make them work with CMI and non-node entities
Comment #16.0
andypostUpdated issue summary.
Comment #16.1
realityloopadded myself to Overlay
Comment #17
tim.plunkettThis process is long and difficult, but let's tackle the easy parts first #2190699: Add missing modules to MAINTAINERS.txt
Comment #18
larowlanAdded #2300583: Consider adding larowlan and tim-e as contact module maintainers
Comment #19
xjmComment #20
Mac_Weber CreditAttribution: Mac_Weber commentedAdded myself to Link module: #2474677: Add Mac_Weber to MAINTAINERS.txt for the link.module
Comment #22
mpdonadioAdded DateTime.
Comment #25
dagmarAdded Database Logging to list of Component listed with no maintainer.
Comment #26
zaporylieMoved Telephone module to list of Component listed with no maintainer.
Comment #30
andypostDatabase & drivers (except mysql) also missing maintainers
Comment #34
andypostAdded child issues
- #3178983: Clean-up Testing from topic maintainers
- #1921504: Create a Condition system component for core
Comment #35
quietone CreditAttribution: quietone as a volunteer commentedI think this is outdated, MAINTAINERS.txt refers to subsystems as of late 2016, #2785891: The distinctions between modules, themes, and other subsystems are not relevant in MAINTAINERS.txt or the issue queue component field.
Comment #36
darvanenIf this is outdated, where do we go to find this information now? Or is the file correct and the issue out of date?
Comment #37
quietone CreditAttribution: quietone as a volunteer commentedI am not following you. The information in the IS is outdated, it no longer matches the components in MAINTAINERS.txt.
What information do you think needs to be kept?
Comment #38
darvanenI just did not understand what "this" was in "this is outdated", sorry. You've answered my question.
Comment #39
andypostComment #43
quietone CreditAttribution: quietone at PreviousNext commentedIt wasn't any fun but I updated the Issue Summary.
Comment #44
daffie CreditAttribution: daffie at Finalist commented@quietone: I am the subsystem maintainer for the Database API. AFAIK that also makes me the maintainer of the MySQL, PostgreSQL and SQLite modules. Only on your updated list the PostgreSQL and SQLite database drivers are marked as "no listed maintainer". Do I need to create an issue to aslo become the maintainer of those modules? BTW, the database drivers now live in modules. Should the maintainers.TXT file be updated for that?