 Vieta de Brasa. Welcome to Prague. Everyone, my name is Holly Ross. I am the Executive Director of the Drupal Association, and I just remembered to say my name, so Donna doesn't have to yell at me anymore. Good job. Thanks, Donna. Thank you, everyone, so much for being here. We're just incredibly excited to be in Prague for another DrupalCon and to celebrate with you this year's theme from one to many. And I'm gonna advance some slides like this. There we go, the theme from one to many, which is incredibly appropriate for Drupal, right? One Drupal, so many people from so many places around the world building so many amazing opportunities and so many amazing websites. We build travel websites here in the Czech Republic, and we build journalism websites in the South America. We build film festival websites in Australia, and nonprofit websites in Ghana. We build association websites in Canada, and we build advocacy websites in India. Unless you think we are missing a continent, who could forget the website for the penguins in Antarctica? That's right. It is this diversity that is what makes Drupal so special, it's this community and everything we are that makes Drupal such a wonderful place to be and a wonderful tool to work with. The Drupal Association is what bridges this divide in the community, that's what we are here for. And we do this through our mission of fostering and supporting the Drupal project in the community and helping it all grow and thrive. We run the Drupal.org website, we help build community through community cultivation grants, Drupal cons, helping Drupal camps, global training days and more, and of course advocating for the project legally and helping to increase adoption around the globe. If you would like to join us, and we invite you to join us in helping make all of this happen and help Drupal flourish, this is our end of year membership drive. You can join us at association.drupal.org and become a member today. How many members do we have out there in the crowd? Thank you so much for your support. Well done. Thanks. All right, from one to many. We're here in Prague, which I think is also appropriate for Drupal. Drupal builds websites small and large. The Czech Republic hosts the largest castle in the world. Drupal, high tech, cutting edge technology. The Czech invented the word robot. True fact. And we have been known to drink a beer or two when you go out on the town here, just be aware that the people of the Czech Republic drink more beer per capita than any other place in the world. So they're gonna give you a run for your money. But even if you're not out and about the town, we have lots of things for you to do here at the con this week. We have Birds of a Feather sessions this year online. Yes. You can sign up for BOFs online. You can review the whole schedule and we do still have a few slots open. So if you wanna schedule one of those social sessions to connect with folks, go ahead and do that online. Also connect with folks locally or socially through social media. If you are tweeting today or you are posting photos to Instagram, whatever you're doing out on the social web, please use the hashtag DrupalCon. Paul Johnson will thank you later because we do love to collate all this stuff and look back at all the fun. You can also request a song for the morning music as we all come in using the hashtag DrupalConDJ. And this is the most important tag. Today is Drees Note. That's the tag for today's keynote. We want you to use that because when you tweet questions out with that hashtag, we have some folks who will be collating those questions and making sure that we get them answered by Drees later today. So Drees Note is your key for getting questions answered. Of course, it wouldn't be a DrupalCon without a big contribution sprint. So excited to have those. If you have been around and been sprinting for a long time, we have lots of different projects for you to get involved in. How many of you have never been to a sprint before? Anyone out there? A few of you, excellent. Oh good, lots of you have never been to a sprint before. Now is your chance to figure out how to get involved with the project and make contributions. We have some great things scheduled for Friday morning. Get involved with Core and Community Tools Workshop. They're gonna teach you everything that you need to know to get engaged with the project and start making your very first contributions. And if you wanna learn more about that, you can visit the sprint mentors who are just in front of the exhibit hall and they'll tell you what's involved in the program and help you get your computer set up so that you can arrive ready to go. I'm huge thanks to Kathy Thays and Andrea Soper and Jess XJM for always helping to make that program run. Yeah, they're amazing. And speaking of sprints, I did wanna point out that we have a new contrib sprint just announced called First Friday. So we all know that Drupal 8's coming out when it's ready. Can you laughter when it's ready? No, okay. We all know that Drupal 8's coming out but it won't be a successful release if we don't have the modules there to support it. So if you are a module owner, we invite you to please spend the first Friday helping get your module ready for Drupal 8. And right now when you do that and you start porting your modules, you're gonna be helping the core team fix their any API issues. So First Friday, new sprint. All right, finally, events here at Drupal CompROG. There's lots going on all the time. Just when you thought you couldn't take another step, someone's gonna find you in the hotel lobby and drag you out somewhere. These are just a few of the things that are going on. You can also still create your own events. So we invite you to do that up on the Khan website. So lots to do here at the Khan. And now of course I get to give you some really fun housekeeping announcements. So pro tips for the show. First, once again, here is the network and the wifi password. If you're having trouble connecting, it's probably because your neighbor has four things connected to the network right now. So please, one device per person if you can help it. Evaluate your sessions. This is the best way that you can help us make the Khans better and better. So when you finish your sessions, your speakers should have some instructions about how to do that on their slides. But you can always go to the session pages at any point during this week. Click the big button and you can tell us how that session went for you. I also wanna remind everyone that it's the community that's the hallmark of Drupal, right? It's the friendships that we make here and the mentoring and the support that we get from each other. We only have one community and we have to take care of it and that's why we have a code of conduct. So I wanna remind everyone about the code of conduct. Invite you to go review it. And also for anyone who has any issues, please report them as soon as possible. You can talk to myself or anyone on the association staff and we'd love to talk to you and help you solve any problems that you run into. All right, lastly, close to last pro tip, we have a group photo today. We're gonna get the great background of Prague behind us. We're gonna move outside. It'll be immediately following the keynote, which means as soon as we're done with the keynote, we're gonna ask you to get up and hustle your way out the doors. You can go through any of the doors in the auditorium here, but we're gonna want you to go that way. So my left out those doors down the central stairs through exit five and out to the plaza. If you can't remember all of that, that's okay. Jam has a megaphone, which is a little bit dangerous. That's right. Thanks Jam. Jam has a megaphone, so he'll be singing something on his way down the stairs. We also have human arrows. Yeah, so follow them out to the group photo. If you want to both take a group photo and have coffee, I encourage you to move quickly. All right, group photo today. Finally, just a huge round of thank yous. It takes a lot to put one of these on. The staff, the board, the volunteers do an amazing amount of work. You can see, nobody can read that, right? We have this on the site too, so please go check out our list of thank yous. There are so many people that are engaged in this process to make such a wonderful event come together, including our sponsors. Without them, we would not be able to put on such a great event at such a low cost to be able to bring all of us together. So it's their contributions and support of this show and the work that the DA does, it's really important for us. One thing that I do want to point out, in particular, are the Drupal Association supporting partners. These folks make a contribution above and beyond what they do to support the cons every year to help make sure that we can begin to fund a better Drupal.org. So these are the folks that have provided us additional funding and are really helping us to start to make the kinds of improvements that you want to see on the site. So thank you to our supporting partners and to our very first technology partners, folks from outside of Drupal itself who are really invested in making sure that this is a platform that works across the web. So thank you very much to all of those partners. And with that, oh, I keep pressing the wrong way. And with that, I would like to introduce to you a very special guest. Please welcome the Wunder Choir. That was awesome. I don't think I've ever been introduced like this. Makes me wonder if I should have brought like a rabbit costume or something. That was awesome. Thank you, that was very, very nice. Welcome everybody, welcome to DrupalCon. I lost track of how many DrupalCon we've had so far, but this is definitely gonna be the biggest one in Europe. And so that's obviously very, very exciting for us. So let's talk a little bit about Drupal. You know, why? You know, why are we here? And you know, why do we do what we do? You know, I was thinking about that the other day and I think it's worth stopping for a moment to talk about that. So effectively, what is our purpose as Drupal? Is it that we work? You know, we make money and we take care of our families? I think for a lot of us, that's true. But is there more? You know, is there more? And I think the answer is yes. I think there's a lot more to what we do. In fact, I believe we're changing the world. I think we are changing the world. And I for one, I wanna make a difference. I think we're an incredibly powerful movement that have been doing some incredible things all around the world. Like if you think about the change that we have enabled, you know, we've enabled so many others all around the world to do what they do, to better fulfill their mission. Whether it's helping others, whether it's, you know, helping the governments run better. There is so much that we do. And so we help, I think, I feel like we help individuals build a dream. You know, whether that dream is having your own Drupal shop, which I think is true for many of you, or whether that dream is doing a startup and bootstrapping an idea. You know, we help, you know, people realize these dreams. You know, we give them the tools to do so. And another thing that we do is we give small organizations a big voice. And that's a really important one for me. The web is getting more and more complex. You know, organizations do need to do more and more with their websites. And traditionally, the tools that people use to really, you know, bring the core of their business online or to do these things online have only been accessible to the large organizations. You know, and what we've done is we've democratized a lot of these tools and we've brought them to everyone. And now everybody in this room and everybody out there in the world, you know, they can use, you know, great technology. And, you know, so we give small organizations a big voice. But we also work a lot with large organizations and have their own problems. But, you know, even for them, we're doing a lot of things. You know, open source is definitely being embraced by the large organizations. And they also need to do more with less. And we give them the tools to do so. You know, we're leading some of the most exciting advances in technology. We're allowing organizations to build rich and engaging experiences. And basically build transformative experiences online. And that's a big deal. And also I feel what our community is about is that we admit no boundaries. You know, we look at HTML as one way to deliver content. We look at MySQL as only one database that we support that we don't limit ourselves to MySQL. Same thing with PHP. We don't necessarily limit ourselves to PHP. We've done more and more JavaScript. And so I've always felt, and I still feel that today, that we're about pushing boundaries and that Drupal is not just a technology stack, but it's an idea. You know, it's something, you know, that's way bigger than technology. And, you know, we'll do it again. You know, we've reinvented ourselves many times and we're gonna reinvent ourselves again. And that's why I wanted to talk a little bit about Drupal 8 because, you know, I do believe that Drupal 8 has the opportunity to basically erase all of these efforts, all of these things that I just mentioned to an even higher level. And so I wanted to talk a little bit about that. As you probably are well aware, Drupal 8 is a major evolution of Drupal. But it's very well aligned with those vision statements that I put up. And as we worked on Drupal 8, we made a plan for Drupal 8. And that plan is sort of the six initiatives that we put forward. I've talked about these quite a bit in the past, so I don't wanna talk about them too much in this keynote, but I do wanna quickly remind people of what they are. The first one is configuration management. For those that don't know configuration management, it's a very big deal for everyone that wants to better deploy Drupal sites. You wanna be able to push content from development environments to production environments. And we've re-architected how we do that in Drupal 8. Mobile, all the way back in 2011, we declared mobile as one of the biggest things that we wanted to do in Drupal. And we've really done so. We've spent a lot of time and energy in improving mobile features in Drupal. And so we've embraced responsive, we adopted HTML5, we even have a better toolbar to allow people to faster and easier navigate Drupal. Blocks, we've done a lot of blocks, work on blocks and layouts. I wish we would have done more in this area, but I do believe we have put the foundations in place. And this will help us adopt to important trends like personalization and targeting, which I talked about in Portland for those that watched that keynote. So a lot of important work there as well. Multilingual, especially in Europe, very important. But we've literally made hundreds of improvements to multilingual. It's hard to talk about what we did because there's so many different things. But massive improvements around multilingual. Views in core. Very big deal, views was the most popular contributed module. We've added it to core. As we move it into core, we made it even better and we started to integrate it in core itself. And it's important because views changes the way people will build websites, right? It really empowers individuals, small organizations and large organizations to really build websites faster. And then web services was the sixth initiative. And that's important because you want Drupal to integrate with third party systems, but also because you want people to build native apps on Drupal. So we built native support for web services. And so these are the six initiatives. We've done a ton of work on them the past six months since Portland. But what I really wanted to talk about here is some of the other features. Like these initiatives get a lot of attention, but there's a lot of other things we've done. And I just want to highlight a couple of those. All right, so the first one I wanted to talk about is the accessibility work. You know, some bugs in Drupal 7 that basically prevented screen readers to really deal with sort of visual stage changes. When a dialogue pops up, a modal, or other things happen, they couldn't always follow along. And so a lot of work has been done in Drupal 8 to make that better. And so I have a little video which I'll show you now which demonstrates how screen readers work and how it works in Drupal 8. Hello, I am Drupal 8 and I am now self-aware. Content, extend content button. Link, comp link, extend structure button. Link, block layout, list 10 items level two. Close overlay button. Visited link, quick edit, list three items. Quick edit field image button. Quick edit field body button. Editing entity node one, field body. So a very quick video, but it shows you some of the great things we've done we've added an API to core which allows us to control what these readers talk and how they can move around the page. And it's a big, big improvement. For many of you, it may not matter, but it matters to those that are visually impaired. And so I think it will help us a lot. Yeah. So the other thing we've done is, we've worked on schema.org integration and it's sort of a hidden gem. And it's something that I'm very passionate about as well. But for those that don't know schema.org, it's essentially a semantic markup to describe the content on your page. And here's a quick example of what you would do in HTML to describe and offer something that you're selling. So you basically have these properties like name and price when you kind of tag these elements, right? And then in this example, there's also like a rating, a four star rating or a five star rating, which is based on 25 user reviews. And even that element, you can sort of expand. And also make more semantic, so you can basically make that type aggregate rating and you can define the rating value and the best rating and how many ratings there were. And that's these kinds of things we've put in core as well. And that's exciting in the short term because it will provide better search engine optimization. So if you look at Google results, you can see that they're doing these rich results which helps people or helps websites to drive more traffic. And so in the case, I tried to look for like a blender omatic or whatever it was. Couldn't find one, but I find a peeler and you can see how Google renders it here. It shows you the rating, it shows you the price, but there's a lot of these kind of schemas, if you will. And so you have them for music and albums and so it lists the songs. So you also have that for recipes and then it's, you know, it gives you things like how long it takes to cook the recipe and all of these things. And that's exciting for everybody that cares about search engine optimization. But the long run, what's cool about that is that it will actually help us evolve the web and actually truly fulfill the potential of the web. And Tim Berners-Lee, the inventor of the web said that eventually we will evolve from the worldwide web to the giant global graph. So the potential that this brings is that the web will become a graph and that computers will start to work like the ones in Star Trek. We ask them a question and they give you the answer versus what we do today is which we, you know, we search, you know, 10 different ways and we extract the answer ourselves. And so I think it's a great cool thing that we added to Drupal Core and it will help us, you know, it will help position us for the future. And I have a little video from one of the founders of schema.org that we interviewed and it talks about what that means for Drupal and the world. So I'll play that now. It's only a minute or so. Many of the major sites like eBay and Yale and others have started using schema.org markup and they mark up all their web pages. But the thing that's most exciting to us is the web is not just about the top 10 or 15 or 20 websites. The thing that's exciting about the web is the variety, the richness, the hundreds of thousands of smaller websites which is what makes us the adoption of schema.org by Drupal. So exciting, so interesting. Hopefully we'll look back at the game from now and say, wow, schema.org is so big and then one of the major landmarks in that progress will be the adoption of schema.org by Drupal. It's pretty cool. Hopefully that will allow us to be at least a footnote in the history of the web. But I really think, again, that we can help sort of bring this technology to the masses. Lots of other great improvements. I want to highlight a couple of more. The new theme system is a very big deal as well and there's a lot of sessions about it here. But if you look at Drupal 7, this is what a template page looks like. You see we're printing variables. Some things need to be rendered, other things are already rendered. We're switching in and out of PHP which is okay for developers to do but for a lot of people it is troublesome in the sense that you can make mistakes and you get white screens but also from a security point of view, there can be risks there if you work with people that are not aware of sort of the Drupal security APIs. And so in Drupal 8, we redid all of that we using twig basically and it looks a little bit like this while it looks exactly like this and there's no more PHP which is a big deal for many designers. And there's no more rendering like everything is pre-rendered. And while we're at it, we also embraced HTML5 and we've updated our templates to HTML5. So a lot of work went into that and I'll talk a little bit more about that in a second as well. So great job to the twig theme and the HTML5 theme. We also added new fields to core and what I mean by that is the way CCK works there's different fields and so we added more fields to core which gives more power to people that wanna build content types and we've built them leveraging HTML5 as well. So what that means is, we added the daytime fields to core which was a contribute module and if you implement that now and you use it on a mobile phone it will actually use sort of the native date picker of the device. This is what it looks like on an iOS device but other phones do the same thing. Same thing with the telephone field which we added but you see if you declare a telephone field you get sort of the numeric keypads instead of the normal keyboard and then we also added the email fields and again, most devices will sort of give you the right keyboard in this case it will have the ad symbol so pretty great work, very empowering for a lot of people. The next thing which we did is we redesigned the administration pages and I'm gonna give an example of the content creation page. What it looked like in seven, some of the issues we saw and then what we did about it in Drupal 8. So there's a lot of small little things which we didn't like and it's actually been a lot of work to get all of these little things right and if you don't stop and think about it or show it in a video like this sometimes it gets lost and how much work we've done there. And we have a vision, there is a bunch of patches in the queue and we think we can even push it more. And there is many more features and I hope that I encourage everybody to kind of like start talking about these little gems, these little things that people like and start sharing those because there is a lot there. So what does all of that mean for you? What's the value for you? And there's a lot of different users in Drupal. There is the large organizations. There is the smaller organizations or the individuals. There is technical people and there is not technical people. And so I wanna look at a few personas. The first persona I wanna look at is a small site owner. And I talk to a lot of those and usually they say something like, it's hard to Drupal 7, it's really hard. And there's no wizarding. It's really hard to add images and I wanna change the main page from just being 10 nodes to something a little bit more powerful. And so for these users, we've actually done a lot. We've added with the week, a lot of the basic features that they want to be installed. We've added something like the tour module which gives them really context-sensitive help and sort of walks them through UIs. We've never done help this way. I think if we do this right and we add more tours, I think it will really help a lot of people. We changed the information architecture a little bit but mostly we've added a new toolbar and that toolbar allows people to navigate faster. You don't need to reload every page as you navigate, making it easier for people to discover things. We've done more drag and drop so it kinda starts to work more. Inline editing is something that a lot of these people care about. They just wanna get going and create content. And then we've even worked on the installer, made that easier. We've added great support for multilingual, for example in the installer, making it easier for people to install multilingual websites. And to me, all of these things are really important. I think if we wanna be more successful with these organizations, I think user experience is a big deal. And so all of these changes that we've made to the user experience are great. And then things like views even make it better because at the end of the day, most of these people don't necessarily wanna write codes. So if we can avoid them writing codes, we're gonna make them more successful. All right, another persona is a front-end developer. We've done a lot of work for these. There's been a lot of feedback from these people. They wanna use more modern techniques. They wanna have less craft to deal with. And generally find things too complicated. So a whole bunch of improvements gone into Drupal for these people as well. We've cleaned up a lot of the markup. There's been people dedicated to cleaning up markup and cleaning it up and cleaning it up. As mentioned, we've adopted HTML5, which a lot of them are very excited about. We've also introduced more like UI patterns, things like models and drop buttons and things like that that they can work with to quickly build a more rich and powerful user interfaces. We've added libraries like backbone and underscore. And more importantly, we've embraced this concept of not inventing everything ourselves. And so we've made everything responsive out of the box. And as I mentioned, we adopted Twig. So a lot of improvements for these people. Then there's also people like marketing managers. And I talked to a lot of these too. And their biggest concern is we will need to publish content to multiple channels in multiple languages. And they have a team of people and they need to be able to use Drupal to basically write all of the content. And so completely different challenges they want to integrate with third-party systems like a CRM system or a marketing animation system, these kinds of things. Lots of improvements for them. The web services support will allow people to build native apps. All of the multilingual improvements are a very big deal for these people and their teams. The REST support that we added to Drupal Core is also very important because they do want to do these integrations, as I mentioned. And schema.org will actually be very helpful for them as well. And it's an area where we are thought leaders because it will help them with the search engine optimization of their sites. Things like responsive preview. I believe are very important for these people. And all of the authoring experience improvements that we've made will really help them. I believe this is a big audience for us because there is a big shift happening from in terms of decision-making and who adopts or who chooses the CMS technology. It used to be the IT organization, increasingly more. It's the CMO, the chief marketing officer or the marketing organization. And making sure that we make improvements for these people is also really important. And I believe we've done that with Drupal 8. The last person I want to talk about is the engineering director. Also a technical person in typically larger organizations. They have kinds of different pain points. They usually complain about things like my team needs tribal knowledge about Drupal. It's hard to get Drupal talent. They struggle with content staging. They struggle with deployment of Drupal. Usually they have a lot of Drupal sites and they need to maintain all of these websites. So they definitely need to do more with less. And then of course security and scalability are also big concerns there. So things we've done for them is we've done configuration management. Configuration is stored in files, making deployment much easier. We started to adopt a lot of other libraries like Guzzle is only one example, but it's a good thing because it allows us to go faster and to leverage documentation from other projects and support more edge cases and things like that. We've adopted object-oriented codes, which specifically for large websites will be useful or large systems I should say. And Drupal is a large system. Makes it more maintainable. Also makes it easier to find talent. We've adopted symphony as a framework, which is great. We've done work around scalability. Like for example, Chix has done a lot of work in supporting no-SQL databases like Mongo, which will help us scale websites. Some of the blocks work that we've done will hopefully eventually lead to being able to support things like Edge site includes and technologies like that to scale up websites. And then for testability, we've done things like PHP units. So lots and lots of improvements. And so looking back, I think Drupal 8 will ship with lots and lots of great improvements for small users and for large users and for technical users and for non-technical users. I know it's one of the goals, at least for me, and I think we really fulfilled that goal. So generally speaking, I feel like we've really upped our game with Drupal 8. We've added so many great new features. And I feel like these features are sort of on the money, if you will. And if I think about what we needed to do to keep Drupal competitive, I feel like we really nailed it. And in fact, I wish we had done a little bit more. But I feel really good about sort of the direction that we've taken Drupal in. Of course, there's a lot of work left to be done. And we really need all of your help. There's a lot of you here. There's a lot of you in the world. And we need you to help us finish Drupal 8. And there's a lot of work left to be done. And instead of me telling you what we need to do, I figure I would ask the initiative leads, the six initiative leads to ask you to help. And so I have a little video of the six initiative leads telling you what they can help with, what you can help with. Here we go. Hi, I'm Gabor Hoji. I'm the multilingual initiative lead. A team of hundreds of people work on this initiative to make Drupal 8 a go-to platform for multilingual sites. Join to help make menu items and taxonomy terms multilingual, or contribute to us for all the improvements. Hi, I'm Chris Vandewater, the lead of the Box and Layouts initiative. I'm looking for people with panels and SQL development experience to help with the page render pipeline, asset management and user interface improvements. Hi, I'm Larry Garfield. I'm leading the web services initiative. We've been modernizing Drupal's routing and menu systems and could use some help from menu experts to finalize the improvements to the menu systems. We could also still use help from experienced model developers to help finish porting Drupal Core to launch the new APIs that we've built. Hi, I'm John Albin Lilligan. I'm the lead of the mobile initiative. We're looking for front-end developers to help with CSS and JavaScript. We've got a lot of juicy things to work on during the cleanup phase of Drupal 8. Hi, I'm Daniel Viena. I'm Tim Plunkett. I'm Damien Lee. And I'm XJM, and we're the views in Drupal Core initiative team. We could do with your help turning all the lists into customizable views. We also need contributors to do accessibility testing. And to write views documentation. Woo! Hi, I'm Greg Dunlap, and I'm the lead of the configuration management initiative. I'm looking for people to help test CMI in real-world situations using real-world workflows. So if you're great at breaking things, I'd love your help. All right, well, let's give it up for these people. They've done a tremendous work leading these initiatives and have given up a lot of their personal time, frankly, in nights and weekends to shepherd these things forward. And they need a lot of help, you know, and everybody can help, you know, whether it's as a front-end developer, a back-end developer, a writing documentation, or just testing. There's many ways to get involved, and at Drupal Core is a great way to get involved. As far as I'm concerned, you know, I think there's three, my three biggest to-dos, basically, are the following. One, we need to make Drupal 8 faster. We're well aware of that. We've purposely left a lot of backwards compatibility layers in place so we can trans, you know, move from one API to another. Once these API conversions are done, we're going to remove these layers, and we're going to be able to focus on performance, which we haven't really done yet to date. We know we have a lot of work in that area, and I feel pretty confident that we can get to great performance. We need to fix the developer experience. It's also been very clear. It's also something that we, you know, have been aware of. We need to simplify our APIs. We need to make some of our code less verbose. And so one of the things you want to do is you want to look at a module in Drupal 7, compare that with a module in Drupal 8, and sort of see where we can simplify things. And then a lot of that is also writing documentation, and, you know, getting people to learn about all of the changes in Drupal 8 and helping them to come along. And that's also something that we'll have to do a lot of work on. And the third thing is, you know, we need to simplify the upgrade path. Well, first of all, we need to fix the upgrade path. And then, you know, write documentation. And, you know, build tools like code or module that will help, you know, people upgrade their websites. So where are we in the release cycle? You know, we've been working on Drupal for a long time. In Portland, we basically moved sort of... We started doing alphas, and we shifted focus to cleaning up APIs. And we asked module developers to give us feedback on these APIs so we can, you know, make them better or easier, whatever is wrong with them. And basically, here we are today in Prague. We're basically going to keep doing the exact same thing. You know, we're going to keep working on cleaning up APIs, and we're going to keep encouraging people to help us make those APIs better. At some point, you know, I think at this stage it's going to be early next year. We're going to switch to focusing on release critical bugs and blockers. And that would be a good time for people to actually upgrade your modules or your themes. Like, if you start upgrading today, we will not guarantee that these modules won't break. So, but we do want you to help. But if you don't want to chase ahead, don't start upgrading today just yet because we are going to make more changes. And then, you know, we'll release Drupal 8 when it's ready when we fix the critical bugs. So basically, what that means is there is still time to get involved. There is still time to make things better. And, you know, I promise you will make the time to get it right. All right, I think we've always done that for Drupal and we will continue to do so. That's the point in releasing something that isn't ready. So, assuming we've done all of these things and we've released Drupal when it's ready, I think we, you know, we also have to up our game relative to the Drupal 8 launch. If you look back in history, Drupal 6, the way we launched Drupal 6 we basically wrote a blog post. I said, here it is. In Drupal 7, I think we created a landing page and we had 300 parties. It was way better. But we can do even better, right? And I think this is all about upping our game. So one of the first things we did is as a Drupal association, we hired Joe. Joe Saylor is a marketing person and one of the first things Joe did is he helped create kind of a new visual treatment for Drupal 8, something that we can use in launch materials to tie things together visually. And like, you know, quick examples is we could use it like this or we could even use it in things like the installer. What I like about it is that it keeps sort of the, you know, the Drupal icon there. Yet, it also provides a visual reference to Drupal 8. So just an idea of what it could be. More importantly, Joe has been working on a launch plan. And I'm not going to show you the entire launch plan, but the idea is that we're going to structure this and we're going to run this as a project and we're going to make materials like overview videos and presentations, but also training materials. Because a lot of you need to, you know, learn about all of the things that changed in Drupal 8. All the way to providing sales guidance to the Drupal shops. So you can, you know, sell Drupal 8 to your customers. Very important for us as a Drupal association is to engage with the community. And so we want to help. We want to get help and work together because Joe is only one person and it's definitely more work than one person can do. And so you want to provide assets so you can promote Drupal locally. We want to work with the local communities to translate materials into multiple languages and basically do an amazing job launching Drupal because I feel like we've worked so hard on Drupal 8. We've worked so hard with so many people for three years. And we need to tell the world all of the great things we've done and we should be proud of that and we should shout that out of the roofs. And I think it's a very unique opportunity because there is only so many Drupal launches, you know, every three or four years. And so it's really an opportunity to attract new people to Drupal and also to reset people's beliefs about Drupal. And I believe Drupal sometimes has a stigma, for example, around the ease of use. And I think we've done so much work around that that we can use a launch event to hopefully try and debunk some of these myths and to get people to know the real Drupal. And so I think if we do all of this, we launch, we build a great Drupal 8 and we launch it well. I think it gets us a step closer to, you know, fulfilling this vision. So to date, you know, more than 1,600 people actually contributed to Drupal 8. It's actually more, but these are the number of people that have a patch in Drupal 8, a patch that was accepted. So it's a very developer-y way of looking at this, but it is an incredible number. So if you look at Drupal 7 versus Drupal 8, when we release Drupal 7, just less than 1,000 people, I believe, contributed to Drupal 8 core already. You know, with Drupal 8 Alpha 3, we have almost more than double the number of people that contributed to Drupal 8. And that's kind of a remarkable number. You know, and I think that speaks a lot to sort of the work that we've been doing. And interestingly, if you look at the number of new contributors versus recurring contributors, you actually see that we have more new contributors, people that have never contributed to Drupal, than the total number of people that contributed to Drupal 7. So we've been very successful in bringing new people into core development. And we've also been very successful in increasing the number of recurring contributors. So some great numbers there. And it's hard, or it's impossible, to, you know, thank 1,600 people. But I do want to highlight a number of people, because I think they've gone sort of above and beyond in helping with Drupal 8. So I want to talk about a handful of people real quick. I'll try to go fast. But one of the persons that I want to, you know, thank is Kathy. She's been a key member of the multilingual team. She first, I believe, she first became involved with Drupal in 2012. So she hasn't been around, or actually she got involved, sorry, she got involved with core in 2012. She's been around longer, obviously. And one of the things she helped do is she helped organize the code sprints. And today she's, you know, running the code sprint at Prague. So if you haven't gone to a code sprint, please come to the code sprint. So thank you, Kathy, for all your amazing work. Alex, Alex is a remarkable story because he quit his full-time job and well-paying full-time job to dedicate all of his time to Drupal and his newborn son Jack as well. And, you know, Alex has just been amazing. I think he's been committing more than 50 patches a week on average. So he's been an absolute machine. And I think also today it's his birthday. Is that right? So happy birthday. But thank you, Alex, for, you know, surprising us all, I think, with your level of commitment. I want to thank Jesse Beach. You know, she's been all over the place. She's been helping with the authoring experience stuff. She's been a driving force around mobile and specifically the mobile toolbar. She's helped with the HTML Vive conversions. And she's been very passionate about the accessibility work. The things that I showed you, a lot of that, you know, would not have happened without Jesse. So she's done a whole bunch of awesome things. She only joined, you know, Drupal three and a half years ago. And I think it's a great example of how so many can join our project and quickly arise to, you know, to be a star. And so thank you, Jesse, for all the great work. Jeremy. You know, Jeremy is a supporter and we need a lot of supporters. And specifically, you know, the way we work in Drupal, every patch that anyone commits or contributes or, you know, submits for consideration, we apply it against our test environment and we run, you know, thousands of tests against it. And Jeremy is responsible for building out and maintaining that test infrastructure and basically enabling thousands of people to work on Drupal 8. So thank you, Jeremy. Shannon is also somebody that's, you know, relatively new to Drupal and Drupal 8. She kind of appeared out of the blue. And, you know, she's been really helping the initiative leads with project management and sort of helping them manage their projects and then also she started to train or project manage, I guess, other project managers, which has been very helpful in sort of running Drupal 8. So thank you, Shannon. Couple more. You know, Scott also only been around two and a half years in Drupal. Has been an incredible help, you know, relative to the theme system. Has really, you know, done a lot of work around the area of Twig. But also markup reviews and these kinds of things. And has also been a great mentor for many others. And so I think that's one of these things that we look for, people that get in help but then also start mentoring other people. So thank you, Scott. Couple more. Tim Plunkett, the machine, has been around for a while but he came out of the views world and kind of got involved with Drupal Core when we decided to move views into Core. And I think he's probably single-handedly responsible for 5% of all of the patches that are going into Drupal 8. And he has worked on all areas of Drupal, you know, from the plugin system to the configuration system to, you know, obviously views in Core. So awesome guy, buy him a beer. Thank you, Tim. Vijay, this is something that I really like. And I first actually met Vijay two years ago when I got, made a trip to India and I met him in India. And, you know, it's just a great example of somebody that, you know, really got involved with Drupal and he's been very helpful in supporting others as well as doing a lot of, like, conversions, conversions, rider conversions and helping to break down, you know, complex tasks into smaller tasks and helping other newer people get involved with Drupal. And I've actually run into him yesterday at the booth here and this is his first ever DrupalCon. So that's very exciting to have him here. So if you see him, give him a big thank you. Berdir, another, you know, workhorse, has been, you know, very involved with entities and field stuff. I've shown real leadership there and think it's a key differentiator for Drupal and sort of the things that we've done to the entity system and the field system, I think really positions us, you know, for the future. And so, you know, it's been a big guide for the Drupal world there. So thank you, Sasha or Berdir. Daniel also comes from views and cores, kind of the, you know, if I got it right, it's kind of the chief, you know, technical architect nowadays for views, another top Drupal aid contributor and rumored to be the only person that actually knows all of you that can keep it in his head. So thank you, you know, Daniel. We're almost there. We're almost there. Klausi, done tremendous work on the rest stuff and, you know, adding restful web services to core and, you know, did a lot of other things, but another great person that has done a ton of work and that you should totally buy a beer. So thanks, Klausi. Alex, you know, Alex for me is kind of an unsung hero in Drupal 8. He's always involved with the most difficult issues and, you know, he has a real skill in sort of breaking up complex things and, you know, pushing forward sensible approaches or solutions and is, you know, I look at him as sort of a momentum generator for the biggest and most difficult issues and he's done that for years now without ever complaining. So thank you, Alex, for being a champion. Ryan, another great example. Somebody completely new to Drupal. He dove in, you know, and he started helping with a new style guide for Drupal 8 which we're implementing. He also created some icons which we're using through Drupal Core and the amazing part that is he's working on some of the most difficult things, you know, getting thousands of us to agree on design and style. But, you know, he's only been around for a year and a half. It's a great example, again, of somebody, you know, the kind of people that we want to have. So thank you, Ryan. Lee. Lee has also been a great champion. He did a lot of work around the UX patterns, things like, you know, modal dialogues and drop buttons and things that I showed you. And he's also been involved in the Drupal module. So thank you, Lee, for all that work as well. So, of course, I can't thank everyone but I didn't want to, you know, I don't do it often. So I didn't want to take a little bit more time this time to sort of stop and highlight these people. You know, at the end of the day, you know, I'm really proud of all of you and I really mean that when I say it. We ask a lot from these people that I showed but from many other people that I didn't talk about. And it's easy for me to show slides. We're changing the world. And it's easy for me to show slides of all the things I wish we do and how we can democratize tools and how we can enable people to build their dreams. But it's these people. It's 1,600 people that helped on Drupal Core that did the actual work. So thank you for these people. And, you know, sometimes getting a release out isn't going in a straight line. You know, it's not always easy. But when it's not, I think, you know, I kind of realize that I'm probably the luckiest person in the sense that I get to work with so many passionate people. And, you know, I think that's one of the best things about what I do. And so with that, I want to, you know, basically give all of you a high five. If I can't do that in person, I want to do a virtual one. So I came up with this thing. I basically placed your hand there. And you give people a high five. Thank you all. And I think I'm going to answer some questions. Please. Thank you all. I've been sitting in the back with Paul Johnson. You guys have been tweeting questions like crazy at a whole bunch coming in. Fortunately, many of the questions were going in similar directions. I've got about five questions. Some areas that we're touching up on. Okay. To begin with something that's important, it also came up when D7 was about to be released. A very simple, very important question. Will we be able to nicely migrate from D7 to D8? Right. So, you know, migrations have always been a little harder in Drupal compared to other systems. That's not going to change. You know, we have a lot of big changes to Drupal 8. And I think we've made them for all the right reasons. But the result is that modules will have to be upgraded to use new APIs. That's going to be, I'll be honest about that, that's going to be, you know, a lot of work. But there's definitely a lot of things that people can do to make migration easier. Stick to the well-known modules. Stick to the best practices in Drupal, like don't hack core. And if you do all of these things, you know, it could be fairly easy, you know, to upgrade. But, you know, if you have custom modules, if you have custom themes, which, you know, most people have custom themes, these will have to be upgraded. So, I think that the thing, you know, we're committed to innovation. And, you know, I think we wanted to make sure Drupal is in a good spot, but we're also committed to making the migration path as easy as we can. And so, you know, we will do a lot of documentation, we will write tools and all of these things to help all of these people migrate. Okay, cool. Then there's this hot potato going around which probably has an interesting flavor. What can we, the Drupal community, learn from backdrop? Okay. So, I haven't spoken publicly yet about this. You know, there's a couple of things there, I guess, that I want to say. I don't want to be careful the way I say it as well. But, obviously, forks are a fundamental part of open source. It's a right and a freedom to fork. And a lot of forks are great in the sense that they allow and encourage collaboration. Press flow is a great example. That all forks are collaborative and that's fine too. You know, sometimes there is philosophical differences and then sometimes it's the best solution to split the community or to fork the community. I don't like that and I think what we should do is we should continue to listen and talk and see, you know, figure out what we can learn but also, you know, reach out to backdrop and see if there's ways that we can pull them back in. And I haven't spoken up about it yet because I think it is a bit of a process. It takes conversations and it takes time to work out what exactly is going on and usually it starts very emotional and over time, you know, I quit many things in life, I guess, emotions start to disappear and there is more room for rational thinking. And so that's why I've basically decided to like sit back and wait a little bit but I'm not afraid of the conversation and I hope that you know, I hope we can bring them back into our community. If that's not the case that, you know, at the end of the day that's fine too and may actually be better instead of having, you know, a disagreement, you know. If that's the case, the only thing I can hope for is that sort of that breakup is honorable and that we don't like start like you know, fighting and that kind of stuff. But there's a lot of things going on and I think we're already committed to a number of things like, you know, this switch to GitHub, you know, we've been talking about you know, possibly migrating to GitHub so as a Drupal association we're kind of studying right now, we're doing sort of an audit of what would be best and it's a little bit more complicated than it looks because our packaging tools do a lot of things. You know, they package the software and so these things, how do we get that in a Git world? The issue queues work a little bit different and aren't necessarily optimized for what we do and so we need to study GitHub and make a thoughtful decision there. You know, we're committed to improving the developer experience but at the end of the day I also believe we need to, you know, technology, we need to move forward. The web is changing rapidly and I don't want Drupal to be in a position where we can't compete if you will. So it's always a very difficult balance in terms of how hard do you want to push? You know, because you need to push hard enough to keep up with the pace of innovation but if you push too hard sometimes that's also not a good thing. It's difficult but I think we'll get through it and things will be fine. The last thing I want to say on that topic is that I feel very confident about Drupal 8. I really believe that it is the right it's going to be a great release which is not to say we can't learn anything from others. Your response actually hooks into the next question. A lot of people were asking since D8 is going to present so many new things you mentioned most of them in the presentation. Can we use Drupal 8 to enter new markets? Do we go beyond websites? Yeah, I think I definitely think Drupal 8 is a more powerful platform than Drupal 7 where it's more easy to be powerful if you will. And there's a lot of ways to answer that question but one way that I've thought about it is we've evolved a little bit more to a content repository instead of a system that's just optimized to outputting HTML pages. So you can put content in and then you can get content out in different channels as they say or multiple formats from HTML to XML or JSON to other devices. That is a big deal and that will allow us to do more innovative projects. That sounds great and then of course a follow-up on that Drupal has been growing quite well in Europe, in North America. Are there any lessons learned from that growth in these particular regions for the other regions outside Europe, outside North America? How do we take that? That's a good question. So any lessons learned from areas where Drupal has grown faster? I think I've traveled to a lot of places and met with tens of thousands of Drupal people and I think what's most valuable is our community. It's not the technology and I've seen amazing local communities in relatively small areas because they are really good leaders and then other times I've been amazed when I go to like a big city, if you will, and you would expect there to be a large community and there isn't. No one there. I think a lot of that comes down to the people like strong local leaders that build out the local communities are so important. So I think that's something that I've seen and we're talking about doing sort of and actually in Prague here, yesterday we had a community leadership summit so we're taking steps to sort of develop more local leaders or to develop science funny maybe, but to encourage sharing of information and knowledge about how you really run a successful local community because out of that comes a healthy commercial ecosystem in that area and they do events and a lot of it comes down to the local people so that I think is something that I've learned. So talking about the community, so expanding the local community in those areas that are maybe new to Drupal taking that to the next and the last question that I have. Any plans for a Drupal academy for young people? Last year, the last con in Portland we had the 11 year old Galen Steele attend. I mean, we need more 11 year olds don't we? I've always felt like a way to measure the success of a project is by sort of enough to be careful when I say that but it's like, you know, you measure it by the number of young people that come into the project and, you know, like I'd love to do things like an academy I'd love to see us develop ways to train more and more people and the beauty is that it's actually you know, higher ed and education is in rapid development and innovation right now. There's a lot of programs like, you know, in the United States there's things like edX which is basically online training platforms and all of these things and I think we may be at a good time to see what we can do there relative to Drupal because I'd love to see more people get involved because I think it's healthy for the project. I agree with that. Well, that wraps up the questions or a summary of the questions I think there's a thousand questions out there so you'll probably get attacked in a few minutes. But thank you very much and thank you everybody for tweeting these questions up to next time. Thank you. Is there more time for questions? Oh, no. Oh, okay. Let me... Just a reminder that now is the time to go take that big group photo so, Dries, maybe you can join Jam and help lead folks out. Sure. Please, around to the left down the main staircase out through exit 5 keep bearing left. Thanks again, everyone. It's... We'll see you tomorrow morning. Thank you. Oh, the map, sorry.