Problem/Motivation
rainbreaw did not respond to the 2025 Annual Core Maintainer Check-In and has been unresponsive throughout the 4-week confirmation period.

As per the Core subsystem maintainer policy, maintainers who do not confirm their continued involvement will be removed from MAINTAINERS.txt.

Proposed resolution:
Remove rainbreaw’s name and contact details from the MAINTAINERS.txt entry for the Accessibility subsystem.

Remaining tasks:

  • Commit the update to MAINTAINERS.txt
  • Notify the Core Committers Slack channel when merged

No UI/API/Data model changes.

Issue fork drupal-3536192

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

griffynh created an issue. See original summary.

ankusht1515 made their first commit to this issue’s fork.

ankusht1515’s picture

Status: Active » Needs review

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Thank you @rainbreaw for helping make Drupal more accessible!

mgifford’s picture

Thanks Rain. You have contributed a bunch to Drupal's accessibility. Thanks.

rainbreaw’s picture

Thank you for moving forward with removing me, and my apologies for not responding during the 4 week period! I appreciate the time that I've spent as a maintainer very much, and appreciate that it is now time for others who can more fully commit to take on the role.

No words can express how grateful I am for the Drupal community, which has been so important to me for nearly 20 years now!

  • xjm committed 45aecb0a on 11.x
    Issue #3536192 by rainbreaw, xjm: Remove rainbreaw as maintainer for...

  • xjm committed c01d005f on 11.2.x
    Issue #3536192 by rainbreaw, xjm: Remove rainbreaw as maintainer for...

  • xjm committed c4f151be on 10.6.x
    Issue #3536192 by rainbreaw, xjm: Remove rainbreaw as maintainer for...

  • xjm committed 39c5d0cd on 10.5.x
    Issue #3536192 by rainbreaw, xjm: Remove rainbreaw as maintainer for...
xjm’s picture

Version: 11.x-dev » 10.5.x-dev
Status: Reviewed & tested by the community » Fixed

Thanks @rainbreaw! Your expertise has been an awesome resource.

The MR did not apply, but this is the sort of issue that committers can just fix directly, so I made the change manually and committed that. Committed to 11.x, 11.2.x, 10.6.x, and 10.5.x. Since this was Rain's single MAINTAINERS.txt entry, I'm also updating the core node permissions, the Google group, and the maintainer Slack channel.

Note that I did not credit @ankusht1515 on this issue. (We are going to limit it to a couple credits for MR creation by itself, because these issues should have been created as postponed, oops). They are credited on another of these issues though for help creating all the MRs. 🙂

Thanks everyone!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.