How are we today? Feeling good? Having a good time? Alrighty, so as usual, I do these every six months in a state of Drupal. I'll be talking a little bit about what we've accomplished in the last six months since I spoke at DrupalCon Chicago, and then I'll also talk a little bit about the future of Drupal and where I think we need to go. It's going to be a pretty packed keynote, I think. There's a lot of information there, so hopefully you guys will not like Zoom out or things like that. At the end of the keynote, there will be questions and answers. If you have a question during the keynote, just use the hashtag DrupalCon keynote. Somebody will collect all the questions and then come up on stage to ask me some of these questions. That's what you do to get your question asked. So before we start, I wanted to give a quick shout out to the Drupal Association, the DrupalCon organizers, and the many sponsors for making this possible. It's for them that we are here, and they just put on one of the biggest, well, the biggest European DrupalCon, so give them a quick applause. This conference has been in the works for over a year, so a lot of effort went into this to make this possible.  As I travel, I meet developers, users, organizations adopting Drupal. What I've been seeing is that Drupal is being increasingly more adopted by large organizations, but also by small organizations, but large organizations that are really starting to standardize on Drupal. I think a prime example of that is happening in New York right now. Pretty much all of the large media companies, about five or six years ago, five or six years ago, they essentially used all sorts of different platforms. For their biggest websites, say CNN.com and these kinds of things, they would use System A. For the medium-sized websites, they would use B, C, and D, and then for their smaller websites, they would use something else. Today, though, more and more of these organizations are starting to standardize on Drupal as a platform for all of their medium-sized websites, as well as many of their low-end websites. Although on the low end, we often see WordPress as well. This is true for all of these brands that you see on the screen. These are some of the biggest media companies in the world, all standardizing on Drupal as a platform, which obviously is great news for Drupal. I'll talk a little bit more about that in my presentation. But the same thing is happening in other industries. Drupal is still doing extremely well in education. I think it's one of the industries, if you will, where Drupal is being adopted the most. Drupal is also doing better and better in financial services industry. And this is also very important because it's traditionally a very conservative group of people. They're always the latest or the last people, I should say, to adopt a new technology. And right now, the Eurostar here in Europe is switching to Drupal for pretty much all of their sites. Same thing with the New York Stock Exchange in New York. Obviously we'll provide a lot of credibility to Drupal once they finally launch all of their sites. But more signs of Drupal being adopted more and more. Government, obviously, with the White House being a prime example, lots and lots of adoption in government still. Some of the sites are listed on the screen, but there's hundreds, hundreds more. Drupal is also doing well in high tech. A lot of technology companies adopting Drupal. The Twitter developer website, switch to Drupal. Symantec is using Drupal. Actually, in a very interesting way. I think it's worthwhile to pause there for a second. So what they have is Symantec.com slash connect. And it's a community website where users can help provide support for products and solutions that they have. And it's not the main Symantec.com website, but it's a sub-site. But they have more than 240,000 registered users. They have more than 740 or 750 pieces of content, questions that are being asked by people. And what they use this for is to essentially reduce their costs. Because 95% of the questions that are being asked, support questions, are being answered by volunteers in their community. So for Symantec, this is a huge success story. A huge success story enabled by Drupal to help them get down on some of these expenses and to innovate the way they work as a company. So it's not just about building a quick website. It's really about fundamentally changing how they work and how they participate with their customers. And we see that happen more and more. So all in all, long story short, Drupal is being increasingly adopted across all industries. Truly a global phenomena, if you will. So let's talk a little bit about Drupal 7. Obviously, we released Drupal 7. A lot of people have been concerned about the adoption of Drupal 7, relative to Drupal 6. We have a long way to go in terms of upgrading some of the key contributed modules. But at the same time, if you start looking at some of these statistics, you can see that it took about 12 months for Drupal 6 to get to 100,000 websites, whereas it took Drupal 7 only six months to get to the same number of websites. Although I think we're rightfully concerned about the adoption of these modules, or the upgrading of these modules. I don't think we should ignore the fact that Drupal 7 is being adopted more rapidly than any other version of Drupal before. Same thing is true for people contributing to Drupal. Number of commits per month has been increasing, especially since the Git migration. It really has spiked. And also the number of unique contributors has been growing month over month, as you can see in this graph. So, again, good news. More proof that Drupal is doing well. In addition, yeah, and some guy. In addition, thanks to Drupal 7, some of the new APIs, some of the innovation in Drupal 7, we're starting to see a lot of great things happen in the Contribute Modules repository. One of these examples is the Workbench module. I highly recommend that you check it out. It allows you to, you know, better control, define editorial workflows. Another quick example is the Media module. Asset handling, media handling has always been a pain point in Drupal and has always been one of the top requested features. Now, there's a module which is being worked on by a number of people which will hopefully address this. And this module, again, leveraged a lot of the innovations in Drupal 7. Another example is a Commerce module, which is, you know, soon to be released. Again, great example of how we were able to reinvent ourselves or reinvent Drupal's Commerce solution by leveraging Drupal 7. And, you know, very excited about the Commerce module. I think it's going to expose Drupal to a whole new world, to, you know, the large Commerce world, which is an humongous. So, hopefully, that will be good news for Drupal as well. So, all in all, I would say, I think we have a lot to be proud of, you know. Drupal is being adopted more and more. Drupal 7 is being adopted more and more. We're seeing better and better modules every day. So, you know, let's give ourselves a quick applause for getting it this far. At the same time, I think we have some interesting thing in our DNA, which is we're never quite happy, right? We're never happy. We're always super critical of ourselves. We're always complaining about ourselves and the work that we do, which is actually a great feature, I think, or a great aspect of our culture. So, in good tradition, if you will, I've organized another state of Drupal survey. I typically organize these at the beginning of every major development cycle. So, the last time I organized one was in 2008. And I presented the results in SEGET, which I don't know how many people have been to SEGET, but it's been ages ago. So, it was time for us to do another one, right? And so, in this keynote, I'm going to highlight some of the results, the results that I've found interesting, you know, and present them to you. After the keynote, I'll make sure to make all of the data available as well. So, I'll upload an Excel file or something so people can do their own analysis of the data as well.  But 3,000 people replied, which, you know, I thought was a very impressive number. Compared to last time, we had, you know, just over 1,000 people. So, 3,000 people, in my mind, means that the results are relevant, right? It's hard to discard some of these data points. So, before we get into the meat of it, let's take a look at who actually took the survey. Most people that took the survey, they labeled themselves as being proficient. And then there's experts and beginners. But then, if we started to correlate the answers of multiple questions together, we get something like this. People call themselves beginners when they have less than two years of experience with the group, call themselves proficient when they have two to three years of experience, and call themselves experts when they have more than four years of experience. What's also interesting is that people start off by calling themselves site builders. You know, they assemble websites through downloading and configuring modules. And then, as they become experts, they actually start to label themselves as developers. Lastly, another interesting correlation is that most of the beginners, they look at Drupal as a hobby. That's what they do in their spare time. When people are proficient, they make part of their income with Drupal. And experts, or the developers, tend to make all of their income with Drupal. So they're the full-time Drupal people, if you will. But most people, actually, most people make most of their money with Drupal. So it's, you know, there is some gray area in between. Of course, you know, many other people took the survey. You can see some of the, you know, some of the names or the labels that people gave themselves. I thought what's interesting is that only 1.1% of the people are marketing people, that even less people consider themselves salespeople. This one was also surprising because I really think we could also use many more of them, which are product managers.  So I think there's, you know, plenty of room, you know, to get more of these people inside of our community. I think at the end of the day, we want to build like a well-rounded community.  And I still think that's very much true, where we need to get more people in the community, especially I think these areas. And I'll talk a little bit more about that in this keynote as well. Where do the people come from? Most people actually came from Western Europe, sorry. Second was North America. And then, you know, pretty much all of the other continents. So truly, again, Drupal being a global phenomena, and that being represented in the results of the survey. As a quick sideline, I thought it was pretty interesting that Europe was actually bigger than North America. I would not have expected that. But it's very consistent with what we, you know, with what I see, which is, you know, extreme adoption in Europe right now. I think Drupal is probably growing faster in Europe than it is in North America. So before we get into the ugly, you know, the ugly parts of the survey, I didn't want to highlight this slide because, you know, it's an important slide because it sort of speaks to the fact that overall people are super excited about Drupal. People are really, really happy. You know, as you can see, awesome was one of the top keywords that people filled out. And the question was pretty simple. It was just a text field, open in the text field, and was, please describe Drupal in one word. And this is what came out. So a lot of people thought Drupal was flexible and awesome, which I think is great. Right. So one of the other questions that I thought was interesting is, what is Drupal's biggest opportunity? And these are the results. I'll let you read them. But the important ones are probably the top three, right, which is replacing legacy platforms and, you know, mobile and IT cost reduction. To me, that was actually surprising, right? Because these are very busy business-like things to bubble up to the top. So let's talk a little bit more about that. So I think what's happening with many organizations, you know, small ones, but also very large ones, is that 10 years ago, these organizations had probably one website if they had a website. Nowadays, most organizations have lots and lots of websites. Even, you know, smaller organizations that have their intranet, their extranet, they might have one or two microsites if they put on an event, or you name it. And then the large organizations often have hundreds, and some of them have thousands of websites all around the world. And so the way that actually came together is very organically. And as a result, these websites are being built by all sorts of different technologies, right? Like, for example, they started out building their corporate website using Vignette. At some point, the CEO of the organization wanted to blog, and so they slapped on a WordPress blog, and they wanted to build an intranet, so they used SharePoint. And so today, many of these organizations are basically, you know, a mess. They have many, many different websites running many, many different technologies as well. So some of it is, you know, Microsoft, PHP, Java, basically, you name it. So it's pretty messy. And so what's happening right now is that a lot of these organizations are starting to realize that they can actually standardize on Drupal as a platform. Maybe not for all of the websites, right? Drupal definitely is not the right tool for every website, but for many of these, you know, websites, people can actually standardize on Drupal. And, you know, that speaks directly to, I think, these two items, right? It's replacing some of the legacy platforms, and it also allows them to save money. It allows them to save money because there is no license fee, but also allows them to save money because they can simplify their internal teams. I mean, you don't need to have experts in all of these different platforms to, you know, manage all of your websites efficiently. And in fact, that's kind of what we see happening in the media, an entertainment industry. So this is a real trend. I've seen it myself. It seems to come out of the data. And I think it's surprising probably to many, maybe many of the developers in the audience, I would think, or maybe not. But obviously, this is sort of a big dream or a big vision, I should say, right? Sort of like making Drupal the platform to standardize on. It's not a small thing to do, but at the same time, I do think Drupal is uniquely positioned to fulfill that dream or that vision. Because I think maybe for the first time in history, there is a platform like Drupal that has the reach, meaning has a very large install base that has a scalability. And by that, I mean, can be used for small websites as well as for large websites. Traditionally, that wasn't the case. Like you would never use, say, a vignette to build a micro site, because it just, I mean, it would be insane, would be too expensive to begin with, and it would be too complex as well, right? So Drupal scales from large to small websites, and then third, it has the flexibility to be many different things. Because of the way we architected the system, because of the fact that we have thousands of contributed modules, people can effectively build any kind of websites by putting together the right modules. And distributions specifically will only help accelerate that, because they're like distributions optimized for intranets, there's distributions optimized for other things and so forth. So I think of all the open source CMSs, of all the CMSs in the world, I think Drupal is sort of at the right time and at the right place to really fulfill this big vision. It's a big vision, but I think it's possible. So let's talk a little bit more about that. So here is where it gets interesting as well, although probably a little bit more predictable. But another question in the survey was, who do we compete with? And more than a third of the people said WordPress. A lot of people said Joomla, typo 3 and so forth. So the majority of the people, is that me? Or the majority of the people basically mentioned open source systems. Very few actually mentioned these legacy systems that we were going to replace in the previous question. So what's up with that? And so anyway, I think we need to be very careful when we say we compete with WordPress because we shouldn't confuse the competition with the opportunity. The opportunities go after all of these legacy systems, as was shown in the previous results. The competition might be WordPress, but it's WordPress beating us at fulfilling that vision. Competition is not us replacing WordPress sites. That's a completely different thing. And I think it's very important that we realize that, because otherwise we're going to be stuck in this thing, in our brains, trying to compete with WordPress at the wrong level. And the competition might be WordPress, it might be other systems, but it's a race, potentially, to get to this vision, rather than a race to capture, say, the low end of the market, which I think a lot of people have in their minds. So let's think bigger, let's expand our horizon, let's actually start to investigate some of these other systems. It's great that we all know a lot about WordPress, but there is a hundred other systems where the real opportunity might be. So let's keep that in mind. Another thing which I think we all experience pretty much every day, but which also came out of the survey results, is that there is these trade-offs, right? On the one hand, we want to make it easy for people to get into the community. We want to be accessible to our website by making Drupal easy to use, by making Drupal easy to develop for all of these things. And at the same time, we have this desire to be better and better at the technology. We're adding these features, we're adding things like configuration management, you know, basically we're adding complexity, because we have a desire to be the best at the technology aspect as well. And of course these to create a little bit of tension. So that's demonstrated by the survey results. So one of the, you know, I think, you know, it is the question that already, actually I didn't talk about this yet, but the question was what are Drupal's biggest challenges? Like even in the top two answers, I think you see some of that tension, right? Configuration management in a great feature, but highly technical feature, right? It's not necessarily going to improve the usability of Drupal for developers. It's going to improve the usability for people doing deployments, but it sort of is at odds with the desire to be very easy to use. We also see it in the next section. So there was another question, which was what makes Drupal awesome? The number two answer was the number of available modules. And then the number three answer with the biggest challenges was, you know, it's challenging is that there's so many modules. And of course it's no surprise, but you know, it's another example of this tension. Yet another example. So another question was, you know, is Drupal a hobby, a part-time thing, or a full-time job effectively? Where do you make your money? And in SEGET, in 2008 the results looked like this. You know, today the results look like this. So although the number of hobbyists might have increased in absolute numbers, in relative numbers, it actually became smaller, and the number of people that make a living with Drupal increased, you know, significantly, I would say. And that also creates tension. Again, because in a way we measure the success of our community by our ability to attract hobbyists, to attract newbies into the project. And at the same time we're also maturing as a community to be, you know, more professional, I guess. We're, you know, many more professionals. And you know, I think people experience that. I think people experience that every day, and that creates some of this, you know, some of these debates that we have. All healthy debates. So, and again, it's important because, you know, as I showed in an earlier slide, hobbyists are in a way like the supply lines to our community. It's how people get involved. And so, again, we need to be very careful about that. At the same time, this increasing amount of complexity is also very natural. If you look at noise technologies like the cell phone, it's basically, you know, over time, these things get more and more functionality, more and more power.  However, I think, you know, Apple, I think is an example of, you know, of, or the iPhone, I should say, is an example of a cell phone that was able to break this paradigm. At least for me and people might differ. But to me, it's one of the, one of the most powerful cell phones that I've ever had. And at the same time, it's the one that's the easiest to use. So they've done a great job combining those two, two things in one. So it can, it is possible, but it takes a lot of rigor. It takes a lot of, you know, work to get there. So in a way, I think we need to, you know, we have this tension between usability and, you know, complexity and functionality. But I really truly believe that we sort of need to get over ourselves a little bit and that we need to embrace this because it's, it's not going to change, right? Usability is becoming increasingly important. It's important to get people in the community, but it's also important for people, you know, sort of in the enterprise, if you will. Everybody cares about usability. And I talked about this in Chicago a little bit as well, but there is this trend which people refer to as a consumerization of IT. And it effectively means that people, they used to be cool with using a terminal, you know, like black and green. But in today's world, thanks to mobile, thanks to, you know, all of these other emerging technologies, people actually come to expect a, you know, a very easy or, you know, a lot of easy, what's the word? They come to expect an experience which is effectively delightful, you know, very easy to use. And so we have to make Drupal easier to use. We have no choice but to make Drupal easier to use. At the same time, we have no choice but to add functionality. I mean, what are we going to do? Stop adding functionality. So, you know, we must embrace this tension. We need to get over ourselves and we need to figure out how to deal with this. And part of that will actually be getting more people involved in the community, more usability experts, maybe product managers, all of these people. And to rethink some of the, you know, some of our processes. All right, this is interesting too. And I might be using a dirty words. But how do we increase Drupal adoption? You know, 60% of the people said, we need to build a better product. Which I agree, it's a great way to improve adoption. Some people said more training and other people said more marketing. You know, reality is that these two, you know, these things serve a different purpose. Like, we can't just rely on building a better product because Drupal 8, I don't want to like announce a release date or something, but it might be two years out from now, right?  I mean, it's not sufficient to basically say, we're going to work on Drupal 8. And two years from now, we're going to, you know, we're going to increase adoption thanks to Drupal 8. I mean, there is long-term things we need to do, which is making a better product. And there's short-term things we need to do, which is actually training more Drupal people and actually doing some marketing around Drupal. I think a prime example is Drupal 7. We've spent, you know, three years of our lives with a thousand people working on Drupal 7. You know, we made it the best release ever. And then once it was released, we hardly marketed, you know, Drupal 7, right? It's like, oh, here it is. Have fun. And as a result, there's still a lot of myths around Drupal 7. People still complain about the fact that Drupal is hard to use. And, you know, yes, we need to make Drupal, you know, even easier to use, but we've made so many great improvements to Drupal 7. We've not successfully changed the minds of the bigger world about some of the great things which we've added to Drupal 7. And I think that's because we don't talk about it enough. Because we didn't promote Drupal 7 enough because we didn't really explain all the great things which are new in Drupal 7, you know, well enough. Another great example, if you want to compete with WordPress, would be to look at the WordPress websites. I mean, here's their showcase. As you can see, they use screenshots. Look at that. They have ratings, you know, all of these things. If you compare that to the showcase on D.O., which by the way is one click away from the main page, and where a ton of people go to, it looks like this. I mean, it's not really showing that we're proud of what we've built, that we're proud of, you know, how people use Drupal. So I think, you know, getting better at simple things, it doesn't need to be like putting on billboards in cities. It's just making our website a little bit easier to use and a little bit more attractive for people. I think it would come a long way in helping to promote our market Drupal. So let's make sure we invest enough time in our website. Let's make sure that we give the Drupal Association a mandate to, you know, invest more in promotion and marketing as well. Plus, and that's the last slide on marketing, I believe. Actually, no. It's also very natural, you know, it's very natural. As technologies evolve, as products evolve, they go from being primarily engineering driven to actually being, you know, more marketing driven. That's how you get them, you get them out there. And that's been true for pretty much everything. There's, you know, exceptions. And it even, I think, relates to this, right? I mean, we see our biggest opportunities replacing legacy platforms, NIT cost reduction. There's very little codes. There's very little engineering that we need to do, you know, to go after these opportunities. It's primarily a marketing driven opportunity where we need to tell the story. We need to tell people the vision. We need to give them use cases. We need to give them examples. There's very little, you know, again, engineering that needs to be done. That's not to say that we can't improve on the engineering side, but it's not necessarily where most of the action needs to be if we want to go after these two opportunities. That's different for mobile, though. All right. So I think, you know, how do we win in general? I think you need to have these three things. You need to have the best technical platform. It needs to be easy to use and it needs to be well marketed. And there's, you know, hundreds of examples of, you know, of organizations. You know, Apple, almost all of us have Apple devices. I think they're winning because, you know, they do all of these things really well. You compare that to another cell phone manufacturer, Nokia. They're not exactly winning. I don't think they're as strong technically as the iPhone, but it's definitely not as easy to use as the iPhone. They're doing a ton of marketing, though. So just marketing is not enough. If you look at Drupal, I would say, you know, we're sort of roughly like this. I think very strong technical product compared to many other solutions.  We're much better than some of the legacy platforms. We're not always as good as some of the open source platforms. So there's room for improvement. Is it well marketed? I don't think so. I think there's a lot of room for improvement there. So that, I think, is how we eventually will win. Alrighty. So let's talk a little bit about how we will win on the technical side and how we can make Drupal better technically. So let's talk a little bit about Drupal 8. So in Chicago, I actually spent a lot of time talking about Drupal 8, and I made some announcements around Drupal 8. First of all, I sort of revised the development process, announced this concept of initiatives since then, announced a few initiatives in my keynote, and I've added a couple since, but you know, web services, HTML5, a design initiative to add a new core team to Drupal 8. Configuration management and internationalization are the five active initiatives that we have. For each of those, we've identified an initiative lead. You can see their picture on the screen, and we have, every two weeks, we have a two-hour meeting with each of them, or with all of them, and they give a status update. So you can see a quick status update on the slides. Overall, I would say they're doing well. We've had some patches committed. Some of the bigger initiatives like the web services and the configuration management initiative don't have patches in Drupal 8 yet, but we're getting pretty close. Because they're so big, they take a little bit more planning and a little bit more architecture and prototyping, but overall, I would say we are making good progress on all of those. So quick applause for all of these five guys. Right. So the other thing I announced was this concept of gates, right? The initiatives, what it actually allows me to do is to accept bigger patches instead of hundreds of small patches. But for a bigger patch to get in, they actually need to pass a number of gates, like there's a performance gate, there's an accessibility, usability documentation, and testing gate. When I announced them in Chicago, they weren't really well defined, and a lot of people ask, like, so what does it mean to pass the accessibility gate? So what we've done since then, with the help of WebChick, is we've actually defined those initiatives, these gates, sorry, with the help of other people in the community. So it was very collaborative efforts, and I think we're very, very close to basically having them well documented. So I expected two yellow ones to switch to green probably by the end of the week. They're very close. So again, good progress. Something else which I announced was that there would be a threshold for the number of critical bugs. At no time, we would have more than 15 critical bugs in Drupal 8, specifically Drupal 8. And so whenever there is more critical bugs, I would stop accepting big patches. And we needed to shift focus on fixing critical bugs as a measure to keep the quality of Drupal 8, you know, sort of sane, and to avoid a situation like we had with Drupal 7 where we have hundreds of critical bugs, and we needed to spend months and months to work down the list of critical bugs. Since then, we've actually revised those thresholds. And you can read them on the screen. But we've revised them in such a way that we can actually balance progress on Drupal 7 with Drupal 8. Because one of the big questions was, so why are we working on Drupal 8 if Drupal 7 still has these, you know, this many major bugs? And so with these new thresholds, we're able to make sure that we make progress where we need to make progress, and that we don't run ahead of ourselves with Drupal 8. So they're all documented as well if you want to learn more about these. So in short, I think, you know, since six months ago, since I announced these things in Chicago, we actually made, you know, a lot of good progress. But is there more to do? And I think the answer is yes. I think the answer is yes, because if we look at some of the survey results again, one of the questions was, what are the top challenges? And I've shown these before, but usability came out first, configuration management and content staging. We're considered to be the top challenges according to more than 3,000 people. What are the top developer requests? HTML5 came out first, better APIs and content import and export, where the top three requested features. I thought content, import and export was interesting, because maybe it's related to the legacy replacement opportunity, where people want to be able to move existing websites to Drupal. And then another question was, as an end user, what are your top feature requests? And end users asked for media and asset handling, mobile support and wizarding support. So no surprises there, I think we've seen that for a while. So what I've done here is effectively taking these nine items, I sorted them by response count. So we have a prioritized list, if you will. And this is sort of the top nine requests, if you will, from a community as a whole. So I think one of the goals we should have for Drupal 8 is to basically knock down this list. Seems reasonable. It's backed by data. I think if you look at the items, at least for me, they're sort of in line with my gut feeling. Like yes, we need to do all of these things. And so the remainder of the presentation, I wanted to give you a quick overview of where we are relative to these nine items. So I have a little score card for each. So obviously HTML5, I think, I would say is green. It's on track. We have in the issue queue over a thousand, over a hundred, sorry, over a hundred HTML5 issues, which we basically need to work through. But overall, I think we're on track to sort of nail this thing. Media and asset handling. There is no official initiative for this. I think what people want is they want to be able to manage files through a file browser, but also better support for audio and video. So I think what we need to do, and maybe we can start this week here at the conference, we need to figure out what that means. We need to figure out what it is that we want to accomplish in Drupal 8. And then once we have defined the goals, we should consider launching an initiative for this. If we feel that's a good idea, I would go out and try and find an initiative owner as well, over the next, I don't know, in the next six months. Usability. This one is an interesting one for me because it's somewhat covered by a gate, although, you know, that, you know, obviously, at least to me, that wouldn't be enough. I think there's much more we can do. We've done some formal usability testing, so I think we have a sense of, you know, areas where we can improve things. But there is a lot there, right? So where do we focus? What would it mean to define an initiative around usability? So I think we need to come up with a more narrow set of goals. Like, are we going to go after the editorial workflow experience or are we going to do something completely different? So again, we'd love to get some input from people in the audience and from people, you know, not at DrupalCon, see if we can formulate an initiative around usability. Mobile support. This one is interesting because it's partially covered by the HTML5 initiative, which will make it easier to build mobile websites. It's also covered by the design initiative, because one of the objectives of the design initiative is to make, you know, to make the new team, which we like to add to Drupal 8, mobile friendly. And it's also partially covered by the web services initiative because that will actually enable us to build native applications for iOS or Android and other devices. So in a way, we're doing a lot of things to make, you know, mobile a top priority, but I think there's always more we can do, especially given how important mobile is. I think we should think about maybe converting all of the existing teams in Drupal 8 to be mobile friendly. I think we should consider adopting responsive design in all of our teams. There's things we can do around scaling of images if we serve them to mobile devices. Should we build a native application for Drupal? You know, that could be cool. And so again, I think we need to define what it is that the next steps will be, see if there's one or more initiatives that come out of this. Wizzywick, you know, we obviously aren't doing much about this, but it's something that people have been asking for. I know Sun has some ideas. I know Quick Sketch has some ideas. So I think we should get together, talk about them, see if we can, you know, have a Wizzywick editor in core. So, better APIs. I think a lot of developers feel this pain where we need to make Drupal easier to use. So do we need to, you know, look for ways to simplify Drupal to improve the consistency of Drupal? Should we look for ways to adopt some of the modern design patterns in engineering? I think the answer is yes to all of these questions. And we're actually doing a lot of that too, the web services API, and to some extent also through the configuration management stuff, but there might be more to do. So let's work on that. Configuration management, we happen to have an initiative for that, so it's green. I think, in short, I would say this initiative needs some more people to help. I think there's good ideas, there's progress, but we need more people to get involved. Content import, export, again, partially covered by some of the existing initiatives, but again, more that can be done. So let's see if we can define goals. Let's see if we can find champions to run with this and, you know, make them official initiative owners. And then finally, content staging, which obviously is a big deal for many. I think this one will actually be enabled by the configuration management initiative. So it's a little bit blocked on that. So the way I like to think about it is that we don't actually start anything here unless we've made enough progress with the configuration management initiative. So what I want to do with these scorecards, I think they're quite handy. So I would like to maybe move them online. Have a place on D.O. or elsewhere where we can basically track them and update them along the way. Maybe my next keynote, I'll quickly run over them again, see what progress we've made. But I think it's a good way for us to know what's going on, what progress has been made. I think if we do all of these things, you know, Drupal 8 will obviously be a great release which satisfies the needs of many of us. Two quick caveats, I would say, which is, I mean, there's a lot of other things which came out of the survey. Like views like stuff in core, better separation between products and framework, you know, all of these things which didn't bubble up to the top nine. That doesn't mean we can't work on them, right? It's still okay for you to work on whatever you're passionate about. I think Drupal is built on passion. So find the things that you're most passionate about. However, if you wanna inject yourself straight through the middle of the community, make sure to work on things that matter. Make sure to inject yourself in the critical pet because that will give you a lot of visibility, a lot of exposure. And so if you care about those things, work on these nine things. And also I think in our conversations, let's not forget about these nine things because we tend to talk about specifics. You know, we tend to talk sometimes about issues which are not in the top nine, which is great and we should continue to do so. But let's make sure we don't spin our wheels talking just about these things and then forget about other big topics. So essentially to wrap up this keynote, and I think we have a huge opportunity ahead of us. I think, again, we're uniquely positioned to basically change our industry, to change the way people build websites, to change the way people manage dozens or hundreds of websites. And I think it also came out of the survey results. So as we go after this, let's make sure we truly understand the competition that we're not blindsided by one or two. And I think the way we go after this is by making sure Drupal continues to be the best CMS out there to make it really, really strong. And to do that, you know, let's focus on Drupal 8. Let's make Drupal 8 a really, really great release at the same time. Let's continue to invest and make progress on these contributory modules like the media module and others. Let's really focus on ease of use and also let's start to embrace ugly words like promotion and marketing. Doesn't mean you have to do it, but at least let other people do it. Let the Drupal Association do it. Let's get more of these people in our community because at the end of the day, all they want to do is carry out all of the great work we've done and help other people get into Drupal by doing so. And so with that, I'd like to say thank you. There should be some time for questions and answers, I believe. Hi, Dries. I've been told we only have time for two questions from our Twitter stream. I've talked too much. One of the first questions that came up was, are there any major sites running Drupal 7 at the moment? It's a good question. Well, there is quite a few of them, but I'm trying to come up with a good example. Examiner.com would be a huge website, actually. Sorry, I couldn't hear that. Right. How is it for representatives? So there's plenty. We should make a list. I'm sorry, I'm blanking on good examples. And then if I aggregate a few questions, you mentioned a lot about the need for marketing and the marketing-driven future and where you wanna go. But is the community able to do that? Or do you really need the Drupal Association to take control? Does it need a top-down approach to create simplicity from our growing complexity? Right. So I think it would be helpful if the Drupal Association, I mean, we need to talk about that as a Drupal Association, but I think it would be very helpful if the Drupal Association would take a lead in that. But then work with everyone basically that wanna participate in sort of carrying out what that means to do marketing. And it means a lot of different things, right? So we need a lot of people to help. But I think when it comes to marketing, I think there needs to be some ownership, whether it's in the Drupal Association or whether it's with somebody outside of the Drupal Association or a small team outside of the Drupal Association. But I think it would be helpful if there was some consistency in how we talk about Drupal, how we promote Drupal, and if there was a vision behind that as well. So I think it would be helpful if the Drupal Association would take this on. So, yeah. All right. No more questions. Tony told you to do two. All right. So I'll be around until I'll reach. If you have questions, you know, don't hesitate to ask. Thank you. Thanks, Chris.