 Good morning! Excited to be here with you this week. This is such a special time for us to unite as a community and to level up our skills and to spend time contributing back to the project. And what I love most about this week is that we created this special experience together. I am deeply grateful for the Drupal Association staff and their commitment to wake up every day ready to serve you in our mission. And our mission is to unite the community to help you build and promote the software. And they work really hard to hear and understand your needs and to work with you to build solutions that move the project forward. And you know, we have achieved a lot together this year. And I'd like to just highlight some of those. Together we created industry pages on Drupal.org. And these are great ways to showcase all the amazing work that you've done and how you've been helping your customers and your patients and digital citizens out there with amazing solutions. And so now we have been able to hear the needs of the business community and start creating content that you can use, excuse me, that you can use to sell Drupal. And we also heard the need from last year's community keynote, Enzo, who said that's really important that we start offering localized content on Drupal.org. And so we created these geo-targeted pages and got case studies from community members that submitted them, and we have included them on each of these pages. So for example, if you are in Europe and you are looking for more information about Drupal and government, you can go to the page and it will serve up the case study of the city of London, which has really great information and really highlights the best of what Drupal can do for digital citizens. And then together we also improved the contribution experience by opening the floodgates with project application process, and we heard the pain and frustration of having projects created but not ready to be shared with the world. And so we worked with the security team and the technical working group, and we were able to solve this problem together. And what's great about it is we increased project creation by 58%. That's significant. That helps the project, and let's face it, it feels a lot better for those that spend the time to contribute back to the project. And of course we spend a lot of time together creating the special week. And so I want to thank all the volunteers who put in hours and hours of their time creating the program and special events that make this week so rich and rewarding. So if you have volunteered to help create DrupalCon, will you please stand up? Come on. Thank you. We could not do this without you. The European community is vibrant and passionate. You are very important to the Drupal project. Just in Dries' blog post you can see that you are responsible for 44% of contribution last year. That is a really big deal, and we know that DrupalCon is one of the many ways that help you come together and contribute in such a big way. We also know that DrupalCon is not meeting all of your needs, and it's also not at a price point, it's not affordable enough for everyone to come who wants to come and be part of this magical week. And so you might have read my very, very long blog series, or you might have heard that we are starting to look for a new model so that we can make DrupalCon better for you and more affordable as well. And we are working with the community to find what that model is, and I know that it is going to result in a better path forward. And what I'm excited about is I know this model will be able to be applied to other parts of the world that are not getting DrupalCon today. And all of this is very exciting. And so please know this is not the last DrupalCon. There will be many more in our future. We're just going to take a pause so that we can rethink the best way forward by working with the community next year. And so we are already starting to work with the community on ideas, and we started that over the last couple of weeks in forums and at the community summit yesterday, and we'll continue to do that this week. And what is wonderful is that there are many ideas already surfacing, and that is very encouraging. And to make a decision, we're going to need a process, a process that works for the Drupal Association as well as for the European community. And I have asked these eight volunteers from Europe who have a lot of experience in running events to advise me so that I come up with the best process that is clear and transparent and works for all of us. And we're going to be working on that this week, and we'll be putting that out to the community shortly after DrupalCon, because what we want to do is make a decision this winter of where or how we're going to do DrupalCon in 2019. So stay tuned. There's going to be lots of really, really exciting things coming. You'll start seeing the ideas, we'll make it very transparent. I'm very encouraged and excited about this. So again, if you want to participate in the discussions, we do have some birds of a feather. We want to do a lot to support camps next year while we're doing our rethink, and we will have a bof so I can hear what your needs are. So please come to that if you have anything you want to express, and we will work really hard to do that next year. And then there's the other bof that we can talk about the future of DrupalCon Europe there as well. So one of the reasons this week is so special is because our local hosts have put in so much time and energy. They held a full day of programming yesterday, trainings and summits, and it was so well run. And I couldn't believe how packed the rooms were. They really filled a need. And I'm very grateful for what the Austrian community has done. And they have so much more for you. And I'd like to invite them onto the stage so that they can tell you about it. Hello, fellow Drupal kings and queens. The Austrian community is more than it seems. When writing this rhyme, we could only guess if our Monday events will become a success. Invited on stage, five minutes to complete. Okay, Megan, we accept the dirty deed. All right. The party tonight will be a ball and we expect you to join it all. There's DJs and live acts and all this stuff and swag bags so heavy you can't carry enough. Champs opening tonight will be a blast. So get your blinky bow tie on fast. No dress code required, but there'll be a wall sprint. For the issue, Tamula, we won't give you no hint. Oi, da. I kind of broke that. Broken? Sorry. And she's broken. But reaching the venue is really easy. There's food places around and it won't get cheesy. For more insider tips and no infinite loop, come over to our booth with a big fat... Okay, well, anyhow, they're amazing. And we're working on the slides really fast. And we're just going to move into the housekeeping. Has everyone access to Wi-Fi? Yeah, anyone need to know how to find Wi-Fi? I didn't think so. So we're going to skip that slide when it comes up. Let's see. What else? Does anyone know what the social media handles are? Who can tell me? Hashtag oida? No. I'll just keep going because I've memorized the slides. Okay, after Dries's keynote, we are going to stay here for a group photo. No, we're not staying here. We're going to go out the door to the left in the mall. That's where the photo is going to be. Okay, we're going to skip over Wi-Fi. I think you've already figured this out. Here are other social media handles. No hashtag oida. So sorry. And of course, we all need coffee. We got up pretty early this morning. And so we have free coffee in the exhibit hall this morning. And then there's also paid coffee available the rest of the day. And for lunch, we have a two-hour lunch break that allows you to decide if you want to go to a session or eat. So they'll be going simultaneously. And just a few good points is vegetarian is in the regular buffet line. But if you order a special meal, you have a special table to go to. And it's in the back wall. You can see the map. Want to keep DrupalCon a very welcoming place for all of us. And so please make sure you're mindful of the code of conduct. If you do run into a situation and you want to talk to someone, we have the community working group members, Rachel Lawson and Adam Hill here. And this is how you contact them. Or you can just submit an online report. And we have lots of activities happening tonight, starting with the opening reception. So please meet us in the exhibit hall where we can kick this off. And of course, the big event of the night is the ball. Please make sure you come. They have put so much energy into this. It's going to be a very special evening. And then plan for women in Drupal so we can celebrate diversity tomorrow night. And of course, Thursday would not be complete without trivia night. So I hope you can join us there. Friday, well, actually all week are contribution sprints. Such an important part of this Drupal con. And it will conclude with the sprint day on Friday. So please, if you are new to contributing, come to the First Time Sprinter Workshop. And we also have general sprints and mentored course sprints all day. We do have one session change. So Tuesday from 12 to 1,300, 1 o'clock. And Schubert 1 to 2, the PHP session, will now be breakthrough large-scale Drupal projects with Behat. And as I mentioned, we have Birds of a Feather. If you are looking for the boards to know what we were talking about and which room and when, look for that board at the top of the escalator on level one. And please, please, please, after your session, fill out the evaluation form. It is really helpful for our speakers to get feedback. They put a lot of time into coming up with great sessions for you. And they want to do the best job possible. So please take the time to fill out the forms. They would really appreciate it. And in our exhibit hall, in the program guide, you might see the map look a little different. I want to show you the updated map, because FFW and SiteGround are just in a slightly different place than what we originally thought. And we want to make sure you can find them. All right. So big thank you to all of the sponsors who have helped us make this event special as well as affordable. I don't know if you read my blog post, but all the numbers are there. And we can't do this without sponsors. They help subsidize all the costs for the venue, the Wi-Fi, the food, the catering. But more importantly, they come and have great information to share with you. They can teach you about training and how to find a job at one of their agencies. So please, be sure to go in the exhibit hall to check them out. And I also want to thank our supporting partners. They are the ones who are coming, like crowdsourcing their funds, so we can pay for Drupal.org, the infrastructure, the maintenance, the new improvements to the page. And so raise your hand if you use Drupal.org. That's right, all of you. So let's thank them. We have our signature supporters and premium supporters and classic supporters that are from digital agencies as well as hosting companies and technology companies, too, that integrate with Drupal. They all want to give back. And they know it's not about leads. It's about supporting our infrastructure that we need to keep building the software. And so with that, I'd like to invite our sponsor of the day, Pantheon, to come to the stage. Please welcome David Needham and Tessa Creasel. Welcome to DrupalCon Vienna. Woo! Drupal really wouldn't be what it is today without the community and contributions from people just like you. So before we bring in the person that made Drupal possible, let's get to know the community behind it, all of you. So we're going to try something a little different. You might have seen it kind of leaked on the screen a little bit ago, but we're going to do a live poll. So we're going to ask a few questions to help you get to know the community here at DrupalCon a little bit better. We're going to show some questions up on the screen and just pull out your phone or your computer. Type in, as you answer, it'll show up live on the screen, and then we'll be able to talk about that. So if you haven't done so already, and I think our slide's up correctly yet, there we go. Join us at Slido.com, hashtag DC Vienna. First question, we really want to know where all of you are from. So one of the things I love about DrupalCon is I get to experience other cultures. I get to come overseas. I get to meet people that I do code with all the time online. And it's amazing for me to, you have that experience of contributing code and talking to people on Drupal.org all the time. And then you see them, and you meet them in person. And they're not always the people that you expect. And so I appreciate the experience of getting to come to DrupalCon, hang out with my friends, and meet new people. We see the results. They're popping in. Europe is winning by a landslide, obviously. If what? New Zealand. We're going to do a call out to New Zealand. It looks like 493, 499 people. Oh, 506. 506. Yay. We're going to move on to the next question. What is your favorite thing about DrupalCon? So for me, actually, Tessa, let me ask you, what is your favorite thing about DrupalCon? So my favorite thing about DrupalCon is getting to meet new people and figuring out what they do with Drupal. Yeah, so for me, I love the sessions. I love being able to go to sessions and hear from people, see things that they're really passionate about. That gets me excited. But like I mentioned earlier, the community, getting to meet people that I only see at DrupalCon every year is really exciting for me. It's a big reason why I come here. I'm not going to lie. I don't think we expected to see beer as a winner. Buy a landslide. All right, we're going to go to the next one. As fun as this one is. So who introduced you to Drupal? David, who introduced you to Drupal? So when I was still at university, I had a college professor, Stephen Murrell, who taught me all about Drupal. So we had the class. It was a final project. He told everyone that you could pick whatever CMS you want. And literally, everyone else in the class picked WordPress, which is OK. But he encouraged me. He helped me to learn Drupal. He helped me to go to my first camp and give my first talk. So Mr. Stephen Murrell is the person who introduced me to Drupal. How about you, Tessa? So I actually started my open source development days in Joomla. Don't shame me. And I was asked to work on a Drupal 4.8 project. I did it. I finished it. But I vowed to never touch Drupal again. And now today, I actually really love Drupal. And it's awesome, like, detailed functionality. All right. So we are from Pantheon. My name is Tessa. I'm an agency and community engineer at Pantheon, which means I get to help awesome developers learn how to be successful on our platform. I'm personally from Minnesota and the United States. If you want to find me online, Tessa K22. Yeah, and my name is David Needham. I'm the agency and community training manager at Pantheon. One of the things I really love about Pantheon and about our team, specifically the training team, is that our job is to help developers be successful on Pantheon, to use our developer tools and to really become familiar with both Drupal and WordPress, and to feel really good about making lots of money, building websites for their customers using Pantheon. So that's why we're here. But so there's this photo of the first time I got to meet Dries. And this was at DrupalCon DC. And this was a really important time for me as a new person to the Drupal community, because I was still in school at the time. I was trying to figure out what I wanted to do with my life, and I wasn't really sure. And I was doing a little bit of Drupal, and I got to meet Dries. And it was a big deal for me to be able to shake his hand and get this picture. And it meant a lot to me. I really appreciated that. So in seeing David's photo, I realized that everyone probably has a Drupal story. Maybe you've met Dries, and he was an inspiration to you. Maybe you've had someone else that has introduced you to Drupal. And we want to hear about it. So we actually created an Instagram account, the account's DrupalCommunityLove. Feel free to follow it. Tell us your story. Share your photos. And be sure to use the hashtag DrupalCommunity. And do that throughout all of DrupalCon Vienna. And we look forward to seeing your submissions. And not just DrupalCon Vienna, because the hashtag will be around forever. So feel free to post photos from previous DrupalCons or other events where you've really felt the love of the DrupalCommunity. And continue using it, too. I mean, Instagram will probably be there forever, right? All right, so without further ado, it's our pleasure to introduce you to the Drupal Project Lead, Dries. Hey, everyone. Let me see which clicker to use. For who is this the first time they're attending DrupalCon? Maybe raise your hand. All right, I have a lot of people. So in good tradition, I'm gonna do the Dries note. It's also called the State of Drupal. And so I'm gonna give you an update on what's happening in the world of Drupal. But maybe, unlike at other conferences, if you're new to Drupal, if you're looking at evaluating Drupal, don't be afraid of the Dries note either, because a lot of our competitors they go like rah, rah, rah. Here's all the great things in Drupal. And then never talk about the things that need to be improved upon. So not only am I gonna talk about some of the great things, but I will also talk about some of the things that I think we need to do better at. I think it's important for us to talk about it. So specifically, I wanted to show you that Drupal is growing and that Drupal is actually very healthy, but also that we're changing. There are things that are changing around us, inside and outside of Drupal. And some of these changes, they lead to questions, maybe sometimes to concerns, maybe sometimes even to frustration. So I also wanna talk about that today and propose some path forwards as well. So that's at a high level, some of the things I would like to cover. But let's start with how Drupal is growing. So there's a lot of different ways we can measure growth, but one of the ways is to look at the activity or the engagement from the contributors on Drupal.org. The issue, activity, and so we see that compared to last year, there was 22% more issues fixed or closed on Drupal.org and that spans both core and conchip. So that's a pretty healthy increase in one year. Similarly, we see that there was a pretty big increase in the number of individual contributors on Drupal.org, again, across both core and conchip. Same thing is true for organizations. The number of organizations contributing increased by 26% across core and conchip. So all great things. As Megan mentioned in her opening statement, Europe is very important for Drupal. And one of the things that we learned from this analysis from looking at the code contributions on Drupal.org is that actually 45% or almost 45% of all of the code contributions come from Europe, which is a big deal, right? Obviously, there's a lot of other ways to contribute. People can organize sprints, they can write documentation, they can sponsor events, they can do mentoring. And these kinds of contributions are also critical to Drupal's success. Unfortunately, they're a little bit harder to measure and so it's harder to report on them and to show you how these things have gotten better. But one thing that we did measure is the number of people attending Drupal camps in Europe. And what you see is that the number of people or the number of people going through these events has also steadily increased year over year. And more recently, there was also a Drupal business survey done. ExoVe and Wonshu, they surveyed basically the Drupal agency owners or the managers or the C-level executives of all of the Drupal shops and they got about 240 people to answer the survey. And what the survey results show is that most of the Drupal businesses are actually doing quite well. Almost 50% of them said that they grew. Both their Drupal sales pipeline is growing as well as the deal sizes are growing. So what that suggests is that the ecosystem is recovering, is growing, and is doing pretty well. One of the questions in the same survey which I thought was really interesting is the question of which version of Drupal do you use? And so these business owners then answered that question and what you can see is that by 38% of the people that answered the survey said that they only use Drupal 8 right now. 25% use mostly Drupal 8 and some Drupal 7. And so what that suggests to me is that Drupal 8 has become the go-to version. Most new sites launching are on Drupal 8 right now which is really exciting. At the same time, it also suggests that the transition from Drupal 7 to Drupal 8 is still not complete. If the transition were complete, I would expect like 90% or something of all of the new Drupal sites to be on Drupal 8. So we have some work to do. It's also reflected in the adoption statistics, but things are trending the right direction. The ecosystem has also matured a lot. If we look at the number of stable modules on Drupal.org, you can see that the number went up from roughly 600 stable modules a year ago to over 1,400 modules today. So that's more than a 2x increase. In addition, there's about 4,000 modules which are currently in development. So what that suggests is that the ecosystem of modules and projects, themes and distributions are getting more and more ready as well. So really good. Specifically of interest is also that some of these infrastructure modules, if you will, these are big modules that a lot of websites use and maybe have other modules depend on it, that they also became ready in the last five months. And so that will also boost the acceleration of Drupal 8. Having said that, there's some more work to do. There's other modules that need to be finished or completed. And my ask is that you try and get involved this week. You can either crack open your code editor and start writing code and upgrading these modules where you can fund other developers, maintainers to upgrade their modules. There's no lack of people asking for funding to get these modules done. So please get involved. It's a way you can really help. Of course, it's not just about the contributed modules. There's about a million Drupal sites using Drupal 7. It's a large number. And a lot of these people have been waiting to migrate to Drupal 8. They haven't been able to do so yet because the migration path hasn't been ready. And so I'm happy to share that we've made a lot of good progress on that as well. There is about 12 critical migrate bugs that are remaining. But once we fix those, the migrate path should be ready. So we're getting really close to that as well. I've spent a lot of time traveling lately. I've been the last two months. I was in Australia, where I met with the Drupal community. And I spent several weeks in Europe before coming here. And then I was in America as well. And so in my travels, I get to speak to a lot of people. And it's very clear to me that a lot of people are excited about Drupal 8. And so when I was in Australia, I was talking to Kim Pepper from previous necks. And I was visibly excited about Drupal 8. And he couldn't stop talking about all of the great things in Drupal 8. And so I recorded a little video with Kim. Hi, I'm Kim Pepper from previous necks in Sydney, Australia. So Drupal 8 has been a game changer for us. We invested heavily with 20% time. And now we're really starting to see that payoff. So the new architecture really allows new features and enhancements to come into Drupal 8 relatively easily. As we're seeing with Drupal 8.4 coming out with content moderation, workflows, media, et cetera, all being added. And this is big for us because having them added into core means we know that they're going to be high quality and stable. The six monthly release cycle has also been a massive improvement for us because developers are now able to see that the changes that they want to make or the features they want to add that they're really passionate about could be in Drupal core within one or two release cycles. And I really think that's accelerating the contribution space. So previous necks is very proud to be part of Drupal 8.6. And we hope to continue contributing into the future. So that's Kim. Yeah. Previous necks has been a fantastic contributor. So thank you to them. But yeah, like Kim, a lot of people are excited about the six-month release cycle. It seems to be really, really working. And so happy to share that next week we have the next six-month release that will be 8.4, which we hope to release. I believe it's in one week and one day from today. So it's really, really, really close. And those releases are actually starting to accelerate. And if you look at the current version of Drupal, Drupal 8.3, we have a set of experimental modules. You can see them on the screen. And if you compare that with the state in 8.4, you see that a lot of these modules have made significant progress. Four of them will be stable. Several are moving to beta. And even the ones that are in alpha have made a lot of progress. It's just that their state didn't necessarily change. And so you can really see that that model really starts working. Yeah. So we're very hopeful that we have some more goodies coming out with 8.5 as well. And so yeah, that's really the synopsis of Drupal is growing. What I showed you is community engagement is increasing. We have more and more people contributing, more and more organizations contributing. The Drupal 8 ecosystem is maturing. More and more contribute modules ready. Infrastructure modules being ready. Upgrade path is almost ready. It seems like the Drupal 8 release became the de facto release. Many businesses are doing well. And the acceleration in Drupal 8 appears to be accelerating as well. So these are all the great things, right? A lot of momentum, at least from my point of view. Now Drupal is also changing. And I wanted to talk a little bit about that. First of all, I believe that the vendor landscape, the world around Drupal, is changing. And I think it's worth talking about that. Because it's changing in sort of multiple directions. And it can leave some people a little bit confused. Like, what does that mean for Drupal? And so I don't know if you know, but the CMS market, which is our market, obviously, is growing at about 11% overall. But then if you, which is maybe relatively slow, I'm not sure if it's slow. But if you look in that market, there's a segment of the market, which is the headless or decoupled CMSs. And that little segment, it's still relatively small sort of part, is growing incredibly fast. It's growing at over 500% year over year. At the same time, we see that the low end of the market, if you will, the single blogs or maybe the portfolio websites or the brochure websites are best served by software as a service tools today. It's a reality. And that's what most people use. And then on the complete other side of the spectrum, we have the enterprise. And what we see in the enterprise is that for them, content management is a component. It's a feature, but it now became part of a bigger thing. So they're starting to build these big suites, and they don't compete on capabilities in the CMS, but they tend to compete on capabilities on the marketing side of the house. And so there's interesting movements, which I think it's useful for us to talk a little bit about. In addition to that, it's not only the vendor landscape that's changing, but also the technology stack seems to be expanding. And again, from the business survey, the Drupal Business Survey, one of the questions that was asked is, other than Drupal, because these are all Drupal agencies, other than Drupal, what other technologies do you use? And the results are pretty remarkable, right? More than 50% of the Drupal agencies are using nodes. And almost, I don't know, you can see the numbers, but a lot of them are using a variety of modern JavaScript frameworks. So that is more proof that this headless or decoupled part of the CMS market is really changing and taking off. It's also proved that developers want to use JavaScript. And so these are some changes. Obviously, it doesn't help that maybe the Drupal 8 release took a long time and that the adoption cycle of Drupal is maybe longer than we all expected. So these market changes, these technology changes, some of the changes in Drupal, it's basically creating some uncertainty with many people in the community. People wondering, who is Drupal 4? Or people that wonder if Drupal is still for them. And so I'd like to talk a little bit about that today as well. So I'm going to start with who is Drupal 4. And so I've actually talked about this before. I've written about this on my blog. I've actually talked about this at Drupal Con Baltimore not too long ago. And I wanted to talk about it again because I think it's important and also because I feel that maybe it wasn't heard or understood. And I think getting aligned on who is Drupal 4 will help us focus. It allows us to say, we're not going to do this, but instead we're going to go and do that. And so let me try and explain you in a little bit more detail than I have in the past what I mean with Drupal is for ambitious digital experiences. So if I think about Drupal, I think one of the greatest things about Drupal is actually that it scales from small to large, that it can serve websites with very little reach or traffic, as well as websites with a lot of reach or traffic. Drupal can power a blog or a portfolio site. But on the other end of the spectrum, Drupal can also power these, let's say, multi-site platforms, the Johnson and Johnson's and advisors that have thousands of Drupal sites. And on aggregate, maybe they're serving billions of page views each month. These are complex infrastructures that have lots and lots of reach. But I actually don't think that reach is the best dimension to look at. I think it's much more interesting to look at richness versus reach. And so if we make it two-dimensional instead of one-dimensional, I think the picture becomes a little bit more clear. And so when I say richness, I mean flexibility or customization, these kinds of things. In a way, it's maybe complexity, too. So if you plot it in two dimensions, it starts to look like this in my mind, which is, I think it really starts to show that Drupal is for sites that have medium to high richness. And what you see is that some of these smaller sites fall out of that. I personally believe that those today are best served by the software as a service builders. And that Drupal is no longer for these simple websites, except maybe when people are starting to do Drupal as a service, which I know some people are doing, which is very exciting, by the way. And I would definitely encourage people to explore Drupal as a service. But I think this is the reality. And of course, it's a little bit of a simplification because two dimensions don't quite capture the complexity of Drupal and where Drupal does really well. I mean, you can see it on the screen, like you could say, well, with these small sites of a ginormous amount of traffic, well, then Drupal is uniquely qualified to scale that to serve billions of pages. And that's true. And so even in this two-dimensional view, you could see it's not as simple as two boxes. But if you don't start to add other dimensions into it, it starts to get complex really quick. And that's why I personally believe that the term ambitious digital experiences captures it quite well. What I also like about it is that it describes our community, not only the projects that we do, but also the fact that we as a community are pretty ambitious in my mind. And so some people have said that Drupal is now for the enterprise, or just for the enterprise. And when I think of the enterprise, I think of this piece, so to speak, on the graph. And I agree that Drupal is great for the enterprise. But I also believe that Drupal is more than just for the enterprise. I think there's a lot of sites that are outside of this white box that Drupal is uniquely qualified to deliver. An example could be a small company. Maybe it's a company in Vienna. Let's say that has rental properties. They have 50 rental units. Maybe they don't get a lot of traffic because they're in Vienna and they only have 50 properties to rent. But they could have a lot of complexity or richness because they need to integrate with an e-commerce platform. Maybe they want to integrate with a booking system. Maybe they want to integrate with a support system. And guess what? They want to do all of that with a budget of 50,000 euros or less. It's not enterprise. But I do believe that Drupal is uniquely qualified for these kinds of websites, which is why I personally take offense when people say Drupal is just for the enterprise. It's more than just for the enterprise. And just like this small company, there's a lot of other companies or organizations. Museums can often be very ambitious and do very cool things. Non-profits can really engage with their stakeholders in unique and different ways. That require, let's say, more complex integrations or startups. Small startups, they could have a big idea and they want to maybe use their website to do some pretty amazing things. Like cart.com is actually a great example of a startup using Drupal in sort of a big way. And so saying that Drupal is just for the enterprise, I don't think is right. And so where this is a little bit of a challenge sometimes is that I think the majority of the Drupal ecosystem is actually sort of in that box. And so for a variety of reasons, that part of our ecosystem has maybe felt a little bit left behind lately because of some of the things that are going on. And so that sums up a couple of the changes. And I'm going to talk about that more in a second. So far I've shown you that Drupal is growing, but that the market around is changing. The Drupal itself has changed a little bit. I tried to explain again who I believe Drupal is for, for ambitious digital experiences. And I've mentioned that quite a few people maybe feel left behind. And so in my travels, when I listen to people or when I read tweets and blogs and all of these things, I hear a lot of different reasons for why people may feel left behind. And you can see some of them on the screen. People think Drupal 8 is no longer for simple sites. People think Drupal 8 moves too fast. Maybe people struggle to learn object-oriented programming. Updates are expensive. So a lot of different things going on, which doesn't help. I wonder if the connection is bad. And so some of these reasons I think are important. But unfortunately, I don't think we're ever going to fix those. We're not going to undo object-oriented programming. It's just not going to happen. We're not going to slow down Drupal 8, especially now we have so much to do. So we want you to come on board. We want you to enroll in Drupal 8. But these are the things that you will have to fix. We want you to learn object-oriented programming. Some of these other reasons are also really important. And those we absolutely have to fix. These are the things that, as a community, we should fix so that these people that I highlighted, the majority of our ecosystem, so that they don't feel left behind. So I'm going to talk about those things next. And what I think we should do to make sure that these people feel hurt and listen to. There's sort of different ways to look at this. But I think two really important pieces of this is the companies building these kinds of websites, like the example that I gave. In my mind, they want more powerful site building tools. They don't want to write a lot of code necessarily. They don't necessarily want to install 20 or 30 modules to get one piece of functionality. And they want to have tools that are easy to use. And I think that's becoming increasingly important not just for those people, but also in the CMS selection process. One of the clear strengths is that IT is less and less involved in the CMS selection, but that the business site, the marketers, and these kinds are very involved with the CMS selection process. So creating these powerful tools and making them incredibly easy to use is actually really important for Drupal. And the second thing that I heard line and clear is that updates and maintenance of Drupal 8 specifically is hard. And lots of people are asking, let's make it easier. So let's talk about both of them. And I'll start with the site building tool. So we've actually taken quite a few steps here to make this better. We've invested in people and process primarily. And I'm going to talk a little bit about those. So on the people site, a while ago, we actually created a product management role on the core committer team, which allows us to look more sort of outside into Drupal, like what are the key features that are missing, using survey data and things like that. We've also appointed Roy as a core committer to the core committer team. And that's special because for the first time in the history of Drupal, we have a non-developer on the core committer team. Yeah. And equally important, I think we have a community, I think increasingly more people here in the audience are passionate about design and user experience. And we're finding ways to involve you in the design process. So we've made some process changes, too, actually. Not sure if you know, but in the past, we would often just build something and then commit it. And then afterwards, we would find like, oh, actually, maybe we shouldn't have built it this way or designed it to work this way. And so with this new process, and Roy and others, we've really taken an approach where we start with design and product management. We first validate the designs, and then we start implementing them and throughout the process, we do more testing, which is pretty exciting. And we also created several initiatives. Again, a while back, like media, layouts, and workflow that are targeted at these people, the side builders. And those initiatives are using this new process. And you haven't necessarily seen them yet because they're still in the development process. So these changes were made, and they're coming through the pipeline. And so I wanted to preview a couple of those things with you today. So the first one is a layout builder. And this is actually showing the new out-of-the-box team, which we implemented. And what we're going to do is create a layout for a page. And so you click on the Layout button here, and that allows you to add sections. And each section kind of its own layout. So here, we're going to just pick up one column layout. And then that gives you the opportunity to add a block to the layout. This is, by the way, using the Settings tray, which is another kind of project to help make Drupal easier to use. That is also getting closer to being ready. So we're showing a lot of different things here. But as you can see, once the block is selected, you actually get to see it as well. Like you actually get the image to show on the page, which is a really nice improvement. Here, we selected a two-column layout for the next section. So we're going to be adding two blocks as well. And then once these blocks have been added, we'll show you how you can actually move them around with just drag and drop. I think it's pretty cool. This is actually real, right? So this is actually working. We may have to stabilize it more. We may want to make some more UI tweaks. But as you can see, this could be pretty close to something that you can beta test. So I think it looks fantastic, too. So thanks to all the people. Could be a game changer. The next one I want to show you is Workspaces. So Workspaces, something that Pfizer actually invested in quite a bit. And so let's say you are a website for a TV show, like, I don't know, The Voice, right? And you have all of these people singing. And you don't know who's going to win. But you do, whenever somebody wins, you all of a sudden want to publish that on your website. So at Workspaces, as an example, what it allows you to do is to prepare different variants of the website for each of the potential winners. And that could include different articles, but also menu items and things like that. And then when the person that wins wins, you can publish the right version into production. That's one use case of Workspaces. But in general, it allows a lot of different people to work on different sections of the website to preview them and take them to an approval process and then publish them or deploy them to production. This is something that was maybe a little bit harder to do in the past. And with these things, you don't need to install all these modules and maybe write custom stuff. And it really became a lot easier to use with the Workspaces module. It builds up years of work, actually, on content moderation and making everything versionable and stuff like that. So again, a really cool new improvement that will enable not only content authors but site builders to be much more effective and efficient. And I think we're delivering it in a way that looks really good and appears to be really easy to use. So very exciting feature. All right, lastly, I want to show you the media library. Media, of course, ranks always super high in our surveys. And what this is showing you is basically sort of a media browser. It shows you all of the assets that you have. Could be images or videos or slides or documents. And it allows a content creator to pick an image and embed it in a post. I mean, it's really that simple, but it's something that we haven't had or haven't had in core. And so putting this thing in core will be very helpful, I think, for a lot of content creators. I don't know why the slides are so flickery, but I'm trying to stay still to see if it helps. I don't think it's helping, is it? Anyway, so that's some of the stuff that's coming out of the new process. So you haven't seen it yet. You can't use it yet. It's not ready, but it's getting closer and closer to being ready. Now, I like the thing that the things I've just showed you are a significant step forward, right? I think you each step forward in terms of usability. But at the same time, I think, you know, let's face it. Like the bar is set pretty high nowadays. Even if you think about simple things like maybe uploading multiple images, if you think about how Facebook does it, you can literally drag a whole bunch of images. And while the images are uploading, you can start editing the caption and editing the title of the album. I mean, just all sort of magically happens. And for better or worse, Facebook is used by billions of people. And it's really setting the bar of how things should work. And the reason that organizations like Facebook and others can do that is because not just the people in the process, but also because of the tools that they have, right? And the reality today is that really good user experience is often built with modern JavaScript. The other reality, as we've seen from the survey results, is that really good user, you know, the developers actually want to use modern JavaScript as well. And so I want to talk about that next and make several recommendations. My first recommendation that I have is not necessarily new. But because headless and decoupled is taking the world by storm, I actually think we should find ways to invest more in that. And the desired outcome is that people can build headless or decoupled applications with their JavaScript framework or JavaScript libraries of choice. In addition to keeping twig as well, right? It's about giving people options, different ways of doing this. And this is what we've been doing around the API first initiative. Now, my second recommendation is actually to consider adding a JavaScript library or framework to core, not for building applications with Drupal or on top of Drupal, but for Drupal's own administrative UIs, right? Big difference. And it's important you understand the difference. I think that would be really useful to do because that would allow us to make Drupal easier to use, to provide a better user experience. Like, think about some of the user interfaces that we have around views or the field's UI. We really can make those better, right? And making those kinds of things better really benefits from having JavaScript libraries. Secondly, it would help us attract more JavaScript expertise into Drupal, which I think is really strategic and important given where this, you know, how fast JavaScript is growing. And third, it would actually allow us to dog food some of our own APIs, our web service API. So there's a lot of good reasons. The main reason really is to give us the tools to make Drupal's own administrative UIs easier to use. Now, to some of you that may sound really daunting and scary. And so my third recommendation really is to start small. Like, we don't need to set out to redesign everything in Drupal. You know, what I'm proposing is we pick one or we pick maybe two user interfaces, possibly new ones, so we don't have to break backwards compatibility if we don't want to, and build those with a new framework. You know, maybe the new layout builder as an example. And C, you know, we can start small with one or two things. That gives us the opportunity to learn, you know. And if you don't like it, we can undo it. If in the process we say, you know what, maybe this JavaScript library would be better, we can test it and swap it. So it gives us some time to figure it out, but it gives us the ability to actually move forward and start learning, which I think is really, really important. So I'm not the best person to pick a JavaScript framework. And so what I'm proposing today is that we start a proposed initiative that we huddle, that we get together this week and after Drupal.com to start putting together a plan on how we can accomplish this. Once we like the plan, we can consider activating it at the right time, depending on all the other things we're juggling. But I like us to reconsider the notion of adding a JavaScript framework to core, because I do think it's really important actually I think it's so fundamental as maybe the move from table-based layouts to div-based layouts, or how people used to have two websites, one for mobile, m.n1, that was for the regular desktop. And now they have responsive websites. I think, I don't know, fast forward 10 years, and I could see a world where most user interfaces are no longer server-side rendered or static, but become increasingly more dynamic and client-side rendered. I really do believe this is a fundamental change in our industry, and I do believe there's a lot of data that is supporting that as well. And so I think it's important for the long-term longevity of the project, as well as for the immediate need for making parts of Drupal easier to use. All right. Does that sound like an idea? Yeah? All right. All right. So I want to move on to the second thing. Making updates easier, making maintenance easy. Talk to several people on my travels, and they say, we used to do Drupal, but then we switched to WordPress or to something else because it was really too expensive to just keep updating Drupal. And so we hear that quite a bit. And so, yeah, I think it's something that we should look at. And it's not a surprise, because with Drupal 8, we've got a lot of great things, but one of the things we decided to do is to have monthly core updates. In addition, we have ad hoc contributed module updates, and we also have six-month core updates. So we have all these updates happening all the time, and the result is people need to be constantly updating their sites. Plus, not only do we have more updates, we also have more and more tools, composer and Git, and we have all these third-party libraries that we need to check and keep an update as well. I feel like this is getting worse. Everybody feeling okay? I don't know what to do about it, though. Maybe I should stay here. I'm gonna try and stay here. All right, so it's very clear to me that what users really want is auto updates, because it addresses a lot of the concerns. It addresses the concerns of the upgrade process is too manual, it requires very expensive talent to keep updating Drupal every month, and frankly, it would be a security best practice too. If you think about what happened just a few weeks ago in the US, because somebody didn't upgrade open source components, it really damages the brands of, in this case, not Drupal, but if this were to happen with Drupal, it would really damage Drupal's brand, and so auto updates, I think, would be huge. I recognize it's not for everyone, and some people don't want it, and that's fine, but I would say most people clearly want it. Whenever we bring up this topic, there's all sorts of complaints and concerns about security, or maybe we need to add a lot more testing, because what if we break one of those sites, and there's a lot of concerns, but here's what I do know as well, is that the best organizations in the world have figured out how to do this. If you even look at Apple or Microsoft, I mean there's a lot of examples, they do auto upgrades, they do updates of an operating system, which I would think is a lot more complex than a Drupal site, right? And so if they can do it, we should be able to do it over time. And in many ways, we're evolving in the right direction, which is really exciting. We started with manual updates way back when, and then we had Drush that helps with updates, which I'm sure many here use. We added an update manager in Drupal 7, makes it a little bit easier to check updates at least, and in Drupal 8, we introduced Composer, as an example to help with the dependency management, and there's a lot of good reasons to use Composer. But if you actually look at the data, and we did this with the Drupal association, they looked at what are people actually using. What we see is that almost 60% of Drupal's users are still manually downloading modules from Ditto, right? So that suggests that while Drush and Composer are great, they're not universally adopted, and it leaves 60% of the people behind, or almost 60% of the people behind. And if you include Drupal 7 data, it's actually worse than these numbers. So there's a lot of reasons for this. We don't really promote Composer if you go to the update manager. We still encourage people to download Drupal versus maybe give Composer instructions. I mean, there's a long list of things we can do, but actually where I think we should go to is this notion of auto updates. And again, just like with the JavaScript framework, we don't have to get there in one step, right? I really think we can take this step by step. And so what I'd like to recommend or propose is that we start maybe simple between quotes and simple could be maybe we just do auto updates for security releases only, security patches only, and maybe for core only as a first step, and we can learn, we can experiment, we can test the infrastructure, we can see how it goes. And then once we've mastered that, maybe we expand it to core and contrib. And maybe once we did that, maybe we can do auto updates for all patch releases, not just security releases. And eventually we can get to maybe minor updates, right? So again, instead of trying to boil the ocean and trying to do everything at once, we can start simple. This one is hard, I think. I'm not saying it's gonna be easy because there's a lot to figure out. I'm not gonna talk about all of these things, but there's clearly a lot to figure out from the infrastructure side to, you know, Drupal stuff and, you know, and so what I would like to propose today again is that we have a proposed initiative to do auto updates and that we huddle, that we get together and that we start sketching out what it would take to do auto updates. Are you guys on board with that? Yeah? Sounds like a yes. I'm sure we'll debate it, but I'll take it as a yes for now. All right, so these are, I think the two biggest things we can do to make sure that a certain group of us don't feel left behind and I recommend that we start optimizing for that. I think if we do two of these two things, a lot of the complaints or frustrations or concerns that I've heard would disappear. I'm not saying it fixes everything, but I think these are two really important buckets and it would, I think it would make a lot of people feel like they would be able to come along instead of feeling left behind, which as I said is really important. I think we're lucky that we have a very large community of contributors, right? Because making this happen is not gonna be easy. Like we have to really organize ourselves and we're lucky that we have so many people contributing. At the same time, some of these things are really complex and they're also really time sensitive and there's a set of organizations in our community that tirelessly contributes on the hardest parts of Drupal. You know, really meaningfully code contributions to address some of these tough problems and so I wanted to recognize them because this is a set of problems like those, right? And so we need to find ways to support these kinds of organizations in the Drupal project. And one such organization is Commerce Guys. They've been, yeah, I bet they're here somewhere. But you know, Commerce Guys is a relatively small company that has a massive impact on Drupal. And so what I wanted to do is show you a little video that I recorded with them because I want you to see how they do it, why they do it and hopefully again get inspired by what the Commerce Guys are doing. So here's the video. No audio. In 2005, 2006, and I really kind of developed a reputation in the Drupal community for creating Uber cart with my co-maintenor and popularizing that as the e-commerce solution for Drupal 5 and Drupal 6. And then I founded Commerce Guys in 2009. I originally delivered services around Uber cart, but when we had to change our strategy, I ended up developing Drupal Commerce instead. Up until last year, I had partners in Commerce Guys in February 2016. I spun the business out and now I'm the owner, president and CEO of the company with my two partners, Matt and Moya. My name is Mike Laman. I'm a senior Drupal consultant for our commerce guys out of Southeast Wisconsin. There I'm co-maintenor of Drupal Commerce 2 and a bunch of other contrib. My name is Balan Givanovich and I'm a Drupal contributor from Serbia and I'm the lead developer of Drupal Commerce 2.x, which is our rewrite of Drupal Commerce for Drupal 8. So back in 2010, I was looking for ideas for my summer of code projects and since I was already maintaining this contrib module for Uber cart for Drupal 6, I figured would be great to learn Drupal 7 and write it for Uber cart for Drupal 7 and then I came across Ryan's blog post called arose by any other name which announced the creation of Drupal Commerce and I said that would be pretty amazing. So I created this plan and then unexpectedly he said, well, I could just spend for you. So that was the beginning of one very long friendship. E-commerce is difficult. There's a lot of use cases and every single site that I have helped implement we've overwritten parts of Drupal Commerce for a need and previously with Drupal 7, overriding parts was near impossible unless you copy, paste it an entire module set but the Drupal 8 architecture we're able to tell the core service container, actually we're gonna use our implementation logic. I think that what we are doing wouldn't be possible for a team of our size and with our level of resources anywhere else. The strength of Drupal is this like collaborative environment that we were a part of where we get to benefit from everybody's work and knowledge and experience and wisdom is really important to us to maintain like a pretty high level of contribution. So even from day one as the new company when we were just three people Boyan was still a full-time contributed module developer. So Matt and I did the work, the income, the revenue generation that allowed us to pay ourselves and keep Boyan fully dedicated to Drupal Commerce and then also ensure that Matt at least had that one day a week to continue to contribute to core as well. And just through some good sales work we were able to get contracts in place that continued to fund core development whether that was projects coming in through Blue Spark or Acro Media that were big Drupal 8 projects that funded Commerce 2.x work or even just some like heroes who just showed up like thank me, nothing Boston who literally just gave us money and said, we don't want anything from you. We just want you to use this to book more of Matt's time to Commerce 2.0. And so what happened was that, we've maintained this spot in the list of all Drupal companies contributing to Drupal because of our activity, despite being a fraction of their size. I think even right now we're hovering somewhere around 300 commits in the last 90 days and that's spread between our Commerce projects, core work and other contributed modules that are sort of dependencies out of our Tangential 2.0 Drupal Commerce. We can get a lot of return value by giving back because yes, we're technically competing for some projects but there's such a market share that we can all greatly benefit by sharing more information such as code, domain knowledge and different tutorials. So that's the Commerce guys. Well, a huge thanks to them because they have done a lot to make Drupal more powerful, not just Drupal Commerce but Drupal itself, more powerful and much more easier to use. And I mean, to me, this is a very compelling example. I know there's other examples but the idea that a relatively small company feel that they can accomplish more with Drupal 8.0 than they could accomplish with anything else out there is pretty powerful, especially if you think about what they're doing like building a commerce platform which is probably one of the most complex things to do. And not only that, but in the process of doing that they can actually meaningfully contribute to Drupal 8.0 as well. Not only do they give or get much, they also are giving much back to the project. And I think it's just an incredible example and I hope that they inspire all of you to contribute as well as to take from Drupal. So, to me that's a Drupal way. And so if you wanted to get involved more with Drupal, if you wanna contribute to Drupal, this is the week. I mean, you're in the right place at the right time to get involved. There's people that can help you. So I encourage you to enjoy your DrupalCon and come talk to any of us about getting involved. Thank you very much. I feel like I debucked the stage by the end of my talk. If I stayed there, it worked. Hey, Rachel. Hi. Good to see you. Good to see you. Yeah? When I sit down? Yeah. Okay. So, a couple of Q&As from the audience. Started with an Austrian themed one. Okay. Nice and easy to get in there to start with. Do you know how to prepare the schnipsel? I know, but I think it involves using a hammer and slamming on the chicken or whatever the beef or... I think we probably need somebody in the audience later to show you how to do it. Yeah, I'd love to actually. Didn't like the workout. Yeah, that'd be good actually. Okay, so moving on to some specific European things. What would a European Drupal camp need to do that would interest you to coming all the way from the U.S. or actually wherever you are. You travel so much. What would get you here? It's a good question. So the way I tend to organize my work, I guess, is optimizing for impact. And I think most people do this, like I wake up in the morning and I'm like, you know, what can I do that would optimize my impact on Drupal? And the challenge that I often have with camps because I get invitations often to come and keynote, typically to come and keynote their camp is that while I love doing those things, for me to be on stage and to deliver a message from the stage to the audience for maybe 200 or 500 people isn't always, and I mean this respectfully, isn't always the best or biggest impact for me. You know, if you think about the time it takes to get there and all of these things. And so, but I love doing that. But so one thing we can make that much more interesting for me is if we could, you know, actually to do what I do, I need to listen constantly to people. And so for me, the value wouldn't be, I understand that the value for the audience could be the keynote, but for me, the value would be to have maybe an organized listening session, you know, round tables where I can talk to the key influencers or key players in the community and in like a half a day or a day or you know, whatever timeframe we can get really deep on some topics and some of these things become really actionable and that kind of stuff. That would be very interesting to me and would be very compelling for me to travel and be at your camp and do a keynote as well, you know. So it sounds like you want to listen as much as speak and do keynotes. Yeah, I listen more than I speak. But yes, I'd love to, you know, if we can sort of organize listening sessions, I don't know what to call it. I think that would be very valuable to me and I'm sure it would be valuable to the other people attending too because it would allow me to interact in a different way versus just the keynote. Like we would have conversations, debates and move things forward that way, which, so I encourage you to do that. Okay, I'm wearing this lovely Drupal T-shirt, hashtag going on Twitter at the moment, people tweeting their favorite Drupal T-shirts. I'm wearing my DrupalCon London, London, yeah. T-shirt today, Croydon, yeah. And because it was where I first changed from being a Drupal consumer to being a member of the community and getting involved in volunteering, et cetera, and doing all sorts of things now. Can you think of a T-shirt that you own that's special to you and why? I have a lot of T-shirts. I keep them in like memory boxes and it's like half of our storage unit is full of Drupal T-shirts. So it's hard to pick one. But I do have all of my DrupalCon T-shirts. I've never missed a DrupalCon as an example. But you know, but I guess I'm gonna highlight my first ever Drupal T-shirt. I can give you a little bit of the backgrounds. And so this was 2004, I believe. And so at the time I was a student at the University in Ghent, I was doing my PhD and I had a presentation accepted at UPSLA, which I don't know if you know UPSLA, but it's in my field it was sort of the most important conference. And it's where they first presented object-oriented programming and things like that. So it was, anyway. But, and so I go to Vancouver where UPSLA was and some people in Vancouver, I think Boris Mann and James Walker, they said, hey, let's do a Drupal Meetup. And I was like, what, a Drupal Meetup? Because, I mean, you have to remember, like Drupal was sort of my site thing, right? I would do it at night on the weekends, I was very passionate about it, but it wasn't necessarily something that I talked to my friends about all that much. And so it's like sort of a basement thing. And for me it was like, wow, we're gonna have a meetup and talk about Drupal? That sounds pretty cool. And so they put together this event in 2004 in Vancouver and it's where I gave my very first Drupal presentation. I'd never given a presentation on Drupal. And yeah, and they made a T-shirt, just a Drupalicon logo, and I was like, wow. And so that's a very special T-shirt because for a variety of reasons, because one, a bunch of people actually flew out to Vancouver, which was even more surprising, like Neil Drum, and I think Zach Rosen, I think was there as well, and maybe Kieran. So a lot of sort of the old timers that went off and did great things for Drupal, they were there. And also, at that event, I mean, and when I say event, it was like one presentation in a bar and then we were sitting in a hotel room with eight of us drinking beers while coding. So we had so much fun. We said, wow, this is really cool. We had so much fun that we decided that we would keep doing this. And so I went back home in Belgium and that's when I said, you know, we're gonna do a Drupalcon. We're gonna sort of raise the bar and organize a real Drupalcon, and that's how Drupalcon was born. And so this first T-shirt, I still have it. I don't think it fits me anymore. It's very skinny, Dries. It was very important because it was how Drupalcon was born, how I actually started talking about Drupal and the first time a bunch of us got together in person and, yeah, it was a pretty big game-changing event. Yeah. Yeah. I'm afraid that we really haven't got any more time for questions because we were a bit behind. And I've got so many more to ask that have come in from the audience and now I've got all this time with you. I've got loads to ask as well, but I really need to hand off back to Rachel. Thank you very much. Thank you.