Questions about building a project that extends Devenv

[liammcdermott]

I have a project called drupal-devenv, which is built on top of Devenv and extends it, and I have a couple of questions about that project:

1. In Getting Started I advise users to add devenv-drupal to devenv.yaml, but I'm aware this approach of using devenv.yaml (as opposed to a Nix Flake) might limit the project's usefulness. Would you structure a project that extends Devenv around devenv.yaml, or would you use a Flake?
2. I assumed that specific frameworks are beyond the scope of Devenv, and a PR adding a Drupal module would be rejected. Is that correct?
3. Vibe check. Do you welcome this sort of project? Do you have any constructive critique on the structure and implementation? Maybe only answer this last one if you have time!

Thank you for your consideration, and for Devenv, it got me hooked on Nix!

[sandydoo]

1. We strongly recommend that people stick to devenv.nix + devenv.yaml, unless they already have a much more complicated flake-based system they're integrating devenv into.
2. It'd be great to have built-in support for specific frameworks too, but our main concern is maintenance burden. The faster the update cadence and more complicated the setup, the less likely that we'd be able to keep up.
3. Looks awesome! ❤

[liammcdermott]

Thank you so much for looking into this, @sandydoo! I'm very happy to hear drupal-devenv wasn't a terrible idea.

Regarding (2), I thought that might be the case. I'm hoping specialists in the community can help! We know our frameworks better than anyone, including all the details and gotchas. So, we should build and maintain framework-specific modules on top of devenv, and users can compose them in their environments.

I have a follow-up issue (or two), which I'll post separately. Thanks again!