tomjn
commented
3 years ago As an aside @iandunn @dd32 @coreymckrill can I get an official hard stance on the meta environment? Right now you're doing that wishy washy thing where you don't say it's unsupported/dead, but you don't say it's alive either, and keep everything vague and ambiguous. The end result is I have to pick up the pieces and help people who want answers, and VVV gets a bad rep as a result.
I understand you want to move away from this repo so:
- clearly mark out the parts that got replaced
- maintain the parts that didn't until they're replaced ( an aspirational or TODO replacement does not help people to contribute )
But finally, stop shit talking VVV when the subject is raised. I know you don't like Virtual machines, but it's a bit rich crapping all over a community project when your replacement is a container in a Hyper-V/Virtualkit Virtual Machine.
If you like/prefer docker just say so and say that's what you support, there's no need to call VVV backwards or regressive. ( you'll look silly doing it when VVV docker is official anyway, and anybody using Parallels or VMWare is already using the same tech Docker uses ).
Honestly it's rude, I and others have bent over backwards trying to help people struggling with this repo, walking people through at WordCamps, answering questions in slack, updating .org docs, prepping boxes and zip files for WordCamps so it opens up docker image style, and getting dismissed as backwards. I'd much rather you just said you don't have time to maintain things and do the responsible thing and clearly mark things out and update the docs.
Vagrant may not be fashionable but it's no excuse for rudeness.
iandunn
alpipego
Users should be warned that there are deprecated sites and given links to the replacements
Related to #146 and #144