WordPress Planet

November 18, 2026

WordPress.org blog: WordPress 7.1.5 Release

This security release features fixes for multiple issues.

Because this is a security release, it is recommended that you update your sites immediately.

You can download WordPress 7.1.5 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.

WordPress 7.1.5 is a short-cycle release. The next major release will be version 7.2, currently planned for December 8th.

For more information, please visit the WordPress 7.1.5 HelpHub site.

Security updates included in this release

  • A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
  • A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
  • A reflected XSS in the legacy media library popup, reported by Anthropic.
  • An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
  • SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
  • Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
  • Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
  • SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
  • Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
  • Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
  • Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
  • Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
  • Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
  • Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
  • Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
  • A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
  • Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
  • Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
  • XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
  • Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.

Thank you to these WordPress contributors

This release was led by Jeremy Felt, Jerry Jones, and Jarda Snajdr. WordPress 7.1.5 would not have been possible without the contributions of the following people:

Aaron Jorbin, Adam Silverstein, Alex Concha, Andrew Duthie, Andrew Serong, Ben Bidner, Christiaan Swiers, Daniel Rodriguez, Dennis Snell, Ehtisham Siddiqui, George Mamadashvili, Giovanni Cintolo, Greg Ziółkowski, Isabel Brison, Jarda Snajdr, Jeremy Felt, jeryj, Jesse McNeil, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Juliette Reinders Folmer, Kira Schroder, Lance Willett, Logan Homolka, Luca Tumedei, luisherranz, Marc Montpas, Marin Atanasov, Mohammad Jangda, Nik Tsekouras, Peter Wilson, Rafie Muhammad, ramonopoly, Rudy Faile, Sergey Biryukov, Shu Takahashi, Weston Ruter

Backports

As a courtesy, the security fixes were backported to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready.

In WordPress 7.0, 1024 bit certificates were removed from bundled root certificates. This change has been applied to 6.9.12 and earlier as part of this release.

WordPress 7.2 RC 2 has also been released, containing all applicable fixes.

by Jeremy Felt at November 18, 2026 05:08 PM

Open Channels FM: The Real Challenge of AI in Open Source, Maintaining What We Build

AI significantly accelerates code writing and participation in open source, improving contributor productivity by over 50%. However, this leads to higher burdens on maintainers, who must manage low-quality, AI-generated code, affecting project sustainability and quality.

by Open Channels FM at November 18, 2026 04:08 PM

Open Channels FM: Expand Your Corner of the Open Source Ecosystem with Open Channels News

Capture the latest in open source with concise episodes and occasional commentary to broaden your understanding

by Bob Dunn at November 18, 2026 03:00 PM

WPTavern: #242 – Mark Westguard on How WordPress Adapts to Rapid Change: the Dot-Com Bubble to AI Hysteria

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how WordPress adapts to rapid change the .com bubble to AI hysteria.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Mark Westguard. Mark has been building websites for over 30 years, starting out in the early days of the web with his agency, Absolute Internet in the UK, before moving to the US and transitioning into product development. He now runs WS Form, a form plugin for WordPress.

During this episode, we get into the evolution of the internet and WordPress through major technological inflexion points. Most recently, the rise of AI. Mark draws comparisons between the AI era and the frenzy of the .com boom, sharing how rapid influxes of investments and hype, can reshape the entire landscape, often faster than the underlying technology can deliver sustainable results.

The conversation focused not just on the opportunities AI brings to developers and end users, such as dramatically lowering the barrier to entry for building websites or plugins, but also the risks and challenges.

We chat about the overwhelming pace of new product creation, and how the real difficulty today isn’t necessarily building a plugin, but successfully marketing, supporting and sustaining it in a crowded ecosystem.

Towards the end, we talk about the potential saturation of plugin marketplaces and what this means for the future of WordPress businesses, especially as AI continues to accelerate product development.

Mark says that he’s embracing AI in his own workflow, but has some nostalgia for the days when coding was a hands-on craft.

Several other points were raised, including the ongoing demand for trusted, supported, software among non-developers, the looming spectre of AI driven security vulnerabilities, and whether traditional CMS platforms like WordPress might see a renaissance if AI hype collapses.

If you’re curious about how AI is shaping, and challenging, the future of WordPress development and product businesses, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Mark Westguard.

I am joined on the podcast by Mark Westguard. Hello, Mark.

[00:03:34] Mark Westguard: Hello Nathan, how are you?

[00:03:35] Nathan Wrigley: Yeah, good. We’re going to have a little bit of a chat today about the landscape of WordPress in the era of AI. Let’s explore and see where we go.

So Mark, before we begin, bio time, basically, would you give us your little bio? Tell us what you do in the WordPress space.

[00:03:50] Mark Westguard: In the WordPress space, currently I’m running, WS Form, which is an online form plugin for WordPress.

And I’ve been in the web game far too long. People can’t see our grey hairs, but I’ve been building websites for, oh, I want to say about 30 odd years now.

Yeah, I’ve gone through everything from Netscape Navigator through to where we are now with AI. So, have been building websites for many many companies, for many many years.

So I had a agency in the UK called Absolute Internet back in the day, back in 1996. And then moved to the States in 2005 and carried on with that, and then got into product about, I want to say eight years ago now. And have been enjoying it, but still dabbling in the agency side of things as well.

[00:04:34] Nathan Wrigley: Okay, so you’ve had a long and storied history. Has there ever been a moment where it’s felt like so much was in flux, in your past? Because, I think anybody really listening to this would have some intuition that AI is a moment of great inflexion point. Maybe this is par for the course though, over a 30 year period in the internet. Has there been anything which has disrupted things or changed things as rapidly as this?

[00:04:56] Mark Westguard: I think, for me it was strange because the internet was there when I started university, but definitely was a big game changer for how we accessed information and searched for information.

The next big thing for me was really the .com bubble, and that going bang quite tremendously, which pulled my first agency into the ground. I mean, we went from 40 odd staff to four people in a day. So that was certainly a big flux in the internet industry that hit me.

Once that recovered, it’s been fairly plain sailing, hasn’t it? There’s been a lot of gentle progression in the internet game. We’ve seen CSS 2, CSS 3. We’ve seen HTML get a little bit better here and there, standards have improved. But nothing like AI. I mean, I remember the first time I typed a question into a bot and got a response back and I was like, okay, this is going to change things.

So yeah, we’re definitely in a big evolution here and one that I think is way more rapid than internet hitting us as well.

[00:05:58] Nathan Wrigley: I think the bit that makes it so profound is the fact that we’ve given over so much of ourselves to the internet. So during the .com boom, there were, I don’t know, how many desktop computers in the UK. I imagine there’s significantly more than there were then than there are now. You know, you had to go and find a computer, sit at a computer, switch the computer on, use things like dial up modems to get access.

[00:06:22] Mark Westguard: Yeah.

[00:06:23] Nathan Wrigley: And all of that kind of stuff, many obstacles. And now everything is in your pocket. So we do commerce in our pocket. We communicate from our, the device in our pocket. In other words, everything is wedded to the internet.

So the idea of things changing rapidly because we’ve become so accustomed to the internet being kind of like a utility. The rapid change is more profound, even if the change itself might not be so rapid.

Can I actually go back to the .com boom and bust bit? Because I bet a significant proportion of the people listening to this won’t even know what that was. Do you want to describe it, and how it crept up on you and overnight just decimated probably billions of dollars from stock markets?

[00:07:05] Mark Westguard: Yeah, it was around about, I want to say 2000, right when it hit. And when we first started as an agency, I was building websites using university computers. I didn’t own a computer. This is what you were talking about. Not everybody could have afford that technology back then.

But we were building websites for the most bizarre stuff. We had people coming in saying, I want to sell curry online. And I want to, anything and everything that they could come up with as with an idea, they were getting funding for.

And we were dealing with small one man bands, but we’re also dealing with big companies that had huge investment, that was pumped into these internet ideas. And it’s kind of similar to what’s happening with AI right now.

There’s an immense amount of money being invested into it. And the internet went from a handful of university websites, to everybody doing all manner of things online. The investment just got over the top. And then at some point somebody went, you know what, these investments have no ROI on them. There’s huge amounts of money being poured into this. And, basically the stock market crashed as a result of it.

And we had companies literally within a week saying, we are no longer going to be continuing our management contracts with you. Or we don’t want to build this website with you anymore. We were building $2 – 300,000 websites for the likes of Safeway and Sony and KPMG and all kinds of stuff. And it just stopped overnight. And it caused a lot of agencies to fall over, just completely fail, within a matter of months.

[00:08:37] Nathan Wrigley: I remember seeing an ad, I was on Kensington High Street in London. I used to work on Kensington High Street, and I remember seeing an ad on a bus stop. So it was a prime bit of real estate in the UK, probably one of the more expensive places that you could put an ad. And it was for an internet product. And the product was that they would come to your workplace, take your shirt, iron it, and bring it back to you. And I remember looking at ad and thinking, is that really what they’re selling? Genuinely? Like, is there a market for that? And obviously, within a month the .com bubble had burst.

But it was on that level, wasn’t it? It was the most peculiar ideas that people could come up with. And maybe some of them would’ve swum now. But back then, everything was sort of sinking. But also nobody had a mechanism to pay for it. We didn’t have the sort of access to credit and credit cards and Stripe and all of those payment gateways and all of that.

It was just, we were falling over ourselves to put ideas out there. Nobody seemed to have the capacity to say, no, look objectively, that’s a silly idea. That there’s no business there. It was more, let’s try it.

And then eventually a bit like happened with the Dutch and the tulips way back. Somebody woke up and said, hang on, there’s no money being generated by these things. Then presumably the bankers all took one look at each other and went, oh, what have we done.

[00:10:04] Mark Westguard: Yeah. And there were a lot of big, big ideas out there that caused a lot of that. I had one guy that came in and I won’t mention the project name, to save the guy’s grace. But he had come up with an idea to do an online training platform for children. And this guy we found out afterwards had maxed out his credit cards, had remortgaged his house, had got divorced from his wife, and a tiny part of the reason for the collapse around 2000. But it was that kind of thing that was happening all over the place.

[00:10:35] Nathan Wrigley: Yeah.

[00:10:36] Mark Westguard: We are seeing a similar thing happening now with AI. There’s a huge amount of investment going into it. Now I’m in no way an expert in the financial world and of investment in AI platforms and stuff, but hopefully we don’t see as big a bang as we did back then.

[00:10:50] Nathan Wrigley: It felt, at the time, it felt really normal until it suddenly didn’t. Until I saw that ad for that shirt ironing business, I genuinely I just thought, oh, that’s a good idea. Oh, that’s interesting. Look what they’re doing. Look what you can do now. Ads over and over again.

But then as soon as it starts to unravel, you begin to get the intuition. Wow, that really was hysteria. We were all caught up in this hysteria. Whether or not you are a financial expert, it must be obvious to everybody that we are caught up in some kind of AI hysteria at the moment.

Now, it may be that 80% of all of the business ideas based around AI will succeed. Maybe it’ll be that 80% of them will fail. But have you got any intuitions that point to it being over egged, hysteria? Are there any things that you’ve seen out in the real world where you’ve thought, boy, that really does feel like a moment where we ought to be thinking about whether we’re caught up in mass hysteria here?

[00:11:48] Mark Westguard: I think AI for me is like the next logical progression. We’re talking about coding here, right? AI is used for lots of different things, but in terms of coding, it’s like the next logical transition in terms of making coding accessible.

So if I think back to when I was in college and I was writing machine code for chips, literally like bite by bite, that was quite complicated. And then came along programming languages where we could not have to worry about the machine coding. And then we’ve got things like, for example Basic on a computer, which meant you didn’t have to worry about some of the more underlying code underneath that.

And then came the internet with HTML. And then we had page builders. Now I’ve got AI where we don’t even have to think about writing a line of code. You can literally just ask it what you want, and hopefully you’ll get out of it what you want. At every stage it has made working with a computer, and making a computer do something more accessible to more people.

So now my father can just go online and say, hey, build me this website. I want a green background. I want this font, I want it to say this. Write me a paragraph about such and such, and they can pretty much whip something up in an afternoon. A year ago, two years ago, that was him having to learn how to code to do that, or would have to use a drag and drop page editor to do that. So it really has opened up the ability to develop software and websites to a lot more people.

The thing that I’m seeing is there’s an awful lot of ideas being developed. People are coming up with ideas. Some people not actually thinking about, is this a project that’s got legs? Do people need this? There’s a lot of repetition going on. There’s a lot of things being built where really, even if you build a website solution or a piece of software, you’ve still got to market that. You’ve still got to support it. You’ve still got to get it out to the masses.

And AI’s not quite there with that yet. I can’t just say, right I’ve built this product, go and market it for me. It’s still going to need some feet on the ground to actually go out there and sell a product.

When I got into software and I developed WS Form, building the actual plugin was a lot easier than actually getting out there and getting people interested in it, and telling people about why it’s a good product. That’s what took the time.

[00:13:57] Nathan Wrigley: That’s a curious insight. So we are in a moment now where almost anybody who’s got the capacity to type on a computer can build anything. And I’m seeing that over the internet at the moment. You said multiple things.

So there’s this person that I follow online, I won’t mention their name. They’re not in the WordPress space at all. And if you follow their trajectory, about a year ago, they clearly got the intuition that they could build an app. And so they did for the Mac, and it was really great. It was really good little app and it served its purpose. It was quite a small thing.

Now, a year later, I would think it’s probably fair to say they’ve probably got about 15 apps. And there was some moment, and I don’t know when it was, probably about the 10th one in, I suddenly thought, how does this person maintain this? Is this just a case of just, okay, let’s build another and another and just keep going through that process. Selling, selling more, selling, more selling. But at what point do the people buying that app get the support that they need and the bug fixes that they need? And that I think is maybe a moment that we haven’t yet faced.

[00:15:02] Mark Westguard: Yeah.

[00:15:02] Nathan Wrigley: The marketing bit. You’ve built a plugin with AI for WordPress, but you don’t have the capacity to market it. So you build another one, and you build another one, and you build another one. But the few people that bought it, they’re going to expect updates and what have you. What I’m basically trying to do is agree with what you said. The wider bit is the harder bit. The selling it, not just building it, and then making sure that those people come back for more later.

[00:15:25] Mark Westguard: Yeah, I think that’s one part that a lot of people are missing. I’m seeing a lot of people saying, hey, I built this and I’m making X million per month. I don’t believe a lot of those posts that you see, with these get rich. If that was the case, everyone would be doing it.

But, I love AI. It’s made my ability to bug test and launch new features so much quicker, and so much more efficient. I just worry that there are so many people jumping into wanting to build businesses with it without thinking about all the other stuff that you’ve got to do to make that business a success.

And that’s kind of what I saw back in the two thousands. I saw a lot of people just coming up with ideas, running with it. They were starters but they weren’t finishers. And the actual marketing of that idea, and getting it supported and everything else was the they fell on.

Yeah, it’s, an interesting time and it’s really hard to keep up with it all because it’s moving so quickly. That’s the bit that for me is a challenge, is just keeping up with the best thing to do. And there are so many people online, on social media that are trying to tell you the best way of doing it. Everyone’s got their own, way of doing it. I’ve had to switch a lot of it off. It’s overwhelming.

[00:16:29] Nathan Wrigley: Okay, so that’s a curious insight. And it was where I was going to go next. I genuinely don’t know what our capacity is to consume this. I don’t know where all the people are going to come from to buy all these things. In order for us to to buy all these things, we must all be earning to pay for all these things. And in order to earn, we all need to be selling our own things or doing some kind of lucrative work somewhere. You know to shell out for these things.

That’s the bit that I’m concerned about. I don’t see where all of these products are going to get revenue from. In the WordPress space, let’s cast our minds back three years. Competition was tough already. You know, you’re in a fairly competitive landscape, WordPress forms, there’s several solutions for that. So that’s already competitive.

Now if you flood the zone with 10 more, 15 more, a hundred more, that means it’s much more difficult for everybody to achieve the sort of the weight that they need to have to make that profitable.

It’s very hard to encapsulate what I’m trying to say, but it basically boils down to what is our capacity to attend to all of this stuff. And I was thinking this morning, coincidentally before you and I joined the call, I was thinking before computers came along, I know life wasn’t as rich and wasn’t as varied, but it was a heck of a lot less noisy. And we really do allow a lot of noise to get into our lives. And it feels like AI, WordPress, it’s very noisy at the moment. And I don’t think we’ve yet crossed that Rubicon. The noise, it’s become obvious to us how disruptive that noise was.

[00:18:07] Mark Westguard: Yeah.

[00:18:08] Nathan Wrigley: I think we’re still, in many cases, plugin vendors and theme vendors and things are still relying on previous year’s subscription to renew, but it’s the next year that I worry about and the year after that. And I don’t know if you’ve got any wisdom there.

[00:18:23] Mark Westguard: It’s an interesting time. I think there’s a lot of experimenting going on that is being portrayed as the way to do things. There’s a lot of people, I guess there’s a lot of people panicking. There’s even a lot of people in the WordPress world that have gone from WordPress to now saying, I’m not doing WordPress anymore, and they’re now a hundred percent AI. And, are they actually producing things that are making them a living? Other than maybe, some of these online content producers. Are there solid products that are coming out of AI?

If you just look at the plugin repo, the number of plugin submissions has gone through the roof because so many people can now just produce utility plugins so quickly and easily. There are still only a handful of people out there actually producing proper products, that are selling as plugins for WordPress, sizable plugins that are really expensive to build with AI. I’m fortunate that I didn’t have a suite of small utility plugins. I had quite a large form engine that I intentionally built to be quite complicated, and that’s kept me afloat.

[00:19:23] Nathan Wrigley: Oh, I see. You’ve got like a walled garden around your product a bit because of its complexity, but also it’s not a utility in the sense that you toggle something on and then something happens on your website. I don’t know, SMTP plugin or something like that. It just this one thing and it does it, and that’s all it does.

Yours is much more broad, deep, there’s a learning curve, but also it performs an essential function on the website. If that was to go away, your forms disappear from your website, that’s catastrophic potentially. So you’ve created a bit of a moat around yourself because of that.

[00:19:57] Mark Westguard: Yeah, I don’t think I created it. I just think that happened. Almost the marketing of the product has changed. I used to be pushing, hey, no code forms just drag and drop. Some people don’t even use the UI anymore. They literally are just using AI to talk to it, because it has the MCP server on it. So it has become more of an engine than a user interface for building a form.

And, we were going to talk briefly about block themes and stuff, on this call and I had recently transitioned my theme on my website from a classic theme to a block theme. And the amount of work that went into that was a lot more than I thought it was going to be with AI. And that’s because I think AI still is filling in the holes a lot.

So, the more vague your prompt is, the more AI’s got to do to fit in the gap. So if I just say to it, build me a website, it’ll build you a website, but you are going to have, umpteen different things that it has assumed that you want along the way.

When I was building my block theme, using AI, there was a lot of prompting I had to do to get it to look the way I wanted it to look. And it took a lot more, I forget how many prompts it was now. It was several hundred prompts in the end to get it where I wanted it to be.

Glad I did it. And I did it a lot quicker than I would’ve done had I hand coded it for sure. And it did things that I am not very good at doing, like writing a block from scratch, that’s still something that I struggle with, and it was really helpful to be able to do that with AI.

You see this in social media, people saying, oh, that guy’s built a website and it looks like it was built from AI. And that’s basically AI fitting in the gaps with what it’s been taught that people want. Certain fonts, certain things like that. So you can definitely use it to, I’ve completely digressed here but, you can definitely build it to build things quicker, but it still takes time to prompt it properly.

And also with someone with programming knowledge, I’m still steering it in certain directions to make it work the way I want, and to make it work efficiently. I’ll still look at code that AI generates and be like, what are you doing?

[00:21:51] Nathan Wrigley: I was just going to interrupt there and say, I guess the curious bit about this is that in in every epoch until now, the frailty of the human being, our capacity to forget things, the fact that we can only allocate a certain amount of our brain to a given task. We require sleep and all of these kind of ordinary things. And we get unwell, we’re not always as efficient one day as we are the next, because we went out the night before, and those kind of things.

I suppose that is also a part of the jigsaw puzzle, which has me concerned, is that the state of AI. Let’s assume a trajectory which is the same as the last five years. Let’s assume that in the next five years the trajectory’s going to be the same. Of course it may not turn out that way, but let’s assume that it does. The worst is now. The worst that an AI can do is today, and tomorrow it will be better, and the day after that, it will be better. And it will never be worse.

And so those little wrinkles that you described, you have to prompt it 200 times to get yourself a website. You’ve got to assume that the combined kind of Borg-like, that’s a Star Trek analogy, kind of Borg-like nature of AI, is that in a year’s time, it’ll be a hundred prompts. The year after that, or six months after that, it’ll be down to 50, and then 20, and then 10. And you get what I’m saying.

You know, it just get’s exponentially better. It never gets worse. That, I think, is the bit that me the most. Is that because it’s beguiling and because as technologists we love shiny stuff, that we don’t see this giant problem building behind our backs. That if we’re constantly beguiled by the shiny, and we give everything over to the AI, maybe there’ll come a point where we look and we suddenly realise, oh, it’s now superior than I am in every single regard in terms of website building. So who’s going to use my services anymore?

[00:23:42] Mark Westguard: Yeah.

[00:23:43] Nathan Wrigley: And I find this a curious thing in the WordPress space, because a lot of people seem to be hyping AI to the exclusion of their future selves.

[00:23:54] Mark Westguard: Yeah. Yep.

[00:23:55] Nathan Wrigley: But they can’t, it’s irresistible. You have to do it, because if you don’t, your competitor will. And so you know, the arms race argument comes out and on we go. And it’s a curious thing that we’re in this moment.

[00:24:08] Mark Westguard: It’s a funny time for sure. It’s the buzzword. It’s what everybody’s focusing on right now. I’m doing it. I am using it as much as I can. It’ll be silly for me not to do that. I embrace it.

You know, I was working with James LePage and his team at Automattic when they were developing all of the different AI building blocks. And he very kindly kept me ahead of what was going on there.

And I’m very thankful for that because it’s one of the things that’s made my product ahead of some of the competition. And I’ve got people now recommending WS Form because of the AI capabilities that it has.

But it’s a completely different way of thinking and working from what I was used to. For me to add a new feature meant adding a new UI interface for it, and writing all of that from scratch. And we were talking before this call that I would probably spend a day or two implementing a new feature and working it out. And I used to love that. That used to be good for my brain.

And I was thinking the other day, I am getting to the point where I’m not thinking anymore. Because I, it just, it’s doing the thinking part of it for me. But my experience in building just that block theme from my website taught me that, much like going to an agency and telling it what logo you have and what colours you have and how you want things to look and how you want things spaced out. All of that initial discovery period still needs to be done with AI in order to get it to do what you want.

Now, like you say, it’s going to be able to do that more and more efficiently. You see that with like Claude design where you can set up a, I forget what they call it now, but you kind of build like a design set.

[00:25:39] Nathan Wrigley: Yeah, like a brand kit kind of thing?

[00:25:40] Mark Westguard: Yeah. Where you give it your logo and your styling and everything else. And you can give it, even the current web address of your site and it’ll feed that in. And then it can then use that to build new elements.

So, there’s still a lot of prompted stuff that goes on. I think there’s a little bit of a myth that you can literally one prompt AI for a lot of things, and get some output from it.

One of the interesting things for me is I went to an AI event once, and I met a guy who was, I think he was ex OpenAI. And he said to me and this may or may not be true, but the fundamental software powering everything in AI, the concept behind it has kind of hit a threshold. And what we are now doing is tweaking that and making that work better. We’re tuning it, fine tuning it.

And that’s where we see an improvement in AI and obviously in processor speed and everything else that’s going on. So it’s interesting that kind of the fundamentals of AI are really at a maximum, in terms of what it can do. But it’s really human tweaking it and training it that’s making it work an awful lot better. And I think that’s where a lot of the improvements are going to come from.

[00:26:38] Nathan Wrigley: You mentioned a little bit ago that you’ve really not required to write code anymore in order to improve your plugin. You can get AI in the loop there and tweak it and iterate on it that way. Do you miss that though?

[00:26:51] Mark Westguard: Yeah, I really do.

[00:26:53] Nathan Wrigley: Is there a bit of you that you could close the box on AI and just rewind the clock and go back to the way it was? Because presumably it wasn’t all roses and unicorns over there. It was hard work and probably kept you awake at night and you’re banging your head against the desks, or how do I do this? Is there some kind of halcyon days thinking there, you know, ah it was better before AI. Would you parcel it up and send AI packing if you could, or are you more happy with it.

[00:27:18] Mark Westguard: It’s a love hate relationship for sure. Love hate relationship. I think, much like a carpenter loves doing woodwork. I used to love coding, call me a nerd. But that was my trade. That’s what I did. And I used to love working things out. And that working out is what kept my brain ticking over.

Now if I have something I need to do, I can get AI to build it. Now, I will absolutely, and that’s hopefully where the quality of my product comes is, I’ll go and check what it’s written. I won’t just implement it and launch it. I will always check what it’s done, and nine times outta 10 I’ll find better ways of doing it. Just because of the way that it’s implemented it. It may not understand that I’ve got a method in my code somewhere that already does that. So I don’t want it to recode it.

But the more and more I use it, the more it seems to understand my code base, and the way it works. And it’s getting better and better. It is like having an assistant in the office that can just deal with the coding for me now. But I do miss it. I really do. Sometimes I’ll just get my hands dirty and do a bit of coding for the old days, but I sit there thinking I could have just prompted AI and it would’ve done it in five seconds. So it’s yeah, it’s weird.

[00:28:22] Nathan Wrigley: It’s almost like a hobby. You take time off and pursue a hobby of coding as opposed to the business of coding, which is kind of curious.

[00:28:28] Mark Westguard: Yeah. And I do miss that. Yeah. And it was a hobby. You would get questioned sometimes, what’s your hobby? And I’d think, oh, is it? What do I? Do I write swimming or, or eating at a restaurant? I’m like, no, I actually, yeah, I used to love coding. My hobby was my job, and I was very lucky in that regard that I was doing what I enjoy doing as a career. So that, yeah, part of that’s missing now. And I do miss it.

But at the same time, I love technology and I love seeing new things come to fruition. And I’ve loved learning about and taking advantage of AI. And there’s been things in my product that people probably aren’t even aware that are little bugs that have just been niggling at me that I’ve never got round to fixing.

[00:29:08] Nathan Wrigley: And now you can.

[00:29:08] Mark Westguard: I just spend a day and I’m just like, you know what? Fix that little pixel that’s out that’s been bugging me all these years, and it’ll work it out for me.

[00:29:16] Nathan Wrigley: I am so torn on this subject because I, like anybody that enjoys technology, I really love when I see a new thing. Whether that’s a piece of hardware or software or the capacity of somebody to do something new, raising the standard of people to do a thing. So on that side of it, it’s all, like I said, unicorns and rainbows. It’s brilliant.

But there is a bit of me, which I think growing in size, which is very concerned. And there are so many underpinnings to that. The people growing up now presumably will not be able to go through the process of learning that you went through. Because what would be the point in spending all those hours learning to do all of the things that you had to do and bang your head against the desk. And so that worries me.

It worries me that if we flood the landscape, our capacity to engage with that is going to go away. Like, how many Mac apps can we have and how many WordPress plugins can we have? At what point does that marketplace become so saturated that nobody can make a living from that anymore? I don’t know if that’ll turn out to be the case. But there’s just this niggling thing that there’s maybe going to be some correction.

And I think the bit, which seems to be raising its head at the moment is AI’s capacity to go out and cause mischief in terms of security vulnerabilities and hacking and things like that. And I do wonder if that will be the thing which enables governments, for example, or regulatory authorities and things like that, to say, wait, the brakes need to go on now.

[00:30:54] Mark Westguard: Yeah.

[00:30:55] Nathan Wrigley: We need to figure out how was this allowed to happen? How is it that our banking systems collapsed? Or how is it that the fridges all got switched up to 50 degrees centigrade?

[00:31:04] Mark Westguard: Which they did.

[00:31:04] Nathan Wrigley: Which they did. How did we allow this to happen? But at the moment, we’re in that kind of free market phase of let it all go wild. But I’m not sure that’s going to be possible forever.

[00:31:16] Mark Westguard: I think it’s going wild on the software side. It’s also going wild just on the infrastructure side right now. The amount of money that’s being pumped into building these server farms and everything else, it’s just off the charts crazy.

Who knows how much this stuff actually costs to run. I feel like we’re in an age where we’re getting quite a good deal on this stuff at the moment. Because we’re in the initial Google phase where Google didn’t have Google ads. It was literally just a search engine and losing huge amounts of money.

It was only when they monetized it that they started to make some kind of profit, and even that took them a long long time. And we are there with these AI farms. They’re huge buildings, massive amounts of investment. And we are paying $20 a month to utilise, effectively, we’ve each got a super computer from a decade or so ago on our desk now.

[00:32:02] Nathan Wrigley: Yeah you’ve got God-like capabilities for a few dollars a month.

[00:32:05] Mark Westguard: I know. Yeah.

[00:32:06] Nathan Wrigley: It’s genuinely insane. Okay. So that’s an interesting point as well. I wonder, so two things here.

The first one is, I wonder if a potential course correction there. The economic model turns out to be unsustainable. And it either collapses or it slowly sort of changes and the fees go up and the capacity to use it goes down. So there’s that.

But also, I wonder if more local AI systems where you download something onto your computer and utilise it there. As opposed to needing the big thing out in the, server farm, the data centre, nobody wants them near their backyard. It certainly seems like that in the UK and it sounds like North America is the same.

The follow on from that is then I wonder if there will be some kind of resurgence for older technology like WordPress. Okay, that was all a bit of fun. We all had a great time playing with the AI, but now that it’s gone in the way that we got familiar with, let’s just revive all the things that we knew used to work. Like our old trusty CMS, WordPress.

I think that’s that’s a possibility, right? The curiosity will dwindle in AI and it will return. Certainly that seems to be the kind of pivot that a lot of people in the WordPress space are hoping for. You know, that AI won’t be able to update your website in the way that clients wish. Use a trusty CMS. AI is going to collapse. Don’t worry, you’ve got the old technology like WordPress, that CMS in your back pocket.

I don’t know if any of those will turn out to be the truth, but certainly an interesting piece to put on the chessboard.

[00:33:37] Mark Westguard: Yeah. And I talk to a lot of plugin developers. Obviously, I’ve got a big community of friends that build plugins and we’re all seeing a decline in new customers. And I think part of that is economy. I think part of that is AI. I think that when I think about it and I look at who I’m looking at like on social media, a lot of those people are very good developers. They’re people that are pretty high up on the WordPress ladder, and developed tools and have developed software themselves.

But there’s still a massive user base in WordPress of people that just want to buy a piece of software that’s tried and tested and works. And don’t want to have to work out how to do that with AI. And go through that because, you could, get AI and say, okay, build me a plugin. And then they’re like, okay well, how do I deploy that? How do I test it? How do I do the security on it? Anyway, there’s a lot that goes into it.

And building stuff from scratch, sometimes, isn’t the best way of doing things. For a lot of people that are developers and know how it all works, it’s great. I can build utility plugins day in, day out now. I don’t even build custom field stuff. I don’t even use a custom field plugin now because I can do that with AI for my own theme. I don’t need it.

If I build a site for a customer, then a lot of the custom stuff I am just writing myself because it’s a few lines of code and AI can do that for me. But there’s still people that aren’t developers. They’re not coders and they just want to be able to buy a bit of software for 50 bucks or whatever, install it, and then it does its job.

[00:35:00] Nathan Wrigley: So that’s a curious thing. And I would fit into that camp. If you took me into any industry apart from web development, WordPress, and you asked me to be confident with, okay, you’ve got the AI thing over here, or you’ve got the $50 thing over there, which somebody else is going to maintain, and you can kind of phone them up if the products itself wouldn’t work.

Genuinely I’m going to pay for the $50 thing, or the a hundred dollars thing. I would never rely on AI. And think about WordPress websites. The amount of clients that I had over the years, who wouldn’t even dare to click the save button, because they were terrified that what they were about to do might in some way just destroy the website, you know, and and they would constantly seek reassurance. Are you sure that I can click save? Yeah. Yeah. click save. It’s absolutely fine. Those people are not going away anywhere.

Although we may become slightly more forgiving of AI, and slightly more trustworthy of it. I think most people in the world, most people in the world, let’s say this sentence again, have never touched an AI.

[00:35:57] Mark Westguard: Yeah.

[00:35:58] Nathan Wrigley: They don’t even know how to interact with it. They wouldn’t know what to do with it if you put it in front of them.

We’re that tiny cabal of people who because we’re on the computers already every day AI and code kind of fit hand in glove, we assume that the rest of the world is happy with this stuff and honestly they’re probably not.

[00:36:16] Mark Westguard: Yeah, and the WordPress world is not a hundred percent developers using it. It’s, there’s a lot of just regular end users that want to build a website, or have in the past maybe installed a classic theme or a block theme, or gone to a developer to build themselves the site. But they’re still using blocks of software to this day.

I mean, every customer that I’ve got is built on WordPress. They’re happy with it, they’re still using it. I work with some very large companies and they’re still using WordPress as the foundation. And we take advantage of AI to be able to roll things out quicker, which is great.

But if I wanted to, if there’s a piece of software that’s quite complicated and that the website relies on it, I won’t necessarily build that with AI. I’ll use an off, piece of off the shelf software that is tried and tested and works, and has the support there for it. I do a lot of stuff with Salesforce, for example, and that could be quite complicated. And, it would take a while to get some of the stuff that we’ve built still done with AI. And there’s pieces of software that we are running that we just pay, 50 bucks a month for and it works, it does the job.

[00:37:14] Nathan Wrigley: I think it’ll be a really interesting moment in the next couple of years seeing where we get with this. Not only whether AI can financially support itself, but whether or not there are outcomes which AI presents to the world that are not aligned to our best interests. Hacking scandals, those kind of things. Whether or not we turn our backs on it and say, put it back. We did enough with AI, we had an experiment with it, and it went slightly pear shaped.

[00:37:37] Mark Westguard: It was great for cat videos.

[00:37:38] Nathan Wrigley: It was brilliant for making videos of yourself, or your politician of choice, doing something that they actually didn’t do. Those kind of things. It was a lot of fun. I mean it’s so beguiling, but who knows where we’ll get to in the year 2027, 2028.

[00:37:55] Mark Westguard: It’s an interesting time.

[00:37:57] Nathan Wrigley: Let’s hope we’re all here to. Yeah, that’s right. We hope we’re all here to experience it. Let’s knock it on the head there. Mark Westguard. Where can we find you online?

[00:38:04] Mark Westguard: wsform.com. Just go on there. You can find information about the product. You can find me on, I’m on Twitter, Facebook all over the place. If you search for Mark Westguard, I’m going to come up. There aren’t many Mark Westguards in the world, so.

[00:38:17] Nathan Wrigley: Perfect. Alright, thank you for chatting to me today. I hope that we both get through to 2027. Take care Mark.

[00:38:23] Mark Westguard: Take care. Bye.

On the podcast today we have Mark Westguard.

Mark has been building websites for over 30 years, starting out in the early days of the web with his agency Absolute Internet in the UK, before moving to the US and transitioning into product development. He now runs WS Form, a form plugin for WordPress.

During this episode we get into the evolution of the internet and WordPress through major technological inflection points, most recently, the rise of AI. Mark draws comparisons between the AI era and the frenzy of the dot-com boom, sharing how rapid influxes of investment and hype can reshape the entire landscape, often faster than the underlying technology can deliver sustainable results.

The conversation focused not just on the opportunities AI brings to developers and end-users, such as dramatically lowering the barrier to entry for building websites or plugins, but also the risks and challenges. We chat about the overwhelming pace of new product creation, and how the real difficulty today isn’t necessarily building a plugin, but successfully marketing, supporting, and sustaining it in a crowded ecosystem.

Towards the end we talk about the potential saturation of plugin marketplaces and what this means for the future of WordPress businesses, especially as AI continues to accelerate product development. Mark says that he’s embracing AI in his own workflow, but has some nostalgia for the days when coding was a hands-on craft.

Several other points were raised, including the ongoing demand for trusted, supported software among non-developers, the looming spectre of AI-driven security vulnerabilities, and whether traditional CMS platforms like WordPress might see a renaissance if AI hype collapses.

If you’re curious about how AI is shaping, and challenging, the future of WordPress development and product businesses, this episode is for you.

Useful links

WS Form

by Nathan Wrigley at November 18, 2026 01:00 PM

Matt: New TLDs

For the first time since 2012, there’s a new round of TLDs being created by ICANN, and we just had string confirmation day!

I’m happy to share that Automattic is uncontested for .jazz, .php, .soul, .wordpress, .tumblr, .woo, and I personally got .matt.

We have really enjoyed shepherding .blog which has turned into a nice option with a pretty clean namespace (that’s why we have premium prices on renewal, not just registration) and it’s had some high profile adoption, for example github.blog, stackoverflow.blog, seths.blog (Seth Godin), tim.blog (Tim Ferriss), noahpinion.blog (Noah Smith), steve.blog (Steve Jurvetson), and mgs.blog (M.G. Siegler) and ~ 395,000 more. 🤠

You can see all the still contested TLDs here.

by Matt at November 18, 2026 10:53 AM

Open Channels FM: Finding Your Edge as the Web Ecosystem Evolves

Remkus de Vries shares how agencies and professionals can adapt to industry changes and take charge of their business direction.

by Bob Dunn at November 18, 2026 10:22 AM

Matt: Who Wrote What

The debates and fire around authorship are playing out faster in literature and other languages than you may be aware of. The best summation of this so far is Brunella Tipismana Urbano’s translated from Spanish essay The Part About the Machines.

The role of intellectuals is to shed light on these crossroads, to, as George Scialabba once wrote, understand their contemporary moral and political significance for the present with singular originality and force. And yet, confronted with a genuinely new phenomenon, our intellectuals have chosen to close their eyes. They have happily chosen ignorance.

by Matt at November 18, 2026 01:20 AM

November 17, 2026

WordPress.org blog: WordPress 7.2 Release Candidate 1

The first Release Candidate (“RC1”) for WordPress 7.2 is ready for download and testing!

This version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended to evaluate RC1 on a test server and site.

WordPress 7.2 RC1 can be tested using any of the following methods:

PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)
Direct DownloadDownload the RC1 version (zip) and install it on a WordPress website.
Command LineUse this WP-CLI command:
wp core update --version=7.2-RC1
WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser.  No setup required – just click and go!

The scheduled final release date for WordPress 7.2 is December 8, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who contributes by testing!

Please continue checking the Make WordPress Core blog for 7.2-related posts in the coming weeks for more information.

Core Changes Since Beta 5

Check out the Beta 1 announcement for details on WordPress 7.2.

You can browse the technical details for all issues addressed since Beta 5 using these links:

WordPress 7.2 Release Candidate 1 brings additional bug fixes, accessibility improvements, and compatibility updates as the release moves closer to its December 8 launch.

Recent refinements include fixes to client-side media uploads, improvements to the new random-content redirect feature, and better keyboard navigation through a skip link in the WordPress admin bar. Additional updates improve plugin dependency messaging, script module translations, and the reliability of the HTML and Interactivity APIs.

Developers will also benefit from continued Abilities API refinements and updates to bundled libraries, including PHPMailer, Requests, getID3, and sodium_compat.

Learn more: Trac #66490, Trac #66681, Trac #66625, Trac #66331, Trac #66591, Trac #65984

Additional Block Editor Improvements

WordPress 7.2 RC1 includes further refinements to the block editor, addressing issues with duplicated block content, keyboard interactions on iOS, and revision previews. Improvements to the Interactivity API prevent outdated navigation responses from replacing newer content, while additional fixes improve plugin installation workflows, featured image compatibility, and link suggestions. The transition to modern SVG icons also continues throughout WordPress administration.

Learn more: GitHub #86839, GitHub #86703, GitHub #86608, GitHub #78367, GitHub #86854

Want to know more about this release? Here are some highlights:

  • New Ipsum default theme
  • Expanded responsive design and Gallery controls
  • Improved Global Styles and typography tools
  • Enhanced Canvas Notes and collaboration
  • New DataForm block settings inspector
  • Faster media uploads and image processing
  • Modernized WordPress admin with SVG icons
  • Faster admin navigation and asset loading
  • New “On This Day” widget and random post discovery
  • Improved translation update management
  • Accessibility, security, and PHP 8.6 compatibility improvements

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. 

Your help testing the WordPress 7.2 RC1 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.2.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 7.2 beta releases. With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.2.

If you find compatibility issues, please post detailed information to the support forum.

Test on your hosting platforms

Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.

Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. Thank you to all web hosts who help test WordPress!

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

An RC1 haiku

The final bugs fall
Release candidate takes flight
Launch day draws nearer

Props to @audrasjb, @r1k0, and @courane01 for collaboration and review.

by David Baumwald at November 17, 2026 04:04 PM

Open Channels FM: What to Expect from the Open Web Conversations Podcast

Conversations about the state of the open web and what shapes its future.

by Bob Dunn at November 17, 2026 11:39 AM

Matt: Triple Rainbow!

While driving between meetings at the Semafor World Conference and San Francisco, I snapped a quick photo of a double rainbow but it turned into a triple rainbow with the iconic Flintstone House.

It’s been a strange few weeks, but driving through the rain and sun and seeing three rainbows reminded me that the storm and the light usually arrive together. Staying optimistic.

by Matt at November 17, 2026 02:02 AM

November 16, 2026

Open Channels FM: The Personal Transition: From Human Code Reviews to AI Collaboration

Adopting AI in software development requires a shift in approach, emphasizing trust, automated processes, and robust guidelines to foster creativity while reducing micromanagement and enhancing productivity.

by Open Channels FM at November 16, 2026 04:22 PM

Open Channels FM: What Is Open Channels FM Podcast Network?

Meet our four shows dedicated to signal, news, and insight for open source and the open web.

by Bob Dunn at November 16, 2026 11:16 AM

bbPress: bbPress 2.6.22 is out!

bbPress 2.6.22 was released on November 15, 2026. It is a security and maintenance release. Everyone running bbPress should update. 🔒

This release strengthens access checks for forums, topics, replies, attachments, REST media changes, BuddyPress group moderation, and public discovery. Protected bbPress content is kept out of sitemaps, attachment comment feeds, embedded content, and listings without the required access.

Maintenance fixes improve topic and forum trash, restore, spam, unspam, and deletion performance, preserve interrupted restore lists, and report failed database queries in the forum reset tool. Block theme rendering, importers, WordPress navigation, BuddyPress compatibility, daylight-saving time handling, and PHP compatibility also improve.

bbPress 2.6.22 still requires WordPress 6.0 or newer and PHP 7.2 or newer, and is tested through WordPress 7.1. The database version remains 264, so no database upgrade is required. Imported Vanilla users with 32-character hexadecimal plaintext passwords may need a reset. The 2.6.22 upgrade notes cover compatibility details.

The 2.7 development branch remains 2.7.0-alpha-4. Thanks to joaquinferrero, zonduu, and konnektiv for contributions included in this release, and to everyone who helped report, review, and test the changes.

Download bbPress 2.6.22 from WordPress.org, or update from your WordPress dashboard when the update is available.

by John James Jacoby at November 16, 2026 05:16 AM

November 14, 2026

Matt: Eric’s Memorial

Eric’s memorial is today in Wichita Falls, there will be a Zoom for people to attend remotely.

James Grierson has a great post remembering Eric. More links and my own writing on Eric is here. I can’t believe it’s been a month already… I find myself returning to his blog or tribute site frequently when going through something tough at work.

In the service pamphlet Eric’s wife Sara wrote something beautiful, “Be the things you loved most about him.” And this quote from Eric himself:

“Build a life with enough margin to help others when they need it, and enough humility to accept their help when it’s your turn.”
— Eric Binnion, July 18, 2026

Rest in peace, brother. We miss you dearly. Your life and legacy continues to be an inspiration to me and others.

by Matt at November 14, 2026 06:48 PM

November 13, 2026

Dave Smith: What if WordPress was built for Users not Developers – Create not Learn

What if the WordPress site editor was designed around what you want to do, not how WordPress is built? In this video I walk through Create Not Learn, an experimental plugin that explores one possible answer. It uses everyday words, starts from tasks rather than menus, and keeps the complex tools out of the way until you need them. We’re using it to test ideas with real people…

Source

by Dave Smith at November 13, 2026 02:55 PM

Open Channels FM: AI and the Changing Landscape of Game Preservation

Artificial intelligence is reshaping the way classic video games are preserved and enjoyed. As AI-assisted tools become more accessible, developers can reverse engineer, emulate, and port games to hardware and operating systems they were never originally designed for. This trend is lowering the technical barriers that once kept old games locked away on obsolete platforms. […]

by Open Channels FM at November 13, 2026 02:06 PM

WordPress.org blog: Copy Your WordPress Site with Reprint

Reprint is a free, open-source, PHP-based tool that copies a WordPress site’s files and database. The plugin is available in the WordPress.org Plugin Directory, along with the command-line client used to copy the site.

WordPress has long let you export your posts and pages. Moving the site itself means bringing along its theme, plugins, uploads, and settings, too. Making that easier has been part of WordPress’s Data Liberation work since 2024.

Example use cases

You can use Reprint to copy your site to a new host, or to create a local copy meant for testing.

While moving your site to a new host, visitors can keep using the original. Use Reprint to copy the site, and then open the copy to check that your pages load, your images appear, and your forms work before you send visitors there. When you’re ready to switch, pause changes on the original site, make one last copy, and point your domain to the new host. The step-by-step guide to moving your site walks you through the move.

You can also use Reprint to create a site copy meant for testing, a place to try changes without affecting the site your visitors use. Copy your site to your computer or try the experimental, browser-based option in WordPress Playground. Use the copy to try a new layout with your existing pages, see how a plugin fits into your site, or check that everything still works after a WordPress update.

How Reprint copies a site

Reprint sends your files and database directly to the computer or server you choose, one piece at a time, without needing to connect to an external service. The transfer can begin without your old host having to make room for an archive of the whole site.

If the connection drops during the copy, you can resume from the last saved point. If you give Reprint a new site address, it can update links that point to the old one. It builds on the WordPress Importer’s approach to rewriting links and applies it to the copied database, including links stored in site settings, blocks, shortcodes, and complex data structures like serialized data or custom fields safely without corrupting tables.

When copying a site repeatedly, Reprint figures out what changed since the last time and copies only the files it needs.

Try Reprint

You don’t need to connect your own site to see how Reprint works. Try the experimental, browser-based option in WordPress Playground. You can copy a sample site right in your browser, with nothing to install.

When you’re ready to work with your own pages and settings, start with a test site you manage. The guide to making your first copy takes you from installing the plugin to opening the copied site on your computer.

by Adam Zieliński at November 13, 2026 12:00 PM

Open Channels FM: After the Announcement, Open Channels News Week in Review

This week’s news looked at AI, open-source licensing, security automation, regulatory software, enterprise spending, SaaS alternatives, maintenance challenges, patents, and credential risks.

by Open Channels FM at November 13, 2026 10:13 AM

WordCamp Central: WordPress Campus Connect 2026 at Compact Polytechnic Institute, Feni

On November 12, 2026, WordPress Campus Connect took place at Compact Polytechnic Institute, Feni, Bangladesh, bringing together students, WordPress enthusiasts, speakers, and community members for a day of learning, knowledge sharing, and exploring opportunities within the global WordPress ecosystem.

The event was designed to introduce students to WordPress, modern website development, open-source contributions, plugin development, artificial intelligence, and career opportunities in the WordPress ecosystem.

Throughout the event, participants had the opportunity to learn from experienced speakers, explore different areas of WordPress, and discover how they can become active members of the global WordPress community.

Event Sessions and Speakers

The event featured five sessions covering different aspects of WordPress, from modern website development to community contributions and career opportunities.

1. Building Modern Websites with Blocks & Full Site Editing

Speaker: Muhibul Haque

Time: 10:15 AM (+06)

This session focused on the modern WordPress editing experience and how the Block Editor (Gutenberg) and Full Site Editing (FSE) are transforming website development.

Participants explored different types of WordPress blocks, learned how to combine blocks and patterns to create engaging page layouts, and discovered how block themes work.

The session also covered customizing essential website elements, including headers, footers, templates, and navigation, directly through the WordPress Site Editor.

Key topics included:

  • Introduction to the WordPress Block Editor (Gutenberg).
  • Exploring different block types and their practical uses.
  • Creating page layouts using blocks and patterns.
  • Understanding Full Site Editing (FSE).
  • Working with block themes.
  • Customizing headers, footers, templates, and navigation.

2. Building the WordPress Ecosystem Through Plugin Development

Speaker: Foysal Imran

Time: 11:00 AM (+06)

WordPress is not just a website-building platform; it is a growing open-source ecosystem powered by developers and contributors worldwide.

This session introduced participants to the role of plugin development in extending WordPress functionality and solving real-world problems.

The discussion covered the fundamentals of WordPress plugin development, plugin architecture, and how developers can build custom solutions to meet different website requirements.

Participants also learned about contributing plugins to the official WordPress.org Plugin Directory and how open-source development can help them improve their technical skills, build portfolios, and explore career opportunities.

Key topics included:

  • Introduction to the WordPress ecosystem.
  • Understanding WordPress plugin architecture.
  • Fundamentals of plugin development.
  • Building solutions through custom plugins.
  • Contributing to the WordPress.org Plugin Directory.
  • Career opportunities through open-source development.

3. Getting Started with WordPress Contributions: Learn, Practice & Contribute

Speaker: Atikur Rahman

WordPress.org Profile: Atikur Rahman (@atik0130961)

Time: 11:30 AM (+06)

I had the opportunity to lead this session and introduce students to the WordPress open-source community and the different ways they can contribute to the project.

One of the most important messages I wanted to share was that contributing to WordPress is not limited to developers or people with advanced coding knowledge. Anyone interested in learning, sharing knowledge, and helping others can become part of this global community.

We explored the different WordPress contribution teams and discussed how people with different skills and interests can contribute to the project.

I also introduced participants to WordPress.org and demonstrated some practical ways to get started with contributing.

The session covered three practical contribution opportunities:

Creating a WordPress.org Account

Participants learned about creating their WordPress.org accounts, setting up their profiles, and becoming part of the WordPress community.

Contributing to the Polyglots Team

I introduced the WordPress Polyglots team, which works to make WordPress accessible to people around the world through translation.

We explored how contributors can participate in translating WordPress, plugins, and themes into Bangla and help make WordPress more accessible to Bangla-speaking users.

Contributing to the Photo Directory

Participants also learned about the WordPress Photo Directory and how they can contribute photographs to this open-source resource.

This demonstrated that contributing to WordPress does not always require programming skills. People with different interests and abilities can make meaningful contributions.

Key topics included:

  • Introduction to the WordPress open-source community.
  • Understanding why WordPress contributions matter.
  • Exploring different WordPress contribution teams.
  • Ways to contribute beyond coding.
  • Getting started with WordPress.org.
  • Creating a WordPress.org account and setting up a profile.
  • Understanding the Polyglots team and Bangla translation.
  • Exploring the WordPress Photo Directory.
  • Practical demonstrations of contribution opportunities.
  • Building skills through open-source collaboration.

My goal was to help students understand that they do not need to wait until they become professional developers to start contributing. They can begin their contribution journey while learning.

4. WordPress & AI: Exploring Smarter Tools and Practical Applications

Speaker: Sayeeduzzaman Noor

Time: 12:00 PM (+06)

Artificial Intelligence is changing how websites are developed, content is created, and digital experiences are managed.

This session explored how AI tools can be integrated into everyday WordPress workflows to improve productivity, save time, and make website development more efficient.

Participants discovered how AI-powered tools and plugins can support website creation, content generation, SEO, coding, debugging, and design-related tasks.

The session also included practical examples of using AI in real-world WordPress projects.

Key topics included:

  • Introduction to AI in the WordPress ecosystem.
  • Exploring AI-powered WordPress tools and plugins.
  • Using AI for content creation.
  • Generating website copy and digital content.
  • AI-assisted website development and debugging.
  • Improving productivity through AI tools.
  • Understanding the opportunities and limitations of AI.

5. Opportunities for Students in WordPress

This session focused on the opportunities available to students who want to build a future in the WordPress ecosystem.

WordPress offers opportunities beyond website development, including freelancing, entrepreneurship, open-source contributions, community participation, and professional collaboration.

Participants explored different career paths and learned why developing practical skills, building a portfolio, and participating in the community can help them grow professionally.

Key topics included:

  • Introduction to the WordPress ecosystem.
  • WordPress career opportunities.
  • Freelancing and earning opportunities.
  • Open-source contributions.
  • Portfolio building and skill development.
  • Learning roadmaps and career growth.

My WordPress Journey: From Student to Mentor to Community Speaker

Being part of this event as a speaker was a meaningful experience for me.

My journey with WordPress started as a student who wanted to learn how websites are built and understand the opportunities available in the WordPress ecosystem.

As I continued learning, I discovered something even more valuable: WordPress is not only about building websites. It is also about learning together, sharing knowledge, helping others, and contributing to an open-source project used by people around the world.

After becoming involved in the community, I started contributing to different areas of WordPress and supporting other learners in their journeys.

I completed the WordPress Credits course, became involved in community activities, and later took the opportunity to support students as a mentor.

My involvement in the community gradually grew from being a learner to becoming a mentor and now having the opportunity to share my experience as a community speaker.

Standing in front of students at Compact Polytechnic Institute and sharing what I have learned throughout this journey was a special milestone for me.

I wanted students to understand that they do not need to know everything before getting involved. They can start with small steps, learn from the community, contribute according to their abilities, and gradually grow.

A Learning Experience Beyond the Sessions

Campus Connect is more than a series of presentations. It is an opportunity to introduce students to the possibilities of open-source collaboration and help them see how they can become part of a global technology community.

Through the different sessions, students were introduced to modern WordPress website development, plugin development, open-source contributions, AI-powered workflows, and professional opportunities.

Each session highlighted a different part of the WordPress ecosystem and showed how students can explore their interests, develop practical skills, and build their future.

I strongly believe that introducing students to open-source communities at an early stage can create valuable opportunities for both individual growth and the wider WordPress community.

Thank You

A special thanks to the organizers, speakers, teachers, and students of Compact Polytechnic Institute for making this Campus Connect event possible.

I am grateful for the opportunity to share my journey, discuss WordPress contributions, and encourage students to explore the global WordPress community.

I also appreciate the enthusiasm and participation of the students throughout the event.

I hope this event inspires more students to start learning WordPress, explore open-source contributions, and become active members of the community.

Looking forward to more opportunities to learn, contribute, mentor, and grow together.

by ATIKUR RAHMAN at November 13, 2026 09:21 AM

November 12, 2026

Open Channels FM: Reclaiming Digital Control: Why User Choice Still Matters

The digital landscape is shifting towards user empowerment, emphasizing open-source solutions that enhance agency. Users are encouraged to reclaim control over technology, creating personalized experiences and fostering independent online communities despite mainstream dominance.

by Open Channels FM at November 12, 2026 07:25 PM

Open Channels FM: How AI and Open Source Shape the Future After Job Loss

Laid-off engineers launch ZeroAuthy and SalesCompel, VINO driver faces patent issues, and security study highlights developer token risks.

by Bob Dunn at November 12, 2026 03:00 PM

Open Channels FM: From Ideas to Micro Apps with Spacefast

A look at how AI agents are impacting web development and what the agentic web means for individuals and companies.

by Bob Dunn at November 12, 2026 11:43 AM

November 11, 2026

Matt: Nathaniel at WordCamp Canada

Nathaniel Christopher has a lovely recap of his time at WordCamp Canada. Very cool that the dashboard widget helped connect him to the local community. Hat tip: Anne.

by Matt at November 11, 2026 08:42 PM

Carlos Bravo: Quantity Is Not Contribution

Flooding open source projects with AI-generated PRs and issues won’t make you a better engineer, and I don’t think it will help your career either.

It mostly adds work for maintainers, who then have to review and triage contributions that often aren’t ready.

by Carlos Bravo at November 11, 2026 04:16 PM

Open Channels FM: AI and Open Source Bug Fixes, Navigating Security Updates and Enterprise Model Spending

From PHP vulnerabilities to AI-driven patching and Chinese open source spending trends brands like Lightwell and Moonshot AI are highlighted.

by Bob Dunn at November 11, 2026 03:00 PM

WordPress.org blog: WordCamp Asia 2027 Is Coming to Penang

Next year, WordCamp Asia 2027 heads to Penang, Malaysia. From April 9 to 11, the WordPress community will gather at the Penang Waterfront Convention Centre for three days of contribution, learning, and connection. Tickets are on sale and sponsorship applications are open, so now is the time to make your plans.

In 2026, WordCamp Asia brought 2,627 attendees to Mumbai, India. More than 1,500 participants joined Contributor Day, where table leads guided work on more than 20 contribution tables. The conference days that followed covered topics ranging from AI and developer workflows to enterprise WordPress and journalism on the open web, and closed with a panel featuring WordPress Executive Director Mary Hubbard, Peter Wilson, and Sergey Biryukov.

WordPress is not a company. It is a shared commitment to keeping the web open.

Mary Hubbard, Executive Director, WordPress

The mix of hands-on work and big-picture conversation is what sets a WordCamp apart. You learn from the people who build, scale, and maintain WordPress every day, trade ideas in the hallway between sessions, and head home with new collaborators and fresh energy for the work ahead.

Penang offers a memorable setting for WC Asia. George Town, a short drive from the venue, is a UNESCO World Heritage Site, and National Geographic named Penang one of the best places in the world to travel to in 2027. The island is famous for its food, from internationally-recognized street food to fine dining, and it is one of Malaysia’s leading destinations for tourism. If you can, give yourself a day or two on either side of the conference to explore.

A regular ticket costs only USD $35, thanks to our sponsors. It covers both conference days, lunch and refreshments, and the after party. Tickets are released in batches, so buying early secures your place and helps organizers plan for everyone who is coming. Contributor Day on April 9 has its own registration, which opens January 27, 2027. It is limited to 600 participants.

April 9 – 11, 2027 | Penang Waterfront Convention Centre (PWCC), Penang, Malaysia

None of this happens without sponsors. Their support keeps ticket prices low, backs the volunteers and contributors who make the event run, and helps WordCamp Asia stay true to the values of the WordPress project. In return, sponsors meet an engaged, international audience of developers, agencies, business owners, and creators.

Five packages are available, from a Small Business table to a Platinum booth, so there is a fit for local companies and global brands alike. Every sponsor also gets access to the Career Corner, a dedicated space for meeting and hiring WordPress professionals.

WordCamp Asia is organized by and for the community. Volunteers, organizers, speakers, sponsors, and attendees each shape what the event becomes, whether they are contributing for the first time or reconnecting with collaborators they have known for years.

However you choose to take part, your presence matters. Buy a ticket, bring a colleague, sponsor the event, or share this post with someone who should be there. Each of those choices strengthens WordPress and the people behind it.

See you in Penang.

by Nicholas Garofalo at November 11, 2026 02:00 PM

WPTavern: #241 – Tiffany Farriss on Drupal Funding, Community, and a Shared Journey With WordPress

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, Drupal funding, community, and a shared journey with WordPress.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Tiffany Farriss. Tiffany has spent the last 30 years working in web design, development, and creation, and she’s been deeply embedded in the Drupal community for the past two decades. She’s currently the interim CEO of the Drupal Association and is the organization’s longest serving board member after Drupal’s founder Dries Buytaert.

This episode is a bit of a departure as we usually focus squarely on WordPress, but Tiffany brings a wealth of experience from the broader PHP family, and this conversation explores the similarities and differences between the WordPress and Drupal ecosystems, particularly when it comes to infrastructure and the sustainability of open source projects.

Tiffany explains the maker-taker problem, and the challenges of sustaining free software platforms that end up in millions of sites across the web. She shares her insights on the real costs behind open source stewardship, drawing from both data and experience, and discusses how tiny groups have shouldered the burden for everyone, and why that might no longer be viable.

The discussion explores the Drupal Certified Partner Program, the push towards quantifying contributions, and how the open source community can improve transparency and sustainability.

Tiffany also touches on the role of public sector procurement in shaping the future of open source, the impact of new regulations, and how community driven recognition could incentivize more organisations to buy their round of beers for the ecosystem.

If you’re interested in the sustainability of open source, the evolution of governance models, and how WordPress professionals can learn from the broader PHP landscape, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Tiffany Farriss.

I am joined on the podcast by Tiffany Farriss. Hello, Tiffany.

[00:03:19] Tiffany Farriss: Hi Nathan.

[00:03:20] Nathan Wrigley: Thank you for joining us. So this is a little bit of a departure. Usually we talk about WordPress. It’s WordPress on the menu every single day of the week. And that is going to be the case, I suspect a little bit today. But there’s also going to be a foray into Drupal because Tiffany is very much connected with the Drupal community.

So Tiffany, really just to get this podcast started, can I just offer you a chance to give us your little bio, tell us who you are and what you do over on the Drupal side, lo these many years. It’s been multiple decades that you’ve been involved in various different ways I think.

[00:03:52] Tiffany Farriss: It has been. Yeah. Thank you Nathan. I’m really glad to be here. I do consider all of us part of the PHP family, whether we’re Drupal or WordPress or Joomla or TYPO3, like I think we all have so much in common.

But I am Tiffany Farriss. I’m currently the interim CEO over at the Drupal Association. I have been involved in web design, development, creation for the last 30 years. And I’ve been heavily involved in the Drupal community for the last 20.

In particular in its governance. I’m the longest tenured board member of the Drupal Association, the 501 (c) (3) that is responsible for the governance. Other than Dries Buytaert, who is the founder of the Drupal Project.

So I’ve been around a long time and I’m currently on leave from my own company, palantir.net to take a year to help Drupal kind of navigate this time of kind of intense disruption, I think it is for all of us. Pretty safe to say, that we are all experiencing the same disruptions from AI. And then just economic pressure in general.

[00:04:50] Nathan Wrigley: So Drupal, I suppose, it would be a good thing to say at this point, Drupal is very similar in its project, in its status, in its goals, in its aims, in its infrastructure and technology to the CMS that most people listening to this are familiar with. It’s a PHP based CMS used by millions of websites all over the world. So broadly it’s the same.

Now you mentioned the foundation. Would you just be able to dig into that a little bit more because that may be confusing for people on this side. There may be some significant differences there. What does the foundation get itself involved with? I know that you described that a little bit there, but if you could go into a bit more depth, that would be great.

[00:05:26] Tiffany Farriss: I do think our governance is one of the places where WordPress and Drupal are a little bit different. In Drupal, we have the Drupal Association, which is an independent 501 (c) (3), which is a US-based not-for-profit. And we have specifically an educational and scientific mission that we’re authorised to do.

We run Drupal.org. We run all of the infrastructure. We support all the security coordination. And we are responsible for Drupal Cons around the world. We do have a founder as well, right, Dries, and he is currently the Executive Chairman of Acquia. But Acquia doesn’t have the same single privileged actor role, that say Automattic does in the WordPress community.

Dries serves on the board, but he doesn’t control the board and he doesn’t control any of the technical steering committees, although he is still the founder and the lead of the project.

[00:06:17] Nathan Wrigley: Okay. So there is a significant difference there, isn’t there? That’s kind of interesting.

[00:06:20] Tiffany Farriss: Yeah.

[00:06:20] Nathan Wrigley: Okay, we’ll dig into that in a moment. However, in the preparation for this podcast episode, Tiffany was very kind to send me three things.

One of them was a YouTube video. It runs to about 20 minutes and sort of summarises what we’re going to talk about, I think, fairly well.

Another one was a blog post that you wrote in June of this year. It’s called Freedom is Not Free, A model for Open Source Sustainability. Again, very much aligned to what we’re going to talk about. That’s on palantir.net, which I’m at pains to point out is not the palantir that you are probably thinking about when you say the word palantir. And there’s another one which again, tackles the same subject, written broadly the same time. It was July this year, written by Dries, the founder of Drupal.

And what we’re trying to deal with here is, what I think Dries has summed up in the past is this maker, taker problem. And it’s very difficult to summarise. I must confess, I genuinely cannot articulate this problem. No matter how many times I’ve tried to articulate it to friends, to colleagues, to relations. At some point I get lost. At some point, the dynamics of it and the argument of it kind of boils boils down to it’s a moral thing.

So I’m just wondering, could you paint the picture of what you were trying to say in that YouTube video and in your blog post. What is the open source sustainability problem that you think, amongst many others, we have at the moment?

[00:07:47] Tiffany Farriss: We like to talk in open source about free and the four freedoms, especially for projects that are based in the GPL, right? But one of those freedoms, I think it comes down to the idea of the word free, right? There’s free is in speech. Where I am free to say what I want and when I want, and accept the consequences of that.

But then there’s also this idea of free as in beer. And the reality is that the beer was never free. And the problem we have in open source is that for the last 25 years of Drupal, a really small group has been buying the rounds of beer for an entire ecosystem. And what I’m saying is that, beer has never been free. You just haven’t been taking your turn at buying the round, right?

So as we deal with kind of the pressures of the current economic situation, the uncertainty and opportunities created by AI, the number of people who are still buying those rounds is dwindling. But there’s still a lot of people who want to drink that free beer. There’s still a tonne of people who use WordPress, a tonne of people who use Drupal and get a lot of value out of it, right? They’re enjoying that.

But what the problem is, is that we have this open source licence, and the licence is what conveys the freedom, right? It makes the code available. And in open source the more people who use the code, the cost of that code goes to zero. And no one’s use of the code is diminished by someone else also using that code.

However, there’s more to being an open source project than just the code. And this is where the concept of stewardship comes in. Stewardship is what makes it dependable. It’s what has made it so that millions of people around the world can feel confident in downloading the software, using the software, hiring someone to create a WordPress or a Drupal implementation for you.

And that stewardship includes things like code hosting, or packaging. Testing frameworks. The security coordination. All of those things, which as more people use it become more expensive, not less.

So, there are these tensions around people who are getting value from open source software, but who currently don’t help pay for the cost that they impose on the project, largely because it’s invisible, right? So I think the first step is that we need to make those costs much more visible. So that’s something I’ve been working on in Drupal for a while. And so I want to expose it, right?

We have 2,800 organisations in the last year who contributed into Drupal, but under 5% of them did two thirds of it, right? There are, I think as in WordPress, you know who really is driving and doing the work. And we do too, right? Obviously in Drupal we know who that is. And because we know who they are, and we know that they’re invested, and that they are passionate about open source and our project. They’re the ones who are easy to ask for financial contributions, or sponsorship to Drupal Con.

So you keep going back to the same pool. And in Drupal’s case, that means that 94% of our financial contribution comes from this tiny group of 5%. So they’re buying the rounds of beer for everyone. And that’s not a sustainable proposition.

[00:11:00] Nathan Wrigley: Do you think, I’m going to rewind the clock a little bit. So, I regard the internet as an ongoing experiment. Where we are now is definitely not where it’s going to end up. And where we were 10 years ago, I don’t know that anybody would’ve predicted that we’d end up where we are today. You know, the internet came around and it evolved in the way that it did.

Do you see in the last, let’s say 25 years that many people have had access to the internet. Can you see moments where, and I’m doing air quotes, mistakes were made, which led to this problem? Or was it just happenstance and serendipity? We just got to this point? There’s no real pointing of a finger. There’s nobody to blame. There’s nobody to say, okay, you made dreadful mistakes. It’s just the way it evolved. There’s no question there, but do you understand what I’m saying?

[00:11:49] Tiffany Farriss: I do.

[00:11:50] Nathan Wrigley: With the benefit of hindsight, can you look back and point the finger, or is it more a case of okay, let’s just deal with the reality of where we’re at now.

[00:11:56] Tiffany Farriss: I can point to that moment. I was on the board at the time when Drupal moved over to Composer, right, and to modern packaging. And what I can tell you is that the board was never, wasn’t a big deal, right? They came to the board and I don’t even think we were really notified that this was happening or what it would mean.

And nobody modelled that packaging costs scaled to infinity, the more people who use it, right? There was no financial model put around it. We became a utility as opposed to just a repository. And I think that’s the moment for us that really changed things. You can continue to run events, Drupal Cons and Drupal Camps and all of that stuff. Those have pretty known economic models, and you can continue to run a website that promotes things. And you probably could even continue to be a collaboration platform.

But once you start to become a packaging utility, then you become part of everyone’s infrastructure. And if you start to provide that for free, and people will expect it to continue to be free. And so I’m, really it’s only in the last couple of years that I’ve started to look into those costs. And for Drupal, we provide the Drupal Association itself provides $10 in services to every site, every year, every modern Drupal site every year.

[00:13:16] Nathan Wrigley: Oh, that’s an interesting stat.

[00:13:17] Tiffany Farriss: It is.

[00:13:18] Nathan Wrigley: You’ve figured that out, you’ve done the maths and it costs $10 for every Drupal site that exists, whether or not they pay anything? That’s such an interesting number.

[00:13:26] Tiffany Farriss: Isn’t But I actually only take in $7.50. So I’ve been pushing forward in technical debt things for years. And that’s a risk, right? That’s a risk for me. And it’s also just unpleasant. I think that if we all start to become a little clearer around what the costs are as a utility, it’s actually not a lot.

When it goes unpaid, it does have a cost, a compounding cost. And in Drupal’s history, what we used to say was if you want to support the project, support the conference. We all learned, obviously, during the pandemic that having an economic model based around a conference wasn’t the best choice.

I still think our ability to get together in person as a community is incredibly valuable, but I don’t see it as the way that we make the money to support the infrastructure. I really don’t like this idea that our revenues, and our expenses are so decoupled like that. And I think that’s really charity thinking.

And part of what I’m working to do is to evolve it into utility thinking? For a couple of reasons, right? One, it’s, not a charity. We are providing a service that people build businesses on, and they expect it to be there. But then also, especially in the case of Drupal, we have such a huge footprint in public sector work, and very large enterprise level government sites. And institutional sites, things that people need to have enterprise level expectations of. And they do, they hit our infrastructure every 15 minutes, right?

Procurement has no way to pay either a community or a charity. However, they can pay for their costs if you can explain it to them in a cost recovery model that this is your share. And I want to be clear, as I talk about what the Drupal Association provides, that leaves aside the volunteer labor for what I like to consider the operational roles that also exist as a part of stewarded open source. Which are the release management, the security team, all of that work that we’re all so very hyper aware of after last week, that also has a cost.

So beyond the $10 that the Drupal Association is providing, there’s $30 provided just by the community as a keep the lights on sort of level. If we had to boil it down to its essence. Beyond what it takes to scratch your own itch, right?

We all know that open source succeeds because I needed to write a module for this, I want to extend that. There are operational roles that aren’t actually in someone’s self-interest to perform, or to underwrite, if you’re an organisation. And so quantifying it has been something I’ve been working on for the last couple of months. And so we’re working now with this $40 a year figure around the services that are provided in addition to the code, that we don’t have to, right? The licence says it’s used as is, but nobody actually does that.

[00:16:08] Nathan Wrigley: No. Okay. That’s an interesting thought. I’m just going to pivot ever so slightly and just talk about the community that you’ve got. I imagine it maps broadly to the community that we’ve got. Do you find having these conversations is challenging? Let’s go with that word. Because over on the WordPress side, is a reluctance for many people in the community to bring money into the conversation at all. You know, it is just almost a taboo in many senses.

And obviously you are pioneering this, the word dollar comes out a lot. You know, you’re actually putting specific numbers out there quite a lot. What’s the pushback like over there? Are there two camps? It’s like the “we’re never going to do this, is crazy,” and the acceptance? Or is there some sort of homogenous bit in the middle where people are starting to realise, okay, Tiffany’s making sense, this adds up. This is what we need to do in 2027, 2028.

Basically, how’s it going? How much pushback are you getting from your community?

[00:17:02] Tiffany Farriss: I think Drupal is a little bit different than WordPress because we don’t have a paid plugin economy. All modules are GPL’d and they’re free. So anyone who is working on Drupal has no direct way to monetize it. And I think that has made this conversation, this recognition a little bit clearer, right?

Our entire economic base of support has been from a lot of the agencies. That’s the segment of our entire ecosystem that’s under the most pressure right now, and so if I say to them, I think we need to stop asking so much of you and we need to start asking more of the others in the ecosystem. It’s been a little bit of a recognition, like yeah, maybe that’s true.

Our ecosystem, our agency ecosystem, they give well beyond what they take from Drupal. And so I think for me, quantifying what just the general site takes from Drupal, has made it really sharp and clear that this isn’t a huge ask. And maybe the labor costs, maybe the infrastructure costs. It is time for us to be able to mature, and to recognise that more people need to be involved in supporting that.

[00:18:09] Nathan Wrigley: I know that you are not involved in the WordPress space in the same way that you are with Drupal, but I’m just wondering if, from what you’ve just said, it sounds a little bit like you have more of a bat-phone into the people who need to be on side. In the WordPress space, I feel like there may be more people who, I don’t know, they own a plugin business, and they make money in that way, but they might contribute nothing back to the community.

There’s people who turn up to events, there’s people who own hosting companies. They’re all spread out in different ways, and earning money in different ways. And so when messaging about, I guess our equivalent would be called Five For The Future, it’s very hard to know where to put that messaging, because you can’t really sum up where these people all are. They’re all over the place and there’s no one place where they gather.

But it sounds a little bit like, and I said bat phone, I hope you knew what I meant by that. It sounds like you have a line of communication which is much more easy to tap perhaps than we do on the WordPress side. If I’ve misunderstood that, please say.

[00:19:10] Tiffany Farriss: I think I do feel like we have a lot of engagement from a lot of the organisations. One of the major changes that Dries put in place back in 2014, was our contribution system. And so we know, it’s public, who is contributing to Drupal, and that’s not unique to us.

But I think the innovation is that every commit has the opportunity for an organisation as well as a sponsor. So when work is done in Drupal, we do have a lot of telemetry around who’s doing that work. So I think that’s given us insight into where some pieces of the value have been experienced over the last 25 years.

And so we’re able to recognise that. But I do think we over index on those agencies who are involved. And so have a lot of, currently we have a Drupal Certified Partner Program, where a lot of those agencies participate. And they know that they’re supporting and underwriting the infrastructure and they take a lot of pride in that.

I think the difficulty is that one, we’re not a 501 (c) (6), we’re not a trade association. So I can’t deliver benefits specifically back to that group. You know, I can’t go out and say to procurement agents, “hey, you really should drive business to these folks. These are the ones who are actually supporting and working on Drupal,” because it feels like a pay to play. And in our case, there is some payment there, but it’s really you can’t become a Drupal Certified Partner without having made the maker contributions, you know?

[00:20:32] Nathan Wrigley: Oh, so there is a sort of quid pro quo there. If you contribute, I don’t know what the specifics are there, but if you manage to get over whatever the hurdle is, you can then access something. What is the something there that you can access? Sorry, I interrupted.

[00:20:48] Tiffany Farriss: Nothing. There’s nothing you can access, right? I mean, we recognise our makers on our website as Drupal Certified Partners.

But I do think that because it’s just a wall of logos, and it isn’t actually an attestation, it’s a lot of marketing copy, right? It becomes hard for procurement to put any credibility in it. And so this is actually the big innovation that I’m working on involving the Drupal Certified Partner Program, which is largely built around those agencies into a Drupal Certification Program that encompasses our entire ecosystem and essentially sets the standard.

[00:21:21] Nathan Wrigley: Tell us a little bit more about the things that you are doing there then. Because that sounds really intriguing.

[00:21:25] Tiffany Farriss: Yeah, I think that what I recognised is that as a 501 (c) (3), one of the things I can do is I can recognise those who are being good citizens. Now we have to come up with what that standard is. And I think in open source, it’s something that you know, but maybe hasn’t been articulated.

And part of that process has been to recognise that there are three pillars of contribution that are all essential for Drupal to be successful.

First is making, those who are actually contributing code, or code adjacent activities to Drupal.

Patronage, right? Those who are actually funding the infrastructure. Funding the core release managers, the core maintainers, the security maintainers.

And then there’s also advocacy. Helping the world to understand what Drupal is and what it does, and to create the documentation, and to go out to events, and to help others learn to use it.

So those are the three pillars of success. And so what we’re doing is we’re taking that idea of the contribution credit that we’ve had for a long time, which has always recognised more than just code contributions, and explicitly breaking it into these three areas.

And then our Drupal Certified Partner Program has been about agencies. So the eligibility requirements for who we recognise were based around what agencies already were doing. And what we’re evolving that into is different kinds of certification for all the parts of our ecosystem.

So we have platforms that are specifically Drupal tuned. Our platforms as a service partners. We have shared hosts. There are cloud hosts. There are infrastructure CDNs. There are end users. There are individuals. And so that entire spectrum of who’s participating, and getting value and benefit from Drupal, I want to create the opportunity for them to become Drupal certified.

And what that means is that Drupal certification is a badge of recognition of those who are engaging with Drupal in a net neutral, or net positive way. That they’re giving back at least what they are taking from the community, or more.

I think we start to move from something that is more like a sponsored badge wall, into a public trust register, which I think is, very helpful. And I, currently on Drupal.org, you can look up any individual, or any organisation, and you can see how they contribute. But unless you’re super in the weeds, it doesn’t mean much to you.

So I think that the lever here is around procurement, and around making this a trust ledger, something that can’t be bought. But something that is understandable to a procurement officer to say, who is contributing to Drupal? What are they contributing to Drupal, so that they can make decisions. Especially if they have two different potential vendors. One who contributes and one who doesn’t.

I think this is all a conversation we can now have because of the way that Europe is leading the way with their open source strategy. You know, that they want there to be more open source used in the services that they provide. From a digital sovereignty perspective, it’s essential for them.

[00:24:18] Nathan Wrigley: Let me see if I’ve understood that correctly. So on one level, I’m just going to use the word Brussels. I hope that everybody understands what I mean when I say Brussels.

[00:24:25] Tiffany Farriss: Yeah.

[00:24:26] Nathan Wrigley: So, Brussels encapsulates the EU, the governance of the EU. Because of the posture that Brussels takes. It could, coerce is the wrong word, but let’s go with that. It could apply a certain degree of pressure to big procurement initiatives to say, look, I don’t know, we need a new website for the French Health Service or whatever. And Drupal is right in there, and we’re looking for organisations that can help us to build that Drupal infrastructure.

Given that’s the case, we are now going to go to this extra layer of what do these agencies that are competing for this contract, what is their position vis-a-vis Drupal? And if it looks good, in that you’ve contributed in the past and you have all the accreditation and what have you, you will more likely have a favourable outcome in that procurement procedure. Did I sum that up right or have I completely misunderstood?

[00:25:22] Tiffany Farriss: No, I think that’s a part of it, right? I think that Brussels has already recognised that it’s in their interests to use open source products, right, open source solutions, and has for a while. But I think procurement’s the real lever where we start to enshrine or encourage bad behaviour, right? What we were calling extractive use of open source.

So if you think of open source as just lumber that you can take and use however you want, right? If nobody is replanting the trees, cutting it down, sawing the boards, then it doesn’t exist anymore, right?

And also on the government side, when we talk about public money, public code. It’s important that you actually get the benefits of it. So it wasn’t just a starter kit that you take and then you own, right? We know that good use of open source, whether it is WordPress or Drupal or TYPO3, right? You want to minimise the amount of code that you own. That’s the advantage. That’s how we all experience the network effects.

So you need to have some behaviours, and I think that procurement officers don’t care, don’t need to know, about what open source is or our specific projects. But what they need to know is that when they are procuring any project, or any solution, that has open source as a component of it. That open source isn’t going to end up being code that they own down the road. They have the right to use it, extend it forever, and they know that somebody can’t turn it off on them, which is I think a very important.

[00:26:48] Nathan Wrigley: Oh, big thing at the minute.

[00:26:49] Tiffany Farriss: Big thing right now, especially in light of the 2018 USA Cloud Act, right? So that’s really been the driving impetus around digital sovereignty. But when we think about good open source use, responsible open source use, there are some behaviours that regardless of project we know are true.

And it is that when you write a new plugin or module, you release it, right? So others can use it so that you’re sharing the maintenance burden moving forward. If you don’t, then you own that and you’re going to maintain those lines of code yourself.

Two, if you patch something, you want to release that patch upstream because otherwise you may have ended up inadvertently forking it. Or in some cases the government pays for the same patch over and over and over again, right? If there are economic benefit to using open source, you need to know that whatever vendor you’re using is contributing the patches back upstream so that you continue to stay, anything that’s non-confidential, obviously, but so that you can stay current and up to date, right? Woe for those who were not current and up to date last week with PHP, right? It made that problem all the more difficult.

So when I think about making it open source use at the government level very sustainable, there’s really three policies I think that they need to implement to help really get the benefits of open source, right?

One is that the patches are contributed upstream if they’re non-confidential within 30 days.

Two, I think that they need to understand that there is a cost to their use. And so creating whether it’s 2% or 5%, creating a line item in every project that uses open source of any flavour, for the delivery of the project, that there is a standard percentage that is contributed back upstream to that open source project, to offset that use. Because right now, the agencies and the companies that are responsible open source users, they bear their contributions and their participation in open source as a tax. So it becomes baked into their hourly rates. Which then as economic conditions get constrained, it becomes a disadvantage to do the right thing for open source.

So I’m very worried about that. But if it is instead a flat line item that all who are responding to a tender have to meet, then the virtuous behaviour that continues the virtuous cycle of open source isn’t a burden on any one firm.

And then the third piece is you want to know, are they a contributor to that open source project? And so this speaks right to Dries’ maker taker dilemma, which I’ve extended to the maker taker faker dilemma. Which is obviously, I think makers and takers are pretty clear, right? You either are someone who’s making and contributing into your open source project. And takers being the ones who are like, thanks for the wood little elves who magically made it in the woods. Great. This is all good. Good luck with that forest.

I think that the fakers are, in some ways, much more dangerous, because they have this, it’s like open source washing. The fakers are the ones who maybe sponsored a coffee one time at an event, but they’re not really giving things back. So they’ve got a badge. Procurement, they can say, oh look, I’m a sponsor.

I appreciate anyone who sponsors at any level. But I think that when you’re talking about competing on a public procurement, there is a very important difference between someone who maintains modules, contributes to the security team, and someone who sponsors a coffee. And I think that it’s on us as open source projects to make that clearer.

So the Drupal certification is our attempt to really become a very trusted public ledger about who’s contributing what, and why it matters to folks who aren’t in our community. I think today, where we stand and where we’re starting, it is a very transparent ledger. But there’s a difference between transparency and clarity. And I think if we want Brussels, and other governments and procurement, officers to be able to differentiate and give a preference to those who are good open source citizens, if you will, those who are actually involved in the projects that they’re using and implementing, for these very important public projects, I think it’s on us to make that easier. So that’s something I’ll be focused on next year.

[00:31:02] Nathan Wrigley: It sounds to me like you could kind of sum this up in the word clarity. Everybody needs clarity. Those people who are procuring things need to be clear on what they’re going to get. Those people who are delivering things need to be clear on what they’re going to do. And the notoriety, for want of a better word that they’re going to get from that.

It also seems like you are in a very interesting role, where you are like this go-between between all the people doing the work on Drupal, and the people who are procuring, and I’m sure that’s really fascinating work. Like what is the proclivity of, let’s say for example, USA or Canada. What are the requirements that they have around, I don’t know, 20% of all public software needs to be open source or something like that. That must be utterly fascinating work. You’re right at the chalk face of all this. Wow, that’s so interesting.

[00:31:52] Tiffany Farriss: It’s absolute candy to my brain. Like I just, I can’t tell you how much I really am enjoying being part of those conversations. And I never would’ve thought that I would’ve been invited to speak at a plenary at the United Nations, and yet I was. And that blog post that you mentioned, that’s on palantir.net, actually those are remarks I gave to the German Consulate, in New York, right?

It all comes from this conversation we’re all just starting to have about what does it mean to sustainably and responsibly use open source as we look ahead to the next 25 years, next a hundred years.

There was a board member I had served with in Drupal a long time ago, Donna Benjamin, and this was, I don’t know, maybe almost 20 years ago now. And she always used to say, what’s our a hundred year plan? And at the time, I was taken back. I’m like, uh, I can’t even with that.

And now as we fast forward to where we are today, I actually can start to see that. And it’s about understanding that nobody intends and sets out to be a taker, right? You can’t pay for things that you don’t know are there, or things you don’t know are already happening. And you can’t meet expectations that aren’t communicated.

So this is the opportunity for open source projects to say, this is what it takes for us today. This is what it takes for us where we want to go. And here’s your share of it. How do we make it easy, and expected that everyone does a little, so we’re not resting on a few who have to do a lot?

[00:33:22] Nathan Wrigley: This is going to sound like a really poor summation of it, but it feels like open source, up until this point, you know, the analogy, carrot and stick, you know.

[00:33:30] Tiffany Farriss: Yes.

[00:33:30] Nathan Wrigley: So the carrot is, we hope that you’ll come along and, you know, follow the lead and do all of the right things. Where a stick is more, if you don’t do the right thing, there’ll be a punishment for that. It feels like open source for the last 20, 25 years, there’s been more carrot than stick. And although it’s incorrect to summarise this as stick, is there a little bit of stick here? Are we trying to cast a, let’s say, a glowing light on those that do everything well, who are the makers? You know, we want to raise your profile, shout from the rooftops that you did things well.

Conversely, is there a bit of okay, those that don’t, we are going to shame. Or is it more a case of we just leave you alone? You just don’t get a mention. You don’t get to be part of the community in quite the same way.

[00:34:15] Tiffany Farriss: Coming back to that frame as open source stewardship as a utility. Nobody considers it a donation to their electric company. They pay the bill because the lights matter. And I think it’s about resetting this frame. We’ve never sent utility bills to people. We’ve never even exposed what that looks like, or maybe we don’t know ourselves. Based on projects, Drupal certainly didn’t until I started this work.

So I think that there’s this expectation that we’re going to continue as we always have on this balance of goodwill and volunteerism. But as last week showed, PHP Foundation, which WordPress is very involved in, Drupal as well, has one full-time employee. And 70% of the web runs on it. So it’s something that we have taken for granted for too long. And I think that this moment is brokered by the blessing and the curse that is AI.

[00:35:07] Nathan Wrigley: I wonder if the wider issue at stake really is notifying the general public. Letting all of humanity know that when you are picking up your phone and using that app, and it’s connecting with that service over here to enable you to, I don’t know, book a restaurant or get a taxi. There’s probably some layer of free software around there.

And would you do anything for free? Is that, I’m not asking you that question by the way. I’m just saying, you know, dear app user, would you do things for free in the same way that you’re expecting this software to be free?

And I think that argument’s fairly persuasive, but it’s not something that has leaked out into the public. You know, the coverage of the PHP thing, nobody knew. The guy that came on the BBC, who was the BBC correspondent, he’d never heard of PHP. And he’s the cybersecurity correspondent for the BBC had never heard of PHP.

And so getting it out into the vernacular, getting it out into the mainstream, that all of this stuff that you’ve taken for granted, we all need to pay a little bit. I wonder if that’s an interesting. It’s like the stick that I was talking about earlier. If the public are more aware whether they will be able to pressure things a little bit more. I don’t know. I’m not sure there’s any mileage in that, in all honesty, but it’d be an interesting experiment to run.

[00:36:20] Tiffany Farriss: I think we’re about to see that experiment, right? So the Cyber Resilience Act in Europe is requiring SBOMs, which are Service Bill Of Materials to be disclosed. And I think that once SBOMs are readily available, it may become clearer, at least to decision makers, exactly how much open source software is in the solutions that you’re providing. And I really am curious to see how it evolves when you do have these manufacturers or organisations, whether they’re service organisations or actual manufacturers, starting to become liable for the risks in your security chain.

[00:36:56] Nathan Wrigley: Right.

[00:36:56] Tiffany Farriss: As I look at this, I look at it as a supply chain issue. And so we’ve now exposed that there are weaknesses in our supply chain. So the argument isn’t, it’s really less of a shaming. It’s saying hey, this is a risk management approach. And I was looking at it as a design flaw. That open source was an idea around writing software. It wasn’t actually envisioned at any time that this was going to run the world. It was just, this is a good idea to do good way to do things. Let’s try it.

But now that we understand that open source does run everything, we need to come back and treat this as a design problem and say, how do we align the incentives? What needs to be true?

I appreciate the work that’s going on in Europe right now, and I think that becomes a bit of the stick. It’s not coming from us. It’s saying, actually if you sell a product that’s based on open source, and that open source has a security issue, you are liable. You’re the manufacturer. See, as an open source steward, the Drupal Association does not have liability. We have responsibilities to disclose, which we have done, all the way back through 2007.

Drupal is a CNA, right? We’re a numbering authority for CVEs. We’ve had a very mature security practise for many years, and we will continue to do so, and meet our CRA disclosure requirements. But those who have blindly been using open source in products or in services for others, they’re now manufacturers. And come December of next year, they’re really going to start to understand how liable they’ve become for any issues in the supply chain.

[00:38:34] Nathan Wrigley: There’s something quite virtuous about that. In that it’s allowing the open source posture to carry on in the same way that it always has. Shifting the responsibility over to the governments in a way. You know, that they’ll create the legislation, which means that if you fall foul of this, that and the other thing, you will now be responsible. And if you are responsible, it’s it’s the same reason we have car insurance and buildings insurance. You need to know what your position is going to be in the event of a fire or a crash. You just have to know it. Because if your business were to go under because you weren’t thinking about those things, that would just be negligence. And so that’s such an interesting way of framing it. I like that a lot.

I also like your definition there. You described the internet over, you know, the last 20 years and how nobody knew that it was going to work this way, and now here we are. And, I guess it would be a bit like, I don’t know, going to a lemonade stand or something like that and getting a really cheap lemonade from a child who’d done it because it was a nice thing to do for the community. Let’s sell cheap lemonade.

But then turning up with 12,000 people and saying, we would like 12,000 cheap lemonades, please. Immediately. No, that’s not available. That’s not the way it was designed. And that feels to have certain overlaps here.

Nobody knew that open source was going to take over the world. Now it has. It’s chronically underfunded. There will be a collapse at some point if companies and businesses are allowed to just have a taker mentality. So you are putting things in place to make sure that is checked. And I think that’s really interesting.

[00:40:06] Tiffany Farriss: It goes from this idea that we passively consume whatever we get. Whether it’s a website or a phone. To this idea of having some sort of active upstream strategy. And again, I don’t think that many of us had the opportunity to understand what software was running on our phone. You didn’t know, right? You can’t mitigate a risk that you don’t know is there. I do think it is unreasonable to think that we don’t know the risk is there now, especially after last week.

[00:40:33] Nathan Wrigley: There’s just no bit of me which would walk into a store and pick things up and just wander out and say. There it is. I’m going to have it because it’s there for me to take. And yet, broadly speaking, I think it’s fair to say that the vast majority of the people in the world consuming things on the internet have exactly that position.

You switch on the device, the device itself is probably working on, in many cases, open source software. And then I’m just going to consume all the things that are there, you know, it’s all free. You know, it might not be free, it might be sponsored by advertising or what have you know, we all have opinions on that.

But we have got ourselves into this position where we completely pick up the devices and think, all free, from top to bottom, free. And we need to change that mentality. So, going back to what I said earlier, getting the message out to the population at large, I don’t know how you do that.

[00:41:25] Tiffany Farriss: I’m a big believer in what Buckminster Fuller called the trim tabs, right? I don’t set out to turn the ship. I turn the little piece, the trim tab that turns the rudder, and that turns the ship. And I think that whether we’re talking about compliance, or we’re talking about OSBOs, and helping compliance within organisations, I think that’s how we turn the ship, right?

We need to create an economic model that really does protect the supply chain. This is a consumer problem. It is a consumer risk. And I think that’s exactly what many governments were set up to deal with.

And so I think they do have the opportunity that the governments, whether it’s the EU or the US or the Canadian government, they spend so much money. And if they change the way that they spend money, and they change the way that they look at open source and how they understand it. And to be a responsible open source consumer, who’s asking for, are we giving back? Are we minimising our footprint? Are we restoring services that we use? Are we treating it like the utility that it is? That alone makes such a huge difference, such a huge difference.

And helps us to move away from this idea of licence only open source economics. Which is essentially that idea that I’m just going to take it because the cost of code go to zero over time, right? That’s not it alone, right?

We expect that when someone finds an issue, especially an issue that can cause remote execution, right? That they’re going to tell us about it. That they’re going to fix it. And that we’re going to be able to have access to that fix. And that’s where we move beyond this idea that the licence itself is free, and it will be free forever.

Those services that is about the human capital, and the human technology that make those things possible. And they are not free, they have never been free. You just haven’t known who was picking up the bill on your behalf.

[00:43:17] Nathan Wrigley: What kind of timeframe? This is going to be my last question by the way. What kind of timeframe do you put on this. How far into the future are you gazing? I’m guessing the answer is it’ll never be complete, this work. But how far into the future are you hoping to get so that you can look in the rear view mirror and say, yeah, we’ve achieved most of what we wanted to do there.

[00:43:37] Tiffany Farriss: Because we’re kind of on forefront here in having these conversations, and we’re certainly not alone. Every one of the open source foundations is having some version of this conversation, or some approach that they’re trying, to make sure that they have the base of support that is commensurate to the folks that they serve, right?

I really am approaching this as a pilot for the next six months, and seeing can we, as we broaden and understand different segments of our ecosystem, and the ways in which they can contribute that align with their interests, right? I’m always looking for the triple win. The win for Drupal. The win for the end agency. And the win for the public, right? Because I am a public facing charity, right? I want all of those things to be true.

And I’ll be experimenting and having conversations with infrastructure providers, with our shared hosting platforms, with cloud providers to say, okay, what does it make sense for you to contribute? What does it mean for you to be a good Drupal citizen, and to give back in a way that feels appropriate to the amount of value that you’re generating from this?

I don’t think that any system can be designed where it requires a hundred percent good behaviour, or a hundred percent participation. It’s going to be a process of iteration and learning as fast as I can. Making sure that we’re being transparent about it, and approaching it from this cost expensing perspective. I’m not looking to maximise profit or other things. I’m a not-for-profit, and I care about resources, and money, and attention going to Drupal. If it comes to the DA, through the DA or directly into the Drupal community, all of those states are a win.

So it creates a great table for conversations with different kinds of players and providers who haven’t engaged. But at least now I can go to them and say, hey, this is what you’re already consuming from our ecosystem. And here’s a pretty good back a napkin for what I think you’re making from it. If we didn’t exist, what would you do? How would you do the security pieces? How would you do the packaging pieces?

And it’s okay if one of the answers in those conversations is, oh, wow, I didn’t realise we were using so much. We can dial that back. That’s perfectly valid. I want to make sure that open source and that Drupal is there for whoever wants it in as secure and as innovative a way as possible.

And so whether you reduce how often you ping my packaging server or you are like, yes, I need this, this is part of my critical infrastructure, and you fund it as if it is a utility part of your infrastructure. Both of those are valid answers to me.

[00:46:03] Nathan Wrigley: There’s so many people in the WordPress space who will resonate with everything that you are doing here. I said I was going to ask no more questions. I have one more. Do you have lines of communication open with, for example, WordPress and maybe PHP? Are you doing this very much in isolation, even though there may be overlaps? Do you have that? Would you welcome that? Would you like to have introductions to people? And if so how can people communicate that to you?

[00:46:29] Tiffany Farriss: I’m always happy to talk to everyone. I will say Drupal and Joomla, WordPress and TYPO3, we have the Open Web Alliance, and so we do talk every month. And we’ve just invited PHP to be a part of that obviously. I have Slack access to all of those folks and we do talk regularly.

In addition, there’s just a broader open source community of leaders. There was the Open Source Congress, that happened in September. I really appreciate being able to talk to my colleagues whether it’s RubyCon for the Apache Foundation, which actually put on this year’s Open Source Congress and did a fantastic job. All of us being able to talk together.

I can say to the CEO of Python, I can say, oh you know, hey what lawyer are you using right now? Or what software did you use for your community elections? I’m looking for some new ones, right? And they have tonnes of ideas and then I’m able to say, oh, here’s how we are doing this, or here’s how we’re doing that. And I just think that level of collaboration and conversation, has been incredible. Right. Rust Foundation, UN Open Source Week and the EU Open Source Week, and Open Source Congress. Those conversations among colleagues have been fantastic.

Any new colleagues I’m happy to talk to as well. You can reach me on many different Slacks, whether it’s the Open Source Congress Slack, or the Alpha Omega Project for Drupal. I’m in Drupal Slack. You can reach me in all of those places, is @Farriss. That’s FARRISS.

[00:47:51] Nathan Wrigley: Nice. Thank you so much. It really is fascinating work. I would really be genuinely curious to watch what you are doing over the the next six months. Where you end up. How the project is received at both ends.

[00:48:04] Tiffany Farriss: Me too.

[00:48:04] Nathan Wrigley: To see what the pushback is like. I would really love to keep a track of what’s going on. But for now, best of luck. I hope that it all pans out in the way you’re anticipating. So, Tiffany Farriss, thank you so much for making the time to chat to me today.

[00:48:16] Tiffany Farriss: Nathan, thank you for having me.

On the podcast today we have Tiffany Farriss.

Tiffany has spent the last 30 years working in web design, development, and creation, and she’s been deeply embedded in the Drupal community for the past two decades. She’s currently the interim CEO of the Drupal Association, and is the organisation’s longest-serving board member after Drupal’s founder, Dries Buytaert.

This episode is a bit of a departure, as we usually focus squarely on WordPress. But Tiffany brings a wealth of experience from the broader PHP family, and this conversation explores the similarities and differences between the WordPress and Drupal ecosystems, particularly when it comes to infrastructure, and the sustainability of open source projects.

Tiffany explains the ‘maker-taker’ problem and the challenges of sustaining free software platforms that underpin millions of sites across the web. She shares her insights on the real costs behind open source stewardship, drawing from both data and experience, and discusses how tiny groups have shouldered the burden for everyone, and why that might no longer be viable.

The discussion explores the Drupal Certified Partner program, the push towards quantifying contributions, and how the open source community can improve transparency and sustainability. Tiffany also touches on the role of public sector procurement in shaping the future of open source, the impact of new regulations, and how community-driven recognition could incentivise more organisations to ‘buy their round of beers’ for the ecosystem.

If you’re interested in the sustainability of open source, the evolution of governance models, and how WordPress professionals can learn from the broader PHP landscape, this episode is for you.

Useful links

Tiffany on Drupal.org

Drupal Association

 Dries Buytaert

Palantir.net

Drupal.org

DrupalCon

Drupal Events

Acquia

Five for the Future

Drupal Certified Partner Program

2018 USA Cloud Act

 Cyber Resilience Act

Joomla

TYPO3

Open Web Alliance

Open Source Congress

Apache Foundation

UN Open Source Week

EU Open Source Week

 Alpha Omega Project for Drupal

by Nathan Wrigley at November 11, 2026 01:00 PM

Open Channels FM: The Hidden Costs of Burnout for Women in Tech

The tech industry is often celebrated for innovation and progress, yet behind the buzz, many women are weighing whether to limit their hours, step back from leadership, or leave the field entirely. Burnout is at the heart of this crossroads, and its impact goes far beyond individual exhaustion. In the most recent Gender in Tech […]

by Open Channels FM at November 11, 2026 11:08 AM

November 10, 2026

Open Channels FM: Debating AI’s Role in Open Source Communities

Open source communities are debating the role of artificial intelligence, questioning whether AI-generated software aligns with traditional values of collaboration and transparency, reshaping definitions of openness in the process.

by Open Channels FM at November 10, 2026 06:27 PM

WordPress.org blog: WordPress 7.2 Beta 5

WordPress 7.2 Beta 5 is ready for download and testing!

This beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.

How to Test WordPress 7.2 Beta 5

You can test WordPress 7.2 Beta 5 in any of the following ways:

WordPress Beta Tester PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edge” channel and “Beta/RC Only” stream.
Direct DownloadDownload the Beta 5 version (zip) and install it on a WordPress website.
Command Line (WP-CLI)Use this WP-CLI command:
wp core update --version=7.2-beta5
WordPress PlaygroundUse a 7.2 Beta 5 WordPress Playground instance to test the software directly in your browser. No setup required-just click and go!

The scheduled final release date for WordPress 7.2 is December 8, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who contributes by testing!

What’s in WordPress 7.2 Beta 5?

For technical details on the issues addressed since Beta 4, see the following links:

Continued Improvements to WordPress 7.2

WordPress 7.2 Beta 5 continues refining the upcoming release with additional security, accessibility, and compatibility improvements.

Recent changes include email notifications when application passwords are created, improved keyboard navigation in the WordPress admin toolbar, and accessibility refinements to Visual History. Additional fixes strengthen permissions for Notes reactions, improve compatibility with MP3 uploads, and address automatic update behavior in Git worktree installations.

Learn more: Trac #63927, Trac #66331, Trac #65122, Trac #66447, Trac #46544, Trac #66460

Further Refinements to Ipsum

The new default theme, Ipsum, receives another round of improvements in WordPress 7.2 Beta 5. Accessibility enhancements include improved keyboard focus indicators and view transitions that respect reduced-motion preferences. Additional refinements to block styles and patterns provide greater design flexibility, while optimized stylesheets and other under-the-hood improvements help prepare the theme for its final release.

Learn more: Trac #66631, GitHub #198, GitHub #187, GitHub #180

PHP 8.6 Compatibility Improvements

WordPress 7.2 aims to fully support PHP 8.6, which is scheduled to be released on November 19, 2026. The WordPress project has a long history of being compatible with new versions of PHP as soon as possible, and this release is no different.

As of the Beta 5 release, all known compatibility issues with PHP 8.6 have been resolved.

While all of the known issues in WordPress have been addressed, you will need to verify that all of your plugins and themes are also compatible with PHP 8.6 prior to upgrading. Keep an eye on the Making WordPress Core blog in the coming days for more detailed information about what to look for.

WordPress continues to encourage all users to run the latest and greatest versions of PHP.

Learn more: Trac #66648

How important is your testing?

Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute – whether or not you have experience. Details on what to test in WordPress 7.2 are available here.

If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.

Curious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

A Beta 5 haiku

One last beta blooms
Release candidate awaits
The finish draws near

Props to @audrasjb and @desrosj for pre-publish review.

by David Baumwald at November 10, 2026 04:59 PM

Follow our RSS feed: 

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this site, send an email to Matt.

Official Blog

For official WordPress development news, check out the WordPress Core Blog.

Subscriptions

Last updated:

November 18, 2026 07:00 PM
All times are UTC.