yawp (noun): a harsh or hoarse cry, or yelp.
yawp (verb): shout or exclaim hoarsely; to make a raucus noise or clamour.
Like Gutenberg’s printing press, the word “yawp” comes from the 15th century, known later from a line in an 1892 poem by Walt Whitman, “I sound my barbaric yawp over the roofs of the world.”
The girl pictured is the original header image from the blogging software b2, which referred to itself as a “classy news/weblog tool (aka logware)” from roughly 2001 to 2003.
yawp (.foo): YAWP is a recursive acronym, and like “foo”, it can have many meanings, as long as the acronym remains recursive. Yawp is Another Web Platform. Capitalize it however you like, dangit.
I think she’s yawping. Are you ready to yawp?
What?
About
In late September 2024, we entered a chaotic interlude in the history of WordPress, involving not just the software, but the major players involved and the community around, with implications for the wider open source software movement.
The pretext on which the controversy began is disastrously wrong, based in demonstrably flawed logic. As the WP Community sets to re-lay its foundation, it is imperative we not repeat the same mistakes. Here I’m referring not simply to practical matters like governance structures, but the free and open source software (FOSS) philosophy and ethos, which are fundamental to the community.
Looking for more context? There are many summaries online, both as news stories and as running chronologies to links. There’s a (co-)founder, a private equity firm, a lawsuit, lots of fallout, and a community in crisis.
If you want to read in the order I’m building my thesis, here’s the outline:
Latest Article
Breaking the Status Quo is The Future of WordPress
Abstract
In this article, I use Matt Mullenweg’s response to a recent article based on an interview he gave to Inc. as a framework to outline some of the reasons why the WordPress project needs a new governance model. I support recent calls for this change. In addition to other reasons I have outlined in related posts, I recap here Matt’s departure from FLOSS ideals, his misrepresentation of his motives in attacking WP Engine, and in attempts to then cast himself as the victim. I then briefly discuss how the increasingly chaotic atmosphere in the community increases what is already an inherently unacceptable level of risk to the WordPress supply chain.