Offering to co-maintain DrupalPod

Problem/Motivation

After some discussion at DrupalCon Atlanta 2025, I volunteered to help co-maintain DrupalPod as part of the Core Mentoring Coordinator team. I had been making and reviewing some pull requests on GitHub as well as here on drupal.org. I previously co-maintained quicksprint with rfay in a similar role and helped realityloop with an early docker-based approach.

Interested parties, mentors and development environment enthusiasts, want to offer to help in two phases:

1. Address the immediate active merge requests and older pull requests, and better be able to provide support:
   • Updating the Core Mentoring VS Code extension as it is out-of-date with pending merge requests and pull requests.
   • Help Drupal Forge by allowing DrupalPod as it exists today to work without using a merge request branch.
2. Plan a long term re-architecture of DrupalPod so that we can better transition to run from dev containers or DevPanel or whatever solution exists in the future. This is probably going to take more than one person’s effort, and there is renewed interest from mradcliffe, realityloop, salim, darren oh, rfay to help out among others.

Proposed resolution

One or more co-maintainers to help organize DrupalPod as it exists today and plan for DrupalPod in the future. It may also be a good idea to form a technical advisory group.

Proposed additional co-maintainers

• mradcliffe — Matthew Radcliffe
• ...

Remaining tasks