Hello everyone! It's me, the main maintainer of Drupal VM for <checks git history> 7 years, almost 100 releases, and almost 2,000 commits.

I wanted to post this issue to give an honest overview of Drupal VM's current status in terms of maintenance, support, and future development:

1. I am no longer using Drupal VM actively for any of my own projects (nor do I work somewhere where it is the main development tool in use).
2. I still actively use and maintain most of the Ansible roles which make up Drupal VM.
3. I still use VirtualBox and Vagrant quite a bit.
4. I do not have the bandwidth to continue maintaining Drupal VM on my own (not to mention trying to fix some longstanding issues, like the Docker build still being broken due to some pesky postfix issue).

I'm wondering if someone in the community would like to take up the mantle of Drupal VM and I could pass my maintainership keys to that person (either through blessing a fork, or giving over access to this repo in my namespace).

If not, then at that point I will continue to minimally maintain the 6.x version of Drupal VM until it becomes a burden (e.g. until CI tests start failing regularly), and then deprecate it.

You may be wondering what I use now, if not Drupal VM? Well, mostly custom Docker environments with a docker-compose.yml file specific to each project. Not that I do as many these days, it's mostly Hosted Apache Solr, Server Check.in, my personal site, and the Raspberry Pi Dramble site.

Anyways—I thought instead of just letting things start to sit and wither more (the issue queue could use a good pruning), I'd open up the floor to discussion about what the future of Drupal VM should look like.

In any case, I am extremely pleased with how many people Drupal VM has helped over the years—far beyond the dozen or so I envisioned when I first open sourced this repo—and I will continue to help people automate frustrating tasks (like local environment setup) no matter what!