Problem/Motivation
markconroy has volunteered to be a maintainer of the Markup subsystem during the 2025 Annual Maintainer Check-In process.
Remaining tasks
Community
Community input is welcome and appreciated until 2026-01-20 (2 weeks from this issue being created).
Comment on this issue, or contact griffynh on Drupal Slack.
markconroy 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-3566056
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:
- 3566056-2026-01-21-add-markconroy
changes, plain diff MR !14694
Comments
Comment #2
quietone commentedComment #4
markconroy commentedHi @quietone,
Thanks for the offer to be a maintainer of Markup subsystem. I confirm:
Comment #6
markconroy commentedComment #7
smustgrave commentedDate for this one passed and definitely a +1!
Comment #8
quietone commentedComment #13
quietone commented@markconroy, thanks for becoming a subsystem maintainer for another area, this time it is Markup!
Committed to currently supported branches, except security only branches. There is no extra admin because markconroy is an existing subsystem maintainer,