Problem/Motivation
smustgrave has volunteered to be a maintainer of the Options subsystem during the 2025 Annual Maintainer Check-In process.
Remaining tasks
Community
Community input is welcome and appreciated until 2026-02-23 (2 weeks from this issue being created).
Comment on this issue, or contact griffynh on Drupal Slack.
smustgrave to confirm the following
- They have read and understand the definition of maintainers.
- They accept the Subsystem maintainer responsibilities.
- They are committed to following our community issue procedures and etiquette paying particularly attention to providing constructive feedback.
Core Leadership team
The Core Leadership Team has reviewed and approved this nomination, and we're now seeking community feedback ahead of confirming the appointment.
Committer
- Commit per standard practice.
- Complete the administrative tasks in add a subsystem or subsystem maintainer.
Issue fork drupal-3572244
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:
- 3572244-add-smustgrave-as
compare
- 3572244-smustgrave-options
changes, plain diff MR !14690
Comments
Comment #2
griffynh commentedComment #5
smustgrave commentedCan confirm I've read and understand the bullets mentioned.
Comment #6
quietone commented+1 from me. I would RTBC but I wish to be able to commit this.
Comment #7
dcam commentedAre we supposed to wait for the comment period to be over before RTBCing?
Comment #8
dcam commentedI'm going ahead with RTBCing this since @smustgrave is already an experienced Core maintainer.
Comment #13
quietone commented@smustgrave, thanks for agreeing to take care of the Options subsystem!
As smustgrave is already a subsystem maintainer there are no additional admin tasks to complete.
Committed to active, non-security only, branches.