Adam

Patch worked. And this module is insanely cool. It's a tad tricky to use, but in general I think it is magnificent. I'm going to submit a PR to add...

@TravisCarden I feel like it should be a separate workflow, but how about this: what if we simply trigger it: * only on `main`, and PRs to `main` * only...

Well...it _should_. But I'm not sure. Windows is tricky 'cause it's just gotta do weird shit all the time. That said, I bet this would work reasonably well on WSL....

I'm leaning towards removing the "immediately install upon project creation" thing. I think it's okay to add _one_ more step. What I propose is that you'd do this, _regardless_ of...

The previous comment is now implemented and documented. The installation is no longer a one-liner; it's a grand total of...2 commands. Three if you count the 'cd' into the project...

Some possible criteria for inclusion: * Active maintainership -- that means at least one maintainer needs to be available for questions and bug fixes, and is on top of keeping...

There a lot of factors. A module like ERR is a problem case because even though it does questionable things at the data layer, it enables (via Paragraphs) _so_ many...

> Is there a timeline for when this person is appointed? That, I don't know. But I don't think it will be, or _should_ be, one person. I think it...

I am +1 on adding the oEmbed Providers module, but I think we should carefully select which providers we enable. It's really easy to go overboard, and we also need...

As of 20eeb2cb3c4859f6d7f7a70ac39079c5268d16ab, I did this in a somewhat hacky way, but it works. Normally you'd be able to override the database credentials using an environment variable, which would look...