Deprecation Warnings

[tomjn]

Users should be warned that there are deprecated sites and given links to the replacements

Related to #146 and #144

[tomjn]

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.

[tomjn]

I would also be mindful that currently there is technically no local dev environment for:

• buddypress.org
• jobs.wordpress.net
• wordpress.org
• developer.wordpress.org
• global.wordpress.org
• translate.wordpress.org
• wordpress.tv

and no official way to contribute to them, and anybody who tries to use this repo to contribute will quickly encounter lots of things that are trivial to fix but requires someone with a .org sandbox to know what they should be changed to.

[tomjn]

I've updated the readme with a link to the wordcamp repo and adjusted the text to indicate support status is limited

[iandunn]

Hey Tom 👋🏻
+1 to updating the readme (xref 789c82b, 380aa42, dc26165)

"official" stances are few and far between in WP organizational structures; it's more like a loose consensus that gets built organically.

The Meta Env was never a project that sponsored time was directed to (re:). I created it as a personal initiative, because I saw a need for it. It was never something that was going to be sustainable without a large group of maintainers, but that didn't become clear until years later.

I haven't done anything to shut it down before, because it seems like some people still find it useful, and because you and others have helped maintain it. If anyone feels like you have to maintain it and don't want to, then I think there's got to be better solutions to that (like Varying-Vagrant-Vagrants/varyingvagrantvagrants.org@2d15f52).

If there's a consensus around shutting it down, that WFM.

I'm not sure what insults towards VVV you're referring to, so I'm guessing they weren't said by me? If I'm wrong about that, please let me know.

[alpipego]

We created a new environment based on wp-env at the WordCamp Asia Contributor Day: https://github.com/alpipego/buddypress.org-wp-env. This should be easy to run, it could use an updated DB dump, however. I'm happy to move this over to a different org if someone is willing to give me a hand in it.