FAQ

waggypuppy Frequently Asked Questions

What is waggypuppy?

A "hard" fork of WordPress 6.7 (sometime during 6.7 beta, specifically this commit from 2024-10-05)

waggypuppy aims to be fully compatible with WordPress 6.0 and later. Backward compatibility with older versions is not guaranteed, but any BC breaks will be well-documented and not taken lightly.

A larger mission for waggypuppy is still being articulated. Watch this space.

Why a fork?

Suffice it to say that the leadership of WordPress has lately become an impediment to the continued good health of the WordPress core and its entire ecosystem. I'll leave it there: it would make my year if there came a time when people actually forget why we forked or who the dramatis personae were when it happened.

Cute name, but are Serious Business Users™️ going to adopt it?

Probably not, but the idea is to eventually support one-click "re-spins" that replace every occurrence of "waggypuppy" in the code with your preferred name. After making a re-spin, it becomes your project that you may use as you wish (under the terms of the GPL). I'm tentatively calling the process "adoption": after all, most people do choose their own name for a pet they adopt from a shelter.

I (Chuck) lack the capability and ambition to truly take over WordPress: waggypuppy exists so you can do so if you wish.

Why was the version history for WordPress not kept?

First it saves 200MiB worth of repo size, but that's not the main reason. As a hard fork, there will not be further updates from upstream WordPress, save for those that are ported manually. It makes little sense to keep tracking an active branch (trunk) that largely can't be cherry-picked anyway due to the major divergence caused by refactoring.

How is waggypuppy properly capitalized?

All lowercase, always. waggypuppy should be lowercased even at the start of a sentence. lowercase everything, dangit!