Problem/Motivation

We added HTMX as a dependency in #3520723: Add HTMX dependency to core and are now building out a series of classes planned in #3404409: [Plan] Gradually replace Drupal's AJAX system with HTMX that will replace the implementation of the Ajax subsystem.

Proposed resolution

I have been part of the Drupal community for over 15 years and a contributed module maintainer for over 12 years. I have been the principal maintainer of the HTMX contrib module since March 2024. I built the implementation for #3446642: [POC] Implementing some components of the Ajax system using HTMX and have been a collaborating contributor to each of the issues in our community initiative as well as coordinating the work of the initiative. I would like to volunteer as a subsystem maintainer for this new capability in core. I have read and accept the expectations for subsystem maintainers as well as the Responsibility assignment matrix.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3534047

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

fathershawn created an issue. See original summary.

nod_’s picture

very much a +1 ! You've been great to work with

nicxvan’s picture

+1 here as well! I've been following the htmx initiative closely and every interaction I've had with @fathershawn has been great!

fathershawn’s picture

Issue tags: +Project governance
fathershawn’s picture

Title: Add fathershawn as a subsystem maintainer for new HTMX subsystem » Add fathershawn as a subsystem maintainer for the Ajax subsystem
Issue summary: View changes

@nod_ suggested adding my name to the existing list of Ajax subsystem maintainers. I had pictured we were replacing one subsystem with another but it can also be described as replacing everything within the existing subsystem as HTMX is a ajax based library. Changed the issue name to match and opened an MR.

nod_’s picture

Status: Active » Reviewed & tested by the community

MR is good to go, The documentation has been read and understood.

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

  • xjm committed db7a54af on 11.2.x
    Issue #3534047 by fathershawn, xjm, nod_: Add fathershawn as a subsystem...

  • xjm committed 3199505c on 11.x
    Issue #3534047 by fathershawn, xjm, nod_: Add fathershawn as a subsystem...

  • xjm committed 9708b971 on 10.6.x
    Issue #3534047 by fathershawn, xjm, nod_: Add fathershawn as a subsystem...
xjm’s picture

Status: Reviewed & tested by the community » Fixed

Committed to 11.x and cherry picked to 11.2.x, 10.6.x, and 10.5.x. I also added @fathershawn with subsytem-maintainer privileges on https://www.drupal.org/node/3060/maintainers and invited him to the private Slack maintainer channel.

Welcome to the team!

xjm’s picture

Version: 11.x-dev » 10.5.x-dev
tim.plunkett’s picture

Welcome @fathershawn! A little after the fact but huge +1

Status: Fixed » Closed (fixed)

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