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

  1. datetime_range.module

Component listed with no maintainer

  1. asset library system
  2. base system
  3. batch system
  4. bootstrap system
  5. browser system
  6. cron system
  7. postgresql db driver
  8. sqlite db driver
  9. extension system
  10. install system
  11. lock system
  12. mail system
  13. request processing system
  14. routing system
  15. token system
  16. action.module
  17. ban.module
  18. content_translation.module
  19. filter.module
  20. help.module
  21. menu_ui.module
  22. node system
  23. options.module
  24. system.module
  25. views_ui.module
  26. workspaces.module
  27. Stable theme
  28. Starterkit theme
  29. composer
  30. user interface text
  31. documentation
  32. other

Component listed with maintainer

There are 80 components with maintainers.

Related issues

Sub-issues

Other related issues

Comments

jhodgdon’s picture

There 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.

xjm’s picture

Thanks @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. :)

xjm’s picture

Looks 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.

xjm’s picture

Issue summary: View changes

.

xjm’s picture

Issue summary: View changes

Updated issue summary.

tim.plunkett’s picture

xmlrpc.inc is D7, xmlrpc.module is D8

tim.plunkett’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue tags: +Component maintainers
larowlan’s picture

I'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 :)

xjm’s picture

@larowlan, I was going to suggest you do so actually, so +1! :)

xjm’s picture

Issue summary: View changes

.

xjm’s picture

xjm’s picture

Issue summary: View changes

Updated issue summary.

andypost’s picture

I could take a history module because following from begining
Also I could recommend @claudiu.cristea for image module

xjm’s picture

Thanks @andypost! Can you file issues for those?

andypost’s picture

Just one #2054181: Add andypost as a component maintainer for history.module for second issue suppose better to ping claudiu in IRC

andypost’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

nod_’s picture

Issue summary: View changes

Adding toolbar maintainer issue

jhodgdon’s picture

pwolanin 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.

jhodgdon’s picture

Issue summary: View changes

Now with the right issue number

xjm’s picture

Issue summary: View changes

Updated issue summary.

larowlan’s picture

Note also #1203886: Remove the PHP module from Drupal core might remove php with any luck

markhalliwell’s picture

I'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.

markhalliwell’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

markhalliwell’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

linclark’s picture

Issue summary: View changes

Removed serialization module since that was committed.

xjm’s picture

Issue summary: View changes

Copy of the revision from August 3, 2013 - 16:03.

xjm’s picture

Issue summary: View changes

Updated issue summary.

nod_’s picture

Missing datetime module

andypost’s picture

andypost’s picture

Issue summary: View changes

Updated issue summary.

realityloop’s picture

Issue summary: View changes

added myself to Overlay

tim.plunkett’s picture

This process is long and difficult, but let's tackle the easy parts first #2190699: Add missing modules to MAINTAINERS.txt

larowlan’s picture

xjm’s picture

Mac_Weber’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mpdonadio’s picture

Issue summary: View changes

Added DateTime.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dagmar’s picture

Issue summary: View changes

Added Database Logging to list of Component listed with no maintainer.

zaporylie’s picture

Issue summary: View changes

Moved Telephone module to list of Component listed with no maintainer.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

andypost’s picture

Version: 8.6.x-dev » 8.9.x-dev

Database & drivers (except mysql) also missing maintainers

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

andypost’s picture

quietone’s picture

darvanen’s picture

If this is outdated, where do we go to find this information now? Or is the file correct and the issue out of date?

quietone’s picture

I 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?

darvanen’s picture

I just did not understand what "this" was in "this is outdated", sorry. You've answered my question.

andypost’s picture

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes
Issue tags: -Needs issue summary update

It wasn't any fun but I updated the Issue Summary.

daffie’s picture

@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?

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.