 Alrighty, good morning everybody, have a clicker, thank you. So I'm Dries, I'm from Belgium, and I'm here to talk a little bit about Drupal today. So what I wanted to talk about today is winning the hearts and minds. As many of you know, or as many of you are about to find out, Drupal is really built on passion. Passion from users, passion from developers, and I would like to see us build even more passion by winning the hearts and minds of people, and I think we can do so through innovation. So before we start, I wanted to give you a few quick examples of really cool innovations. So here is one, which is the fish carrier, some more, soundproof underwear, obviously a really great innovation. We have the Beard scarf, the good news is they also have a kids version, so you can go as a family. There's the cat duster, not everybody likes cats, some people have babies, so there's the baby duster, there's the noodle cooler, and then my favorite is the noodle-eater hair guard. But the real question, of course, is what kind of products win the hearts and minds of people? And so let's look at a few companies or products which were once perceived as being innovative and today no longer are, and you see some of the examples up on the screen, like Kodak or Palm or Nokia and some other technologies. And then on the flip side, there is products like this which we all relate to probably as being very innovative companies like Apple and Google, Facebook, Twitter, and so forth. So the real question is what's the difference between these two categories of companies or products? And the answer is not a propeller powered lazy boy, but continuous innovation. That's what separates the first or the last companies from the first companies. So let's talk a little bit more about that. So if you look at the typical lifecycle of a product, it typically has four phases, the development phase, it has the growth phase, the maturity phase, and then sort of the decline phase and adoption increases, install base increases over time until you reach the decline phase. So what that means for Drupal, for example, I would say Drupal 7 right now is kind of, has just reached the maturity phase. Drupal 7 grew very fast. It grew about 2.5 times as fast as Drupal 6 in terms of adoption, so the way we measured that, by the way, is we looked at how fast we got to 100,000 installations measured by data though. And it took, I don't remember the exact length, but it took Drupal 7 2.5 times less time to get to 100,000 installations. Also, Drupal 7, the number of Drupal 7 installations has now surpassed the number of Drupal 6 installations. So there's more Drupal 7 sites out there. So we could probably put Drupal 6 there. It's actually sort of declining as people migrate or upgrade from 6 to 7. That's what happening. And then obviously Drupal 5 is on its way out. It's obviously still maintained, but fewer and fewer people are using it. And then of course, as most of you know, I think we're working on Drupal 8 right now and it's very much in the development phase. And we'll talk a little bit about that as well. So let's go back to innovation though. So how do these companies innovate? So they innovate because they sort of extend those product life cycles. In the case of Apple, they do so by launching new products like the iPhone, the iPad, and also the iPods. And so where these other companies failed is that they stopped innovating. You know, and a great example is Kodak. They actually owned the analog photography market and they invented, I don't know how many people notice, but they invented digital photography, right? Back in 1975, I think. But they've never been able to really capitalize on that. They weren't bold enough to change and to disrupt their own analog photography business. So reinvent themselves and to innovate. And so they died. So there's a big lesson there and a good reminder for us to continue to embrace big changes. And I'll talk about of these big changes in this presentation. All right, so in terms of Drupal, obviously we don't have multiple product lines like the company like Apple does. We only have one product which is Drupal. So the way we innovate is by making each version of Drupal better than the previous version and adding more cool features to it. So that looks roughly like this. So if that's the way we innovate, what does that mean for Drupal? So let's have a look at the past and the current, I guess, to figure out what we need to do going forward. So I wanted to start here with a little bit of Drupal self-reflection. I wanna talk about Drupal's strengths. I wanna talk a little bit about our weaknesses, which is maybe unusual for people that go to traditional technology conferences. But I do like to talk about our weaknesses so we can learn from them. I would like to talk a little bit about the opportunities that we have and finally some of the threats. But before I do so, I wanted to give the floor to a number of people. So I went out and interviewed a number of people, people that use Drupal in a big way and that are pushing the limitations of the platform really. And I've asked them to comment on these four things and came back with a little video which I'll show you now. We had tried a lot of the enterprise content management systems out there. A lot of them were sort of legacy systems that were modified to work with the web. We narrowed our search down first open source and then secondly we looked at communities around the various open source platforms. And it didn't take us a long time until we came to Drupal and saw that it was a very vibrant, large community that was very active in developing Drupal and pushing it into the future. Obviously it's the community. I went to my first Drupal Con in May of 2010 and was just blown away by the ecosystem and the energy. So having a very flexible, robust platform comes from having a vibrant community. The opportunity in the marketplace is huge. I don't think that there has ever been a time where the commercial products in the open source products were either so evenly matched or if anything the open source products probably have a richer feature set. We made the pitch that we're gonna choose this new platform. We're gonna deliver something on the web within one month which for a big company that's typically a very difficult thing to do. We had our first website was our exchanges platform which is our blog site out in end production within 30 days. Being able to handle video well. Being able to handle like text blog content well. Being able to handle community features well. And being able to combine those into a single cohesive site. Certainly some of the challenges with Drupal is talent starvation. How do we get more people involved into Drupal and how do we get them up to speed? I would like to see Drupal evolve to a place where mobile isn't something that's an afterthought. Works on any browser, any screen size, any phone. There's a tremendous opportunity there to simplify workflow to make things easier for editors to perform everyday tasks. The opportunity for Drupal is enormous. From where I'm sitting I see a world where multi-million dollar CMSs are going out of fashion. It really is an application platform and a platform to build web applications on top of. And I think Drupal's perception needs to break beyond that it's just this content management system. We'll start to do a lot more with mobile. So I'm very excited about the opportunities to expand on our desktop experiences and bring those to the mobile web. And we're gonna be leveraging Drupal to do that as well. I think that the vision is solid. I think that they wanna take Drupal to a level where it continues to get easier and easier to deploy web content. As these companies are making this transition for the first time into this new ecosystem that they're getting very excited about, Drupal is going to be at the forefront of that decision-making process. I think the Drupal community represents what open source is all about. It's been great. I feel a tremendous amount of promise. I love being part of the community and I'm incredibly appreciative for everything that everybody does every single day. So, there's a lot of things here in what they said. I wanna talk a little bit about these things in this keynote, but it's very consistent. These things are very consistent with things I hear everywhere. Like wherever I travel, these are the kinds of things people are saying. So let's break it out a little bit here. Let's talk about the strengths first. I think listening to the video, obviously community, community, community, people everywhere look at Drupal and they see the biggest strengths, honestly being you guys. So that's a huge testament to all the work that you've done. So, obviously what does that really mean? So, if you think a little bit about it, the fact that Drupal is open source, the fact that we can share a code that the license allows us to share code leads to collaboration, right? And that kind of collaboration leads to community and I think the important step is that community leads to innovation and that's, I think, why so many people really like Drupal. So, they like Drupal for the community because that translates into a lot of flexibility. Tens of thousands of us are taking Drupal and extending it in different ways, adding tens of, you know, thousands of modules really and that allows people to build pretty much any kind of website, right? It really changes the way people build websites. It frankly changes our industry. Like, where we're going from a world where people used to develop websites by writing code or by using frameworks to a world where people can actually assemble for the most part of a website. So, this vision of the assembled web and the kind of flexibility that that gives you is, I think, a direct effect of having a very vibrant and active community. And it's a big change because it is replacing a lot of legacy proprietary CMSs. So, a big opportunity there. So, obviously we can talk about our strengths all day. There's many, but I would actually like to talk a little bit about our weaknesses and, you know, the things that keep me up at night. Let's see. So, I really thought long about it and I came back with three things. You know, obviously there's a few more but I think it really boils down to three big things. The first one is the fact that we have, you know, a rudimentary authoring experience. And I think there's two big things happening right now in the world. First of all, and this is relatively new and it's kind of worrisome in a way for us, is that the content authors, the actual staff that needs to use Drupal from 9 a.m. in the morning till 5 p.m. at night or whatever, they're very involved nowadays in the CMS selection process, if you will. Whereas it feels like even a year ago or two years ago, it was mostly a decision made, say, by IT or by technical people versus the actual people using the CMS. So that's kind of an interesting trend, which means we need to put a lot more emphasis on the authoring experience. And the second biggest trend, and this is one that I've talked about in the past, frankly, which is the consumerization of IT. Like things like iPhones and tablets and all of these things have fundamentally changed the way people expect applications to work and the kind of usability people expect from these applications. So I think these two things combined really puts a lot more, puts a bigger spotlight on Drupal's authoring experience. So I do want to talk a little bit about that in this keynote. The second thing that keeps me up is our framework. Although Drupal still has, is still, in my opinion, one of the best CMSs, technically, we're also at an interesting point. Like if you look back at the early days of Drupal, Drupal was successful because it was very accessible to hobbyists. People could get it in the code, make some quick changes, you know, add to Drupal. I think for all the right reasons, Drupal has evolved to be more complex and some of that accessibility is lost in the process. At the same time, for more seasoned developers, Drupal is also a little peculiar. Like it isn't necessarily what they expect to be. So we've arrived at this point where it's a little hard for newbies or hobbyists and it's also a little hard for seasoned developers. So something for us to work on. And I'll talk about that as well. The third thing that keeps me up is, you like this image? It's a pool with small people. So it's a small Drupal talent pool. But this is actually a good problem in a way because Drupal is growing so fast. The demand for Drupal people, Drupal experts, continues to be bigger than the supply. And it's one of those things which is holding us back a lot actually. And it's an area where we're doing a lot of work on. The Drupal Association made it one of its priorities to help grow the ecosystem. There's things like Google Summer of Code which we should all participate in or help with. So there's a lot of initiatives to try and overcome this. But it is important that we continue to work on this. So these are some of the weaknesses. I'll come back to these in a second. So let's move on to opportunities. So according to Mary Meeker, who is a partner at Kleiner Perkins, I don't know how many people know Kleiner Perkins. It's probably the number one or among the top venture capitalist firms in the world. And so she said that we are now in the fifth major technology cycle. What that means is, I'll let it come up on the screen, it really means mobile. And so a lot of people are making very big bets on mobile. And so let's put that in perspective a little bit. So if you look at Drupal today, we estimate there's about 1.5 million sites. So big applause for everyone. That's a giant number by the way. But if you put it in perspective, it's only 6.7% of all the websites that have a content management system. So it's a pretty large number, but it is our first opportunity. The opportunity is to go after the other 90 plus percent. And I think we're well on our way. I think that number keeps going up. It's also where I think the platform vision comes in, like the one Drupal to rule the model vision, if you will, where we make Drupal better and more suitable for more different kinds of websites. So I think that number will go up over time. Interestingly though, only about 30% of all the websites in the world actually do use a CMS. So how many people knew that? Not many. So 70% of all the websites don't actually have a CMS. And that's also a huge opportunity for us because eventually either these websites will stop to exist or they'll probably move to a CMS. So making Drupal easier and better will also help us go after that piece. But the real opportunity, the biggest opportunity of all is really in mobile. If we believe the predictions, mobile is just about to explode and we'll grow by 25X over the next five years. And so in that picture, we're tiny, right? And we basically have kind of one shot at this with Drupal 8 to really go after mobile. So we're ready in five years. So that I think is a big opportunity and I'll come back to that as well in a second. So the threat really in my opinion is that we are unable to innovate and that we are basically being bypassed by other systems. So I think we've talked about that in the beginning, the need for innovation and the way we innovate. So all right, so that's kind of this section where we talked about the strengths, the community, the innovation, the weaknesses, the opportunity and the threats. So what does that mean, right? What do we do with this? Well, first of all, it means we need to start kicking ass with Drupal 8. And so in the beginning of the presentation, I said that I would like us to win the hearts and minds of more people. And so when I think about that, I would like us to focus for Drupal 8 on three different audiences. Developers, site visitors and authors. And I'll talk about each of those in this presentation. So let's start with developers. So I've already explained some of the weaknesses which is this aging framework. So what we wanna do there is really update Drupal a little bit. I think, as I said, Drupal is still one of the best TMSes in the world, but I think also some of us realize that if we don't innovate on the framework piece, we risk being left behind. And so we spent months and months discussing about what that means, technically and architecturally. And after months, we've decided to leverage pieces of symphony, but we weren't all in agreement still. And so we basically got like 15 people in the room together, locked ourselves up in the room for about three days. And what we came out of is that actually we do wanna use symphony and we probably wanna use more of it than we expected. So we've decided with Drupal 8 that we are gonna embrace portions of symphony. Could be quite a bit. And obviously that's a very big deal. It's a very big decision for us because it will propagate to our contribute modules, the way we work, the things we need to learn and so forth. So instead of me talking about what that means, I've made another video and I'll let two experts basically explain you what that means. Here we go. Drupal at this point is the most advanced and powerful traditional CMS on the market, but the market is changing and what is going to be a market leader in the next five to 10 years is different than what was a market leader in the last five to 10 years. Drupal right now has a huge opportunity to really reinvent and reposition itself to be the leading system of tomorrow as well. Symphony is two different things. First and foremost, this is a set of reusable and cohesive components that you can use for your PHP project. Symphony is also a full stack framework and a full stack framework means that you have a tight integration between all the components and you don't need to make the glue yourself. We are one of the first big framework to have embraced PHP 5.3 and all the namespaces and stuff like that. That's the first point. And the second one is that we have tried to make it really flexible. I think the second version is really great if you want to create products on top of the framework itself. When we were working on the WISC initiative, we had a number of goals. Easier support for web services and being able to build more robust page layouts that could do partial page caching, could do edge side includes, could do a-ha callbacks in a much more efficient manner. And I think that's a going to be cultural shift for Drupal but a positive one and one that we are ready for and will benefit from immensely, which means that enterprise developers coming to Drupal will have an easier time adopting it. Developers coming out of computer science programs will have an easier time adopting it. It means that we can produce smaller pieces in modules that we can assemble LEGO style in Drupal in a site and build a more tailored site with less work. People who want to use Drupal as both a content management system and a framework get a stronger underlying foundation for both. Are we excited about this or not? It's kind of a big deal. I mean, it's a very big deal. So expect to see many of us talk about this at Drupal.com. Fabien, the symphony project needs will is actually at Drupal.com and there will be a session this week on symphony and possibly other sessions as well. So if you're interested, make sure to attend these sessions. And I couldn't explain it better than Larry and Fabien, but obviously symphony brings as many benefits. It's for people that really don't really know symphony. It's a well-tested open source project. It's very compatible. It has a very welcoming community behind it. We've had amazing help from these people in trying to do prototypes and stuff. And it's very solid technology. There's a lot of people using it. So I think by leveraging symphony and by working with the symphony project, we'll be able to go to more places faster, especially on the technical side of things. There's a lot of interesting things in symphony which will allow us to build more pluggable websites. It's gonna be easier to remove components from Drupal. But it also allows us to get to the next level of scalability because out of the box, for example, symphony has embraced edge site include. So it changes the way we can cache pages. It changes the way we can render pages. And in doing so, we can go after bigger websites. For me, one of the biggest advantages of symphony is that it actually will help solve that, you know, small Drupal talent pool issue, I hope, I think, I believe. Because by adopting a modern framework, I think we'll be able to get more developers, more seasoned developers, but also more junior developers and hobbyists because ultimately people wanna work with the tools of the future, right? They wanna use, you know, for their own careers, they wanna use the tools that will get them the furthest along. So that's kind of the first big thing, symphony. The second thing I wanted to talk about is what we need to do for site visitors. And I've already talked a little bit about this today, but I've definitely talked about it in previous keynotes, is we need to build a great mobile experience. And it also came out of the video. But if you think back, if you look back, in 2000, all the traffic came from desktop browsers. 10 years later, only in 2010, 3% of all the traffic came from mobile. If we are to believe these predictions, then by 2015, mobile traffic will be huge and will be bigger than desktop-based traffic, if you will. And so about a year ago in my keynote in Chicago, I said if I were to rebuild Drupal from scratch today, I would build it for mobile first and desktop browser second. And so I really believe if we need to change Drupal, turn it around so we can embrace mobile. If you think about mobile, there's different kinds of mobile if you build. There is native applications that run on your mobile devices, like iOS or Android. And then there is mobile web experiences, meaning people that visit your websites through a mobile browser on a mobile device. And we need to do the right thing for both. Because we need to do the right thing for native apps because I truly believe the web is changing from just web to web plus apps. I think that change is pretty visible to most of us. As Drupal, we need to embrace that. What that means and what we're doing here is on the native app side, we are adding restful web services to Drupal Core. We want to make it very easy for people to retrieve content in Drupal in different formats. And we want to be able to expose some of the CRUT functions, the basic operations on Drupal objects through APIs. Also think, and this is something we haven't talked much about, also think that maybe we should start thinking about adding SDKs, software developer kits to Drupal and possibly maintain these as projects on DDo as well. So people have starting points to build mobile apps. So hopefully something we can talk about this week. And then on the mobile browser side of things, we are working on making HTML5, the default output of Drupal 8. And we're also working on adding things like responsive design and all of the things that you would come to expect there. So a lot of things going on there, a lot of progress being made. I think an area where we could do better is embracing a mobile culture. Like when we work together in issue views, I almost never see anyone share a screenshot taken on their Android or taken on their iPhone. So we still need to get it in our DNA to really truly embrace mobile. And it's important that we do this now because we need to do it before the rest of the world does it. Because we need to build Drupal so that it's ready by the time the rest of the world wants it. So I think we need to work on this a little bit more. So maybe everybody should get an iPad or something. If you reach under your chair, it's provided by the Drupal Association. I'm joking. But maybe you can ask your boss. But I think it would be really helpful for all of us to do this. All right. And we'll talk about this at this conference as well. So the third audience is the site visitors. Sorry, it's the authors. So we talked about site visitors. Let's talk a little bit about authors. This is a big one. It's probably the newer one for most people. But as I said, Drupal today really wins based on technical merits. And so we did a whole bunch of research, and I created this kind of like spider graph. But it basically what it shows you is different content management systems. And we've rated each of those based on technical strengths. And so I'm not sure it's very readable, but there's scores from zero to eight. If you have an eight, like Drupal, it means you're the best. And so you're all the way out there. And if you have a low score, technically, you're more towards the middle. So Drupal is winning on technical strengths. But if you look at the authoring experience, I think it looks a lot more like this, where frankly most of the other systems are better. And so that's an area that we really, really need to work on. So if you look at the authoring experience in more detail, and you break it up in several components, you know, what does it actually mean, authoring experience, right? So it's like inline editing, workflows, mobile authoring, localization, layouts, all of these things. And if you look at all of these competitors that I just showed you, and you take the best from each of them in these areas, you can sort of create an ideal product, roughly, right? And that's what's shown in orange. And then we looked at Drupal and overlaid that with the ideal product. And so what it shows you is that we're doing pretty well on the workflow site. And that's, you know, thanks to contributed modules like the workbench module and other things. But we're doing pretty weak, for example, on the inline editing side of things. And some other areas. So ideally, over time, you would be able to sort of, you know, spend the entire graph and get a lot closer to what I think would be the ideal product. All right, so what does that actually mean? I think it means a couple of different things. First of all, I think we should put more stuff in Drupal 8 core. Because a lot of these things are expected. A lot of these things are what I would call infrastructure that every person needs. It's like, people want more inline editing. People want more drag and drop. People want more improved content administration tools. People really want better media support. Like, that's why people get a content management system, to be able to manage the content, right? And people do want better page layout building tools. And I think a lot of these things we should try and put in core, which would, you know, obviously make core bigger. At the same time, we need to keep core very pluggable. Because we also need to recognize that distributions are the best way to build, you know, specialized user experiences. Like these things core can do, core can provide the infrastructure. But to really create the best user experience, you need to know the audience. Often distributions, they know the audience that they're built for. So, we're also doing a lot on distributions. One big thing which we just did is we changed the way we can build distributions on D.do. We can now include external libraries and all of these things. Which is a big change. We're also working on better promoting distributions on D.do. There's a lot of events happening to help grow a community around distributions. And ultimately, I think the big one is we really have to figure out the revenue model for distributions. Because I think if people can make money with building distributions or more money, you can actually make money with distributions today. But if more money could be made, I think it would cause more people to build really great distributions. I think distributions are the way to... If you go back to the planets, it's the way to capture more of the other things which we aren't doing yet. So, here's a quick screenshot of some of the things which we're trying to do on the Drupal main page. As you can see on the screenshot, we're trying to make distributions. First-class citizens by adding it to different pieces of the website. These are just mock-ups that gives you an idea of what is hopefully to come. And this is something the Drupal association wants to really start helping with. So, we're starting to build a bigger team of people working on D.do. So, obviously, it's kind of a big topic. It's not necessarily easy to pull this off because it's really hard, especially as we get bigger, to build consensus on what is one considered good usability and secondly, what should belong in Drupal Core and what shouldn't belong in Drupal Core. I mean, this is the kind of stuff which we have talked about for many, many years. So, here's a proposal on how to fix this. First of all, let's look at the Drupal 8 timeline. This was announced recently, but I'll announce it again. The goal is to get to feature freeze by December 1st. That's roughly eight months from today. Once we're feature frozen, there will be some time to complete the features which we started adding. And then ultimately, we want to freeze the code by February 1st, 2013 with the goal to release Drupal 8 at the next Drupal code in Europe. So, not the one which is coming, but the one after that, right? So, that's, I think, roughly 18 months from today. So, that gives you a sense of when you can start planning upgrades and things like that. So, anyway, if we want to nail the authoring experience in Drupal 8 and if we want to make progress there, we only have a little bit of time left. So, what I would like to do here is, you know, go through three phases. First of all, I think we should do some analysis. You know, we should do more talking brainstorming about what we want to add to core. I don't have all the answers. I think it very much should be a collaborative effort to figure out what we want to do. Then I think we should come up with designs, mock-ups, maybe even prototypes. And then by the end of July, I should really start to make some decisions based on these mock-ups, like we're going to add this to core, and this is what it's going to look like. So, we can actually start implementing it and basically implement the mock-ups that we kind of signed off on. Once implemented, hopefully these things will be able to get committed before feature freezes. What exactly will go in? I don't know yet. We have a lot of work to do here, but I think it's important that we have some sort of timeline and that we have decision-making points in order to get there. So, that's what I would like to do, and I'm sure we'll talk more about that this week as well. Other than that, we're also working on a lot of other things. I don't necessarily want to rehash all of them, but we've launched a number of initiatives for Drupal 8, and this graph actually tries to summarize some of our status. So, what it really means is that most of the initiatives, they're pretty much done with their analysis, meaning we have figured out what we want to build. It's kind of the what. Most of them are doing really well on the design phase, meaning we know how to build it. All of them are in the development phase. We know what to build, how to build it. Now we just have to build it. It's a lot of work. That's why it's important that more people actually get involved. We need a lot more help. If we want to get this done, we're going to have more people that need to contribute to making this possible. So, make sure to go to the sessions. Each of these initiatives will have sessions, either in the core conversations or elsewhere, where you can learn how to get involved and where you can learn about the details. So, I think if we do these three things, if we focus on these three things, I think we can win the hearts and minds of authors, developers and site visitors. I think that would fuel into a lot more passion. I think it would make Drupal better. I actually think it would help us overcome our weaknesses. We would do more of our strengths. It would overcome the weaknesses because we would go after, we would fix the framework thing with Symphony, we would fix the authoring experience with some of the work we're doing and actually think in doing these two things, we actually also help fix the talent pool issue, as we talked about. At the same time, by doing mobile, we actually go after the opportunity, which is also very important. And again, in doing so, we reduce the threat of being replaced by something else. And if we do so, I think we can make Drupal 8 very successful and I think it can translate in the next big bump in terms of adoptions. And with that, I'd like to say thank you. Thank you. And open the floor for some Q&A. I think we have about 10 minutes or so. Yeah. It didn't take very long before DrupalCon keynote was a trending hashtag in the US. I think three to five minutes and it was announced that it was pretty much out of control. So I think we got some good questions ready to go and I guess we'll start with some difficult ones and then move to the easy ones. So first one we have is from a gentleman named Art USA Mac. What is the limit of symphony integration and does it mean rewriting Drupal on symphony? Right, it's a good question. I don't have the answer. So we basically agreed to use certain components of symphony. At the same time as you saw on the graph with the progress bar, Larry and the rest of the team, they're still trying to figure out how far we want to go. So we have some things which we agreed upon and then there's basically still some great area where we want to figure it out still. So it's the best I can say right now. Sure. But go to Larry's session. You may have all the wisdom. Or at least some good answers for us. So we have another question from a design's drive. Will jubilee be mobile friendly out of the box? Yes. So the goal, that would definitely be the goal. So one of the things which we're doing is as I explained, we want to output HTML5 out of the box and then also we want to update all of our teams that ship with core to support responsive design. Excellent. We want to improve the admin back end. So it actually works great on mobile devices. So we're doing all of these different things through a number of these initiatives with the goal to provide a great out of the box experience on mobile devices. Awesome. That's great news. This is from... These are difficult questions by the way. We've thrown an easy one there. No. This one's from Mr. Randy Fay. Are there changes we need to make in our community or development process now that we have grown so large? That's a tough one. Thanks, Randy. I think the answer may be yes. I think we have a culture of making changes. If you compare the way we work on Drupal 8 versus Drupal 7, I think that's already a huge change. We put a lot more process in place in terms of number of critical box, which we want to have open but also the initiatives and putting people, the initiative leads in more of a spotlight, I think is a way to delegate leadership and authority and I think as we get bigger and as core gets bigger, I think we need to do so. I have a few other ideas in that area as well, which I'll talk about in my core conversation. I don't know when it is, but this week. But the answer is yes, and I think we've always been open to discussing these and I think we have a track record of implementing changes as well.