 All right, now really we can go to question and answers. So just a quick sort of guidelines for here. We'll have two mics up here in the front so you can kind of walk up a lineup and we'll get to them. A light will briefly shine on you when you're gonna ask your question and say your name, where you're from and try to make it a question. Hello Matt, Ryan Kenny from Miami. As a volunteer speaker organizer and contributor that passionately supports WordPress and our shared mission to create a more open and accessible web. I'm concerned because I don't believe that we currently have a stated accessibility policy, community code of conduct, conflict of interest policy, code of ethics, diversity and inclusion policy or privacy policy. Between the foundation and, so my question is two part. The first is between foundation and the project, who would be responsible for assisting us in creating and enacting those policies? And the second part is how is we as a community, how can we help make this happen and try to enact some of these policies over the next 12 months? That is a good question, thank you. One thing, I do think we do have some of those policies in place. Like definitely we have a privacy policy. So we do have some of those already. Maybe we need to make them more discoverable. Yeah, I don't believe that they're published. I'm on the core contributor for privacy and we've been working as a team on it, but I don't believe that it's been finalized and published yet. Well, let's make sure it should be in the footer of WordPress.org. But I believe we've had one of those for a little while. For the others, I would say that the first priority is always making sure that what the purpose of each of those policies is that WordPress is embodying. And I'm very proud with the improvements we made to all those areas in the past year and beyond. You know, especially particularly accessibility. And that is in spite of there being a policy or not. We've tried to enact bigger changes in WordPress in a policy-first way in the past. And to be honest, it felt nice, but it didn't always make things actually change. So when we've said every commit must be X, Y, Z or something like that, or just maybe had it as a broad policy, like I think we did one for accessibility on the theme directory once, didn't have the same impact as when we actually built the tools or worked alongside folks to make the changes. So I do think about that. I also think about how can we make all these policies that be about things that we want people to do? Not all negative framing. I was a little, it was pretty noticeable when you came in here. Some of you might have noticed the first three things you saw when walking into WordCamp US were costumes, weapons and a coat of contact. I was like, whoa. Like little placards for those following on to home. They were like big black and white placards saying what wasn't allowed mostly. I think we've always done really well in WordPress where we don't try to enumerate every possible thing we don't want people to do, but really talk about the principles of what we want to create together. And I would love for us to also evolve how we present ourselves at WordCamps to incorporate more of that. Well, thank you. In terms of those other policies, let's talk about tomorrow contributor day. So we can sort of dial in which ones are there versus not and talk about what might be a good process for getting the rest out there. Perfect, I look forward to that. Thank you Matt. Thank you so much. See you then. All right, we're gonna bounce to the left. Hi, I'm Alicia from Canada and I was really happy to see a number of security talks this year and there was one this morning on auto updates where I learned that there's like 80,000 plugins now for WordPress, which is awesome. But I work for Sikuri and we know that a lot of sites get hacked through plugin vulnerabilities, not through core vulnerabilities. So I'm curious about, you know, the future of auto updates for plugins, but my main question is, you know, most users don't know this. So how can WordPress and the community better inform administrators or maybe even email, somehow notify them about security risks of deblaying plugin vulnerabilities, the potential risks of breaking sites with auto updates and some alternatives like virtual patching? That is a super good question. And one of the things that is one of the nine focuses for the year, I think it is super, super, super important. We're laying some groundwork. So like that admin email I just showed will allow us to more, we wanna use that to message people, not just about core like we traditionally have, but also about the plugins they're using. So that is part of the reason for getting that in. And sometimes we have to build the foundation before we build the house on top of it. So that was one of the things that we realized we didn't really have a good up-to-date version of. Over time, you know, very much the hill that we're, or the mountain we're trying to climb in the distance is that you just log into WordPress and it's safe, secure, and you get the latest and greatest. And you shouldn't have to think about whether something's a plugin, whether it's in core, whether it's part of your theme, whether you customize your theme, but then there's a security update to a different part of it. Like we need ways to handle all of these possible cases and update at least for the sites that allow us to, right? So the file permissions as such, as many sites on the web as possible. I would like to call out and thank the web host here. So almost every major web host, certainly all the ones that we promote, do automatic updates of core for both major and minor releases. And yeah, that's been fantastic both for us, because that means people are getting the latest and greatest WordPress, but also for them, because that means the sites are less likely to get hacked or compare a four-year-old version of WordPress to like today's proprietary alternative. The other thing that I'm starting to see more adopt, we do this on WordPress.com, lots of other hosts are starting to do it too, it's auto-updating those plugins. So if you are a web host and you're not auto-updating plugins yet, figure out how to make that opt out and get as many of your sites on the latest versions as possible. It is true that most vulnerabilities we've seen, and certainly the ones that have affected most sites have been in plugins and themes. And themes are particularly hairy, because people might have customized the code there. But these are, it's all just code. And so for sites that give us the permission to modify these things by the file permissions, I think that we'll be able to tackle it. It is really, really impressive what we already have. I know for those of you who are at the auto-update panel, we had Nace and a few others there, we forget that it wasn't that long ago, five or six years ago, that everyone had to update their WordPress manually. And we now get over a 99, usually 99.9 and 99.5 auto-update rate and allows us to get usually like 60% plus of the WordPresses in the world on the latest version within a few weeks, which is not as good as iOS, but way better than Android. So we're, as a true platform, which WordPress really is, it is the operating system for the web that's gonna power so many things that we know now and so many things we can't even imagine yet. It's so, it's really, really important that we invest in that auto-update mechanism. Thank you. So thank you. It's our great place to contribute it, especially if you work on security stuff. Am I all right? Hi Matt, my name is Mika. I'm from Yoast and from the Netherlands. And so at Yoast, we're really into Gutenberg and we're making Gutenblocks. We have a lot of schema updates in Gutenberg, but our research shows that only half of our customers use the block editor. And that's hard because that means that we have to basically maintain two products. And I'm wondering if you know how we can convince more people to start using the block editor because there is a lot of negativity surrounding it and we're trying to be supportive, but it's hard to get there. And I saw Yoast post some of these steps. It was the post with the most comments we ever had. I believe you're assuming that every user of the classic plugin is not using Gutenberg, correct? No, we did research within our audience and asked them what are you using, classic or the block editor. And half of them answered, we used the classic editor. So more of a survey? Yes. Yes, I know surveys aren't all, but still it shows that a lot of people aren't using it. So we have about just by the numbers, we think, like I said, almost three times as many are using Gutenberg than not. So we think only about 25% are kind of using the classic editor of people who have updated and not all of those are using the classic editor all the time. Some of them are switching between Gutenberg. So it's 25% or below that are still on there. I think the way that we get people on is first improving Gutenberg, right? There's been so many changes. If you're one of those people who's not on Gutenberg yet, that's okay, we're still making it better, but I'd encourage you to take every couple months, like every two or three months, every major WordPress release, try it out again and see if the things that frustrated you have been addressed. Two, I think it's blocks. So you notice how on that tweet, Hannah talked about how I really want this cover block. I do believe that block first adoption will really help things. And so as, for example, in Yoast, if just making things up, like let's say you had a really cool new feature that was Gutenberg only, that would be a great reason for people to upgrade. Though, I say that knowing that you all have done as much to contribute to Gutenberg as like anyone else in the world. So actually a quick round of applause because pound for pound, Yoast gives more back than us anyone, a CEO, I know a lot of that's due to you. So thank you. So I think that is what's gonna drive it along. But also let's recognize that we're only a year in, we've got 75%, that last 25% will probably, it'll be like a parabolic curve. But I do think that, I mean, we still have 10% on versions prior to 5.6 of PHP. So I do think that we'll kind of asymptotically approach like 85, 90%. And that's the point when as plugin developers, I would say, you can really focus on Gutenberg first for everything. I just hope you're right. I would be very surprised. I mean, we'll check this next year. We can update all these stats. I'd be very surprised if not 90% or more of all new posts going in WordPress next year were Gutenberg. So, but we got a lot of work to do, right? Because think of it, also some of the stuff coming around the corner, like real time co-editing, right? I could see that being a really compelling feature for people that'll help them make the leap to Gutenberg. And of course in Gutenberg, you can still use a classic block. So you can actually still have almost exactly the same interface inside of Gutenberg. So there's lots of reasons for people to upgrade. Thank you. Thank you very much. Let's see over here. I'll just check time, all right. Hello, I'm Milan, it's up from Serbia. So I'm raised, born and raised in communism. And now we try to survive democracy. And yeah, so. Me too. Yeah. Well, the second part. So looking at open source project, the idea to me is closer to communism, but I wouldn't advise applying that. But also democracy doesn't work. So I'm thinking, yeah. So my question is looking at WordPress, I don't see any system there. And I wonder when will we see something that we can identify as a system for making plans, making decisions, what are the names, something like that? That's a good question. I'll take a face value, all your value statements on different political systems. And say that WordPress is going to look different and maybe none of the political analogies directly apply because it is software. And so. There are other open source projects that have some kind of system and it works. I think we should call what we do the WordPress system. Okay. Yeah, it's like. When will we see it? It was actually one of the, I know the WP governance project kind of fizzled out, but one of the great outcomes I think was, they kind of documented how decisions get made, the team structures for doing so. The good news is that, you know, basically everything except, you know, like choosing the jazz name for a release happens in a Slack or P2 or GitHub or track channel somewhere. There's even, you know, there's a contributor to WordPress who I was talking with and they were like, ah, you know, what happened about page got made and like the secret process, I want to be a part of it. And then realized that that all just happened on track. So almost everything you see happens as part of an open process. So there's a lot of transparency. And so through the actual organizational structure, I think that it's changed in the past that will change in the future for depending on who's contributing, their strengths and weaknesses and what all organizational structures are a series of trade-offs. So what we're trying to optimize for at the time. So prior to when I took back over, we kind of have the lead lead role, we would say that for each release, there was a release lead that had ultimate authority, including over myself, for what was going to be in that release and you know, the buck stopped there for everything. And what we were trying to do there was increase the sort of flexibility that release leads had because we got into space where releases were a little more incremental and we want people to feel the autonomy to do bigger things. So I would say that kind of like an outfit you try on for different outcomes that you're looking for. And these different organizational structures will try different things for different parts of WordPress. The key that for everything we do, I think will be that transparency. And of course that we're open source at the end of it so that the product is something just like that film was Creative Commons. It's so cool that whatever we create as a community is available to the community as well. Thank you so much. Thank you. We needed, if you have any good words for that too, like what is kind of a transparent do-walk or see or something like that? All of these words have trade-offs, so. Hi, my name is Paul Wilson. I'm from Hawaii. I actually came here on another conference but I think most of your Southern California automatic employees were on my same plane. Cool. And I learned about this word camp so I jumped over to here. So. But I teach digital entrepreneurship at a university in Hawaii and WordPress historically has been the main thing that we go to. And so I have two questions that deal with that in particular. First is the bullet point. I wanna make sure I got it right from your presentation implementing full site editing that kind of slipped in there at the end. And I feel that's what's really been eating at WordPress as market share as you have Wix, Weebly, all the other ones that I see my students gravitating more because they like the customization of being able to edit full site without being restricted to themes. And so my question on that one is we've seen acquisitions in the past such as WooCommerce where you've brought them in and we've seen tools like Divi Elementor page layer that already have all of that in place. Is that something that you guys would consider to help make it more competitive and make it more realistic for people that are just getting started where they can customize without having to be locked in theme-wise? Totally. So a good way to look at it, there's probably at least 25 that I looked at of these page builders that would each have its own data model, each way of doing things for solving this problem that you said. So part of why we started in Gutenberg was to provide them kind of like a common rails that they could all build on top of. So page builders I don't think are going anywhere but they won't need to reinvent the wheel of the basics like the core CMS stuff that will now be handed inside a Gutenberg. They can build on top of that and create lots of cool things outside of there. Full site editing is basically the realization of the original promise of Gutenberg which is what we wanted to do was essentially flatten WordPress. Take all these different concepts that you would learn in different places around WordPress and make them all blocks. So you could learn a block once and you knew that anywhere and what we're doing with the customization phase is breaking out the post box. So right now all those blocks we showed by default you can just have inside poster pages. We want you to have that in headers, footers, sidebars, whatever you want. So we're doing a lot of the work there to port things over. There's some more that needs to be done like navigation block is still not finished. It's a very complex interaction but certainly by this time next year and hopefully in the early part of next year we'll have it so your students and yourself will be able to take, like I said, look at any site on the web and just using some blocks maybe the 2020 theme be able to recreate that. So that is 100% where we're going. We're not, as far as I know, not going to acquire any of these plugins but you also don't need to, right? Because the plugins are going to continue and they're now going to be able to move even faster and work together more, which is also something we hear users say because in the past like choosing one of these is almost like locking yourself in to a particular way of doing things. If you want to use a different theme or something else that's not compatible you're still locked in. So this is a very user-centric model of trying to solve this problem for the entire WordPress ecosystem. So on the second... We got a lot of people waiting. So can I just really quick on the... Well, it's not a really quick question. I'll let you jump over to it. All right. Thank you for your time. Thank you. Hello, hello, and you've got the mic? I do. Hi, Matt. Michelle Ames from Give WP and WP Coffee Talk. And I would like to lighten this up for just a quick second and ask you a fun question. I ask every guest of my podcast, what's the biggest mistake you've ever made with WordPress and what did you learn from it and what's your proudest WordPress moment? Ah. The biggest mistake is a longer story. But there was a hot nacho episode. This is what it was referred to. Hopefully most people in the room haven't heard of it, a few have. But super early on with WordPress it was basically like completely unfunded and I'd like run out of money and we were getting a harder designer to redesign the logo. Actually, Jason Santa Maria who did do the logo we currently use, but then ran out before he was going to do phases two and three which were redesigning the website in the WP admin. Anyway, long story short, like someone paid us to put, paid me to put these links on the website. We're totally spammy. But it was kind of before web spam was a thing and also might have inadvertently like then invent but certainly popularized a way to hide content using CSS that Google was not yet aware of. And so that was definitely the worst thing I've done to WordPress and the web. My initial pinnage for that was creating a kismet. Which was to create something to fight web spam especially which I understood the people were doing there. But then hopefully the 15 years of WordPress following that and what a proud, I get incredibly proud every time we come together for these big work camps, US, Europe. And last year having 5.0 ship and being able to talk about it and see how the community came together. And I mean that really was the biggest change we made in our 16 year history. And this idea of going from kind of a document model to a block model of editing is it's impossible to overstate how important that is to the future of WordPress. So seeing how that came together and how we iterated in public, how it was all that happened, definitely one of my proudest WordPress moments. Thank you. Thank you. Hi Matt, my name is Wolf Bishop. I'm with WP Top Hat and I live right here in Southeast Missouri. So kind of home for me. I'm gonna kind of screw up the trend that she just tried to set up with a bit of a more controversial subject. One of the greatest things about WordPress is the fact that it's released under the GPL which means we can use, redistribute, change, plug-ins, themes, anything that's released under that license as much as we want either for free or profit. And we love that about it. This has brought about a trend of a growing trend of companies known as GPL clubs which redistribute plug-ins either free or for profit. And there's a lot of controversy in the community about this. Some people are absolutely for it and others are definitely against it. And this kind of attitude is mixed between both plug-in or developers as well as end users. I've spoken to developers who support it, developers who are against it, same with end users. So I think the community might like to know what is your official or unofficial opinion about these types of companies? Sure. First and foremost, I'll say it's allowed by the license. So it's something that is, at least in all the cases, I'm aware of the license. When we create GPL software, it's explicitly with that freedom. And we couldn't prevent folks like that from doing it without taking a lot of freedoms away from everyone here in this room. So it's one of those uncomfortable, almost like the First Amendment in the Bill of Rights. Sometimes it's uncomfortable, but it's really, really, really important. My personal view on it is that the customers there will get what they pay for. Yes, they can get 100 plug-ins. Well, one, it's weird to pay for that in the first place if they're price sensitive, but they're not supporting any of those developers. They're not practicing fire for the future in their own case by voting with their wallet for the software that they use. Sport that. I mean, I've started now where I pay for stuff I don't even need to pay for, donations or patreons or stuff like that just because I wanna see more of it in the world. How you spend your money is just as important as how you spend your time and any other resource. You're supporting a certain worldview. You're gonna encourage more of whatever you're paying for to happen. So if you're seeing companies, like some of the ones we've mentioned today, that are giving a lot back to WordPress, doing a GPL, creating great user experiences, supporting Gutenberg, all that sort of stuff, even if you don't need to, maybe just pick up their yearly license or something and think of that as a way of supporting more of what you wanna see in the world. And for these companies that are kind of taking lots of people's work, but not really giving much back, either to those core things or to core, maybe choose not to spend money there. Great, thank you. Thank you. Well, good afternoon. My name is Olivia Bassette and I'm from Miami, Florida. Obviously, I think it's safe to say that I'm from a different generation from most of the people in the room. So my question to you is, how do you think WordPress is gonna be adapted by the next generation of kids in K through 12 schools? Or how do you think you're gonna change the WordPress so that way kids and kids through 12 schools will want to learn WordPress and want to join the local WordPress meetups, like how they joined robotics and different things? Thank you. Well, first thank you. I believe, Olivia, you were one of the speakers at this work camp, right? Yeah. Very modest. So the example that you're setting is something that inspires. So this is gonna be on YouTube later and boys and girls, maybe of your generation will see you here asking a question, being a speaker at work camp in front of a thousand adults. And it's kind of beautiful. When I got started with WordPress, I was 19. And the old comic in the New Yorker, like on the internet, no one knows you're a dog. I would think like, it's great, on the internet, no one knows that I'm a 19 year old kid in Houston who doesn't have a comp side degree and is learning to code. People just were looking at the code I was creating and we started working together and we're able to create something that became a community, came a product that powers a lot of the web and that I'm still excited to work on every single day when I wake up. So those examples being out there, I think really help. The hero press stories, we probably need some more younger folks on hero press. See, tofu or somewhere here. Just kind of get more of that out there. Kids camps, I think will help. And finally, we need to, well, this isn't finally, we need to make WordPress easier and more accessible that will help with younger generations as well as older generations. And the last plug I'll put in there is something that happened this year was Automatic, which is my company, bought Tumblr. And we announced that we're gonna switch all that to WordPress. So there's gonna be a half a billion more WordPresses in the world and Tumblr definitely has a younger audience on it as its primary user base. And so I'm very, very excited as, it's not gonna be the first year but probably second or third year as those become WordPress on the back ends. Tumblr.com can be like a react front end talking to the WordPress API. And you can have a different user interface on top of that. And those folks, much like before WordPress, there was a generation that learned to code, CSS from MySpace and things. Like by going where there's a lot of youth activity happening already and it's a pretty fun site as well. The customization and the path we have there could allow them to graduate to be WordPress and maybe graduate being someone as cool as you talking at work here someday. Thank you so much. Thank you. Hi Matt. Becky Davis from Chicago. And I've been doing this a long time. I have sites that are out there that are six and seven and eight years old and I'm still maintaining them and they have thousands and thousands and thousands of posts in multiple languages. And you want me to switch over to Gutenberg? Are you kidding me? I do, but you don't have to. So my real question is, I've heard rumors that the classic editor is going to die in the future. Please tell me that's not true. What did we officially announce for a classic editor? 2022? Yeah, that's not cool. Well, there's a lot going to change between now and 2022. I guess. In the world in general. Like we'll all be like doing work camp on holograms or something. But so we, I think it went from Gutenberg release, we said four or five years that we announced at that point that we were going to continue maintaining the classic editor plugin. In reality, in open source, when things have usage, it gets maintained. And so the classic editor still has a couple of million users by 2022. Guess what? It's going to keep going. Guess what? We're going to still work on it. If it makes you feel any better, again, but we don't want to promise that. It's just because that doesn't encourage what we want to happen which is people start to adopt. And so hopefully some of the sites that are six or seven years old, maybe as you start to update them for a new design or something else, that could be an opportunity to also bring them over to Gutenberg. Or maybe that's something their users or you as a developer want to bring in. Like I've definitely, by the way, I have word presses that are 16 and 17 years old. And it's been kind of fun to go back and see like things that I used to have to custom code or have a lot of HTML and custom CSS. I can now recreate in Gutenberg. That's a little bit of work, but it's also really, it's kind of interesting and I learn as I do it. And I know it's going to be forward compatible because Gutenberg 100% is the future of word press. So if you were to ask me, 20 years from now is there still a classic editor? I mean, I hope not, but only because no one wants to use it. So sometime in between there, its usage will dwindle to the point where it'll maybe either be a niche plugin or not something officially supported. It's still open source. So that still means that people will be able to customize however they like. There's people who only post a word press using a command line. So use that as an example of some pretty niche things can still be actively supported and maintained. But I do appreciate if at some point in the future you take a look at Gutenberg again and try it out. I'm trying to play with it on new projects, but on projects with thousands of pages, how do I transfer that? There's no script for that. We should make a script for that then. Thank you. I will do the last couple, maybe two or three. What's up, Matt? Hey. Hey. My name is Christy and I have a question for you. You are a CEO, so you know. Or you have consultants that know that a key component of any successful project or organization is good stakeholder management. So this idea that in any group, we have a ton of people and a lot of the time, most of the time they have competing interests. If we have buyers and sellers, the buyer wants to get the most money, the seller wants to get the least money and we have to find a place in between. I think we could argue that the word press open source project has even more stakeholders than the traditional corporate structure that maybe has employees, buyers, shareholders. I'm curious what we're doing in 2020 and beyond to bring all of the different people with different motivations together in the word press project to work towards a common goal. The questions that we see here demonstrate, I can probably list about seven different kinds of stakeholders with different motivations, different incentives, different things they wanna see. How do we get everybody working towards that same goal of what we saw in the video, which is making the project and the world a better place? That is a good question. And I am so relieved you defined what stakeholder management was. Because for a moment there, I'm like, man, I'm a terrible CEO. I have no idea what she means by that. You gotta thank Andrew Nason for that one because he texted me and said, what's your question? And I said it and he goes, you gotta define stakeholder management. Oh, thanks Andy. Yeah, so maybe not the most corporate CEO ever. In terms of, but I do think about that problem quite a bit, which is there are so many people with different types of interests, different incentives, different motivations, different things that are important to them, special interest within WordPress. And it can be cacophonous sometimes, right? Like all the voices in the room. I also think it's part of what makes WordPress beautiful and exciting is that those voices occasionally come together and create like a chorus, or we can all go in the same direction. We're never gonna make everyone happy. And not everyone's ever gonna agree with all of our decisions. I'm sure there's many things I presented today that a lot of people would strongly agree with or say would be bad for the web, which is opposite of our goals. But what we do try to do is put our philosophy out there of what we're trying to do, the web that we wanna see, and the things that are really core to us. I came up in an earlier question, things like transparency and open source. And then say, if those are also important to you, you know, get on the bus and we'll take this journey together. If not, guess what, it's open source. So you can still, you can create evil press or something. And can. Sure, it's open source, you can fork it, you can change it, you can take the code, you can not fork it, you can use it for whatever purpose you like. And so you're not forced, but if you do wanna be part of this, what I would term more the community of people contributing to WordPress. We do have to think about how we present things. So it's state of the word, but it's also what happens at meetups, what goes on the blog, what gets translated into the 50 plus languages that WordPress is translated into. It very much is a global and multifactorial problem that is part of the fun of it. I was listening to a, I think it was a podcast with, who's the guy that does the documentaries, like Vietnam, Jazz, Ken Burns, right? The one that has the awesome pan effect. How cool that he has effects built into iMovie, like to be a director to have that, your name and effect someday. And he was talking about, they have this neon sign in their editing room. And I'm gonna butcher it, but I think it said it's complex because he covers these really interesting rich stories. And for everything, there's kind of a surface story, like the kind of tweet version that you can say about what happened in, gosh, I'm not like the Civil War or music called jazz. But the reality is it's really, really complex. And I tried to, I thought about getting like a neon thing that said that from my office after I heard that podcast. I think it was the podcast he recorded, Tim Ferriss, if you wanna check it out. So thank you for your question. Thank you. All right, next to last. Hey, Matt. My name is Jeremy Ward. I'm a senior back and engineer with WebDev Studios. And I was excited to see in your presentation today and was aware of the decision last year to upgrade the minimum version of PHP. And it's great to hear 83% adoption, I believe you said it was. 83%? Or plus 5.2. And so 83% of people on WordPress 5.2 are running PHP 7 or higher. Right, exactly. And that's awesome. The goal for this year, as I understand it, was to get the minimum version of WordPress onto 7 plus. And of course, I think it's next month that security updates for 7.1 end. I'm just wondering if you can elaborate on like the 10% the laggards, the ones that are still on the old versions and the conversations that you are planning on having with WebPost to get them up to date so that we can push everything forward. Sure. So one common bit of info that a lot of people don't know is that WebPost that we're running older versions of PHP that the PHP project itself was no longer officially supporting. We're still getting backported security fixes, usually from third-party companies that they would subscribe to or things like that. So although 7.0 will no longer be officially supported by the PHP project, it's a little bit like when we say we don't want to support old things. They just don't want to have to deal with it. They want to focus on making the new thing. But there are, you know, WebPost often subscribed to servers and there'll be, those people will still have PHP security updates. So it's not actually as end-of-life as a PHP project would like you to feel. In terms of what we need to do to pick up those old people, not old people. People on old versions of... I made a generational mistake there. People on old versions of PHP is we got to work with a host. You know, it's really something where, you know, apart from a small hand-fill that might be running like servers in their closet and on their home connection, like pretty much everyone runs WordPress on a WebPost, on a server image, on, you know, the great WebPost that sponsors work camps. And so one thing we're looking to start doing is start identifying which hosts or have those older versions and just use that to talk to them. They might not even know themselves but they have to have half a million WordPresses still on PHP 5.6 or something. So if we can expose that to them and kind of offer the best practices of what we've seen folks do to upgrade. By the way, this is also an area where I've seen direct competitors, hosts that compete with each other for the same customers, actually help each other out and open source their scripts and things that they used to do upgrades. We hosted some amazing stuff there. So we can bring these folks along but it's not the end user that probably needs to hear it at this point because they've been seeing the notices and everything for a while now. It's that we need to start working with wherever they're paying to host their website. Great, thank you. Thank you. All right, and we're gonna end on this one. I apologize, I know there's a few more questions but I'm very cognizant of time and for the folks that didn't get to it, come on up afterwards, I'm happy to talk to you. All right, so you've got the last question. Please introduce yourself. You're the celebrity that was on that video, right? Now I just wanna go and turn down somewhere because it's a bit embarrassing. I'm Matt, my name is Francesca. I'm the WordPress Community Manager at SiteGround and right now I serve as the release coordinator for WordPress 5.3 that hopefully, yes. November 12th, right? November 12th, I'm just a shouty bossy lady, everyone else is doing the work but one thing that I do, I also like- Not bossy, you have executive management skills. Yes, yes, thank you, thank you. I'm also a good listener. So one thing that came up over the past few months in conversations with many different people involved in the release is that they feel it will be great to have a calendar of releases, a year-long calendar of releases. So how do you feel about having a calendar for 2020 for the next? Because you said yourself, three releases at best every year. So how do you feel about having a calendar for 2020? This is a good one to end on. Let's do it. Yes, yes. Sure, thank you. There's no reason not to. We do kind of a version of that early in the year. So we might as well map it out. As long as people realize that those dates might move, you know, in the New Yorker when they say they're going on to the town, they're like, musicians leave complicated lives, developers leave complicated lives, and some things might move those. It depends who's bossing them around, you know. But, oh, maybe the releases you lead will be super on time. Who knows? We'll have 10 days to see. And the place that we should have that, and we have had it a little bit more in the past, I guess we just fell out of updating it, would be slash about slash roadmap, probably the best place for that. And that shows the days of previous releases, the jazzers they chose, and then we've previously showed some of the updating ones, but I guess we fell behind there. So let's fix that up a contributor day. Let's do this. That will be done. As we wrap up, just very quickly, I would love to invite all the organizers for WorkCamp US this year to the stage really quick. So if you were involved in organizing, doing something, coming up, coming up quickly, quickly. Maybe not too quickly. We did, was it WorkCamp? We did have an injury when the organizers were coming up at a previous one. So, come up carefully. Okay, come on, come on, come on, come on. Keep coming, keep coming. All right, wait for everyone to get here. Oh, come on from this side too, oh, okay. Oh my goodness. Look at this, look at this. Is this the 47 that we talked about earlier? I'm glad we had it rammed, that's awesome. All right, we're missing one, but so, can we do a quick round of applause for putting this together? Thank you so much. And all right, let's go. Thank you all so much for an amazing state of the word. I'll see you next year.