Well everybody, it has come to my attention that #WordPress ™©® may need to be #forked for the good of the group.

Has anyone been a part of any of the big forkings of the past or manage any #opensource projects that have any insight about what it might take to accomplish such a task?

I know making a fresh GitHub account is basically Step Negative 15. What sort of challenges would a new community fork of WordPress be facing?

I personally would be willing to contribute all that I can which most likely wouldn't be a huge help just because I'm not that knowledgeable but if anybody is starting out in that direction I'd be willing to join up.

(Disclaimer: I'm not associated with Automattic or WPEngine in any way. Please don't DM me Matt.)

@MrMozz A few folks have done forks of WordPress already, but it's hard to build up a new community to the point of it not just being more work than what is getting out of it

@david Fair enough and I totally get that. I also don't suppose it's something that like the Linux foundation or the Apache foundation would be interested in taking on for the foreseeable future.

I just hate to see such an important piece of open source internet infrastructure get pooped upon in such a manner by a handful of jerks if there was another way forward.

@MrMozz That's the other thing: WordPress has always been a laughingstock among a lot of FOSS people, for good or bad, and it's not something that will be helped by a situation like this.

Never mind the number of petty things that have derailed distros 😅

@david No kidding. Heck, even Deb and Ian eventually split up, and that's one of the most stable parts of the FOSS world. Haha.
ClassicPress | Stable. Lightweight. Instantly Familiar.

ClassicPress is a community-led open source content management system. A fork of WordPress 4.9, it retains the WordPress classic editor as the default option.

ClassicPress

@syntaxseed Hadn't heard of either. Really cool. I'm especially interested in Bedrock because its bragging about composable installs.

Classicpress looks like it might be a nice drop in replacement for a few of my clients too if it comes to it

@MrMozz I tried Bedrock for a while. The concept that you can use composer for all the addons & keep your build in Git was tempting but lots of plugins & themes aren't available via Composer so you end up half-and-half which defeats the purpose. So I went back. 🤷‍♀️

#Bedrock #Wordpress

@syntaxseed @MrMozz via https://wpackagist.org/ all themes/plugins in the official repo can be installed via Composer.

If not in the official repo, but open source, 99% they're in GitHub/GitLab so ok for Composer.

Only issue are "premium plugins" not in the repo nor OSS. For those, you might need Satispress https://github.com/cedaro/satispress.

We have that mirrored in our Private Packagist instance.
So it takes some effort, but 100% Composer-powered WP is double. But overkill if it's not your daily job.

WordPress Packagist: Manage your plugins and themes with Composer

@gmazzap @syntaxseed oooo. This is cool too. I'm a little primed to be excited about this because I've been messing a lot with Ansible and NixOS lately and I just want to compose everything now. I finished up a project a few weeks ago that involved un-mucking and migrating an unloved WordPress/WooCommerce site from GoDaddy to a standard web host and being able to just declare a set WordPress state would have been glorious.