What is the backbone of millions of websites around the world? They were built using Drupal. The free, open-source content management system. It's leading a digital transformation across industries. From one hub to many, simple to complex. With swift page loading and ease of content editing, multilingual capabilities, and rigorous security, Drupal is the platform that performs. 70% of universities use Drupal. Media rely on Drupal for extensive delivery of content. Governments count on Drupal. Finance and commerce sites need Drupal for security. Tourism destinations bring their clear waters and mountains to life on screens using Drupal. Are you marketing for the future? The next billion customers of digital experiences will probably never have a personal computer in their homes. Drupal scales video, audio, and text to all devices. Work from a centralized content hub. Stretch your strategy across sites and channels. Whether it's one site to many or simple to complex, Drupal is the building block. Choose help along your journey with our partners. Dream big. Drupal will get you there. Good morning, DrupalCon. How's everybody doing today? Anyone go out last night? Was there fun to be had out on the town in this beautiful city of Seattle? Awesome. Well, we're thrilled to have you here in the Emerald City and I want to say that I'm especially impressed with the Drupal community's navigational skills. This convention center's got sort of an MC Escher vibe going on with all those escalators. So really, really impressed that you all made it here. It looks like we've got a full house. So I'd love to welcome you all to the event. And for those of you who don't know me, my name's Tim Lennon. I'm Hestanette on Drupal.org. And I have had the privilege to serve as the interim executive director for the Drupal Association since September. And it's really been an honor to be in that role, to serve this community, to work with the amazing Drupal Association staff, and to bring the whole Drupal community together for events like this and for all the programs that we undertake. This is a really special DrupalCon and it merits a special kind of welcome message that's bigger than just a hello, thank you, good morning, goodbye. A lot's changed at the conference this year. And just from what I've seen in the early part of the week, I'm humbled by all the positive reactions that I've heard. Our community has grown in terms of personas. There are the builders, the developers, the front-end designers, the UX designers, everyone who is involved in building digital experiences in building Drupal itself. All of you are here with us today. But beyond that, we've also brought in the content editors and the digital marketers, who now have a dedicated track within DrupalCon. And we're really excited about their presence here with us at the conference. This new track sold out like month and a half in advance of the conference. It's been very successful. And we want to bring these audience together with us for all the future DrupalCons moving forward. Similarly, we've created dedicated space for agency leaders to network with each other to learn how the buyer has changed for Drupal installations and Drupal sites and learn how to help grow the Drupal business ecosystem. And finally, we're bringing in decision-makers and people at end-user organizations of Drupal to close the feedback loop so that we understand their needs and where Drupal needs to go to support their use cases. But beyond that, our community has grown in other ways. Our thought leaders are increasingly diverse. This is a quick graph of speaker representation at the last three North American DrupalCons. The gray bar represents speakers who look like me.  But the blue bar represents the sort of underrepresented speakers from a variety of audiences across a number of axes of representation. And when we first began measuring this for our speaker audience, at Baltimore, we had about a 33% representation of these groups. In Nashville, that grew to 40%. And here in Seattle, 50% of our speakers are from underrepresented groups. It's really phenomenal. It's absolutely phenomenal. Also at this event, we doubled our grants and scholarships and speaker inclusion funds to help make this possible, to help bring people who might not otherwise be able to attend the event. And we're thrilled that the changes we've made have enabled us to do that. The support of sponsors, the support of those people, buying those tickets, all of this makes it possible for us to bring people who otherwise wouldn't be able to make it. So thank you to all of you who've helped enable us to do that. On the same vein, our community itself is becoming more diverse and inclusive. I want to give a special shout out to the Diversity Inclusion Group, who have led the way, pushing us to elevate the voices of underrepresented people, inspiring us to expand that speaker inclusion program, and who've rolled up their sleeves to do the work on Drupal.org and here at DrupalCon. You can see some statistics, anonymized demographic information from the users who've opted to give this information to us. This comes from about a 13% sample of the folks who've been active in the last year. And these are some metrics that we're tracking and then want to continue to improve over time. But that work is never finished. The work of becoming a more welcoming community, a more welcoming project, whether that's for personas, whether that's for people from underrepresented groups, and in many different ways, always continues. And I was really excited last night when the Drupal Diversity Inclusion Group announced a new initiative. They're starting a speaker initiative to help further increase the number of underrepresented people who feel confident speaking, submitting sessions, and coming to DrupalCon and other events to share their knowledge and their insights. So last night at the opening reception, they announced this initiative, and I want to thank Pantheon who's offering to match the first donations up to $2,500, and the seed donors you see there who have chipped in already, even though this just went live last night, to get us started. So if you'd like to get involved, there are some links you can use to learn more.  We've had a lot of conversations over the past couple of years on governance, and in this particular area, I wanted to give an update about the community working group. We've made a few changes in supporting that community working group. They've adopted a new charter in December of last year so that they can focus their programs in new ways. They're no longer just a conflict resolution body, but they can focus proactively on community health, on leadership training. We can provide legal support for the community working group, and they have a new independent escalation body for any of their decisions and the situations that they get into. And so that escalation body that the community working group can rely on is made up of the community-elected positions of the Drupal Association Board, so that's currently Suzanne and Ryan, and we've brought in a third-party outside member to give us a perspective beyond just the Drupal community. So that's Jono Bacon who will be joining that review committee. Now I'd like to give you some updates on Drupal Association programs. So first, last year we talked a lot about the Promote Drupal Initiative. This was sort of a one-time, fund-raised initiative to create something almost like an initiative coordinator position, except not for some code sprint, but for promotional materials, to create consistent Drupal brand and strategic messaging, to connect new decision-makers and influencers throughout the world. This has been a global partnership. The same way that we work or collaborate on code, on documentation, on UX, on events, it's an effort that spans the globe. And I want to thank in particular many members of the European community who have led the way in the Promote Drupal Initiative and put together a lot of materials, and I want to share a quick sneak preview of what's been made available. So this started off with a brand book for Drupal, so that any materials that were going to be created as part of the initiative would have this consistent look and feel. So it's an extremely long document, so I'm just going to let it scroll through here. But it has all the guidelines, the color, the logo usage, a tone of voice, all of these things that help us make sure that all the materials created by this group are in a consistent way. There was also a pitch deck that was put together as part of this effort that can be used collaboratively by any freelancer, any agency, any individual who's trying to demonstrate the power of Drupal, trying to show what tremendous sites, what case studies are out there. Again, it's just such a tremendous resource, but also tremendously long, so I'm flipping through it very, very quickly here. But there are some amazing stories there that everyone in this room is having a conversation about Drupal and the power of Drupal and where it's used in the real world. This can help you to show that to your prospective clients or whoever you're trying to educate about what we do. If you want to participate in this, by the way, you can submit a case study to be included in this slide deck, and you can get involved in the Promote Drupal initiative. In addition to that, you can also submit a case study format. This isn't live yet, so I'm just going to share a design mock. But we are intending to create a new version of the way the case study format on Drupal.org works. That's more media-centric, more interactive, with more testimonials and statistics, something that's better targeted to the end-user audience rather than just a sort of technical overview, although those details will be included as well. Finally, at the beginning of this presentation, there was a video that was put together as part of this initiative. That video is being licensed under Creative Commons, and again, being made available to anyone around the world, individual, agency, anyone who would like to promote Drupal on any channel they have to any audience. I want to say some thank yous, because the Promote Drupal initiative is not possible without the support of many individuals and organizations. I want to thank the top contributors who helped build some of these materials first, both individuals and organizations who did a lot of work to make those materials that I just showed you possible. But I'd also like to thank the sponsors of this Phase 1 of the Promote Drupal program. A lot of people came together when we put out a call for fundraising to make it possible for us to do this work. So thank you very much. Next, I'd like to talk about some more updates from the association, particularly around Drupal.org tooling. I think something might have happened involving a new virtual assistant on April 1 that was helping everybody out. That was really the big one, really exciting. But actually, the main thing I'd like to talk about is our partnership with GitLab and the tooling upgrade that just happened in the last two weeks on Drupal.org. Yes, thank you. We're a multi-year, multi-working group, multi-committee initiative, and we finally made a decision to move forward with a partner, in this case, GitLab. And we've completed that first phase of that work, which means that all of those code viewing links anywhere on Drupal.org and old issues and new issues in the sidebar of projects, all that stuff will now take you to the beautiful and much more usable code viewing interface in GitLab. If you're a maintainer of a project, you can already use inline editing tools to create a new code viewing interface. And coming next, we'll begin an incremental rollout of additional features. And that means merge requests are not too far away. So we're really excited about this, really excited about these changes. We're still working together with the GitLab team to make this happen. In fact, they're going to be here this week. There's a panel on Thursday morning if you have questions about this process or just want to hear about the journey. So we're thrilled with this and we're looking at improving and involving the tooling that the Drupal community uses. Finally, I want to talk a little bit about Drupal Steward, which is a new program that we hope to be introducing soon. Drupal Steward is born out of the idea that having to have your teams on Red Alert for a patch release, for a highly critical security release can be difficult, frustrating, especially if you're a large enterprise, especially if you're not in the United States in these time zones. We work together with the security team to create a sort of joint service that we're developing to roll out. So this joint service is to create a web application firewall that will help protect sites from vulnerabilities ahead of the patch release and will use those proceeds to support security team programs, support association programs. So there's going to be a bof later today that I encourage you to join to learn more about how this is going to work. And now a few thank yous and many many. First, a tremendous thank you to the Drupal Association staff. Without the help of the staff, none of this would have happened, and we are a small group of people. It's everyone, boots on the ground, everyone contributing in every way. So this is your staff of the association. If you see them, say thank you. I also want to say thank you to our production partners. These are the people behind the scenes who organized the AV who've consulted with us on other parts of expanding the event. They're great folks. If you run your own events, consider reaching out to them. Finally, I want to thank, well, not even finally, I want to continue to thank our sponsors, including our diamond sponsors, Acquia, Pantheon, and PlatformSH, all of our platinum sponsors, our gold level sponsors, silver level sponsors, funds, and module sponsors who sponsor things like special events like coffee or the women in Drupal Luncheon, things like that. I want to thank our supporting partners as well. The supporting partner program is what funds the work on Drupal.org. So for example, this transition to GitLab would not be possible if we did not have supporting partners to fund the engineering team. Similarly, all of the testing, the Drupal CI infrastructure, we simply couldn't afford it because of our signature supporting partners, our premium supporting partners, and the classic supporting partners in our partner program. Finally, a special thanks to top individual contributors to the project. So as you know, we started tracking a contribution credit system. In no particular order, here are all the top 75, I believe, contributors over the last year in terms of contribution credits. I have applause for these people who have moved Drupal forward. Absolutely. In addition, there are a number of organizations that sponsored this work, and I want to recognize the top organizations that do that as well. So these are the top organizational contributors, those who have sponsored the most individual work that made it into the Drupal project. So thank you very much to all of these people. And finally, thank you volunteers. There are so many of you here in the audience that I can't be in this room because they're around the convention center making everything happen, making everything work. So one more big round of applause for the volunteers, please. All right, some quick housekeeping and updates before we get into the rest of our programming. One, the code of conduct is critically important, and I wanted to talk about this pretty much at the top of my housekeeping session. DrupalCon is dedicated to being safe, inclusive, welcoming, and harassment free. Rachel and Rebecca on the Drupal Association team can be a primary point of contact if you ever need to immediately make a call about a concern you might have. You can also use that email address or talk to any member of staff who can connect you to the right person. So if anything should occur, please let these people know. The Wi-Fi, yeah, it doesn't beat the code of conduct, but in case you don't have it already, here's your information. On social media, you can promote us with the hashtags DrupalCon and DrupalContribution, and you can follow DrupalConNA for up-to-the-minute news about the event. Also, coffee. For the first time at DrupalCon, it will be free all day in the exhibit hall during exhibit hall hours. Yeah, I thought that would get applause. I was pretty sure that was the most important slide I had in this whole deck. Lunch will be served from 12 to 2 in the back of the exhibit hall as well. And the Women in Drupal Luncheon will be happening from 12 to 2 in the skybridge of the Convention Center. We actually kind of walked through that on our way here into this main stage. And don't forget to come to Trivia Night on Thursday. It'll be happening at the Armory. It's on 305 Harrison Street, sponsored by Palantir. It is a 21-plus event, so please don't forget your photo ID, and the Food and Drink service will begin just before 9. Immediately following Dries' keynote, we're going to do a group photo. It's relatively easy to find the place this year, I promise. We're all just going to go straight out these doors and then back to the registration area. That big M.C.S. you're looking atrium and do the photo there. One more thing. Some of you may be wondering, where's the pre-note? What happened to that thing? So I just want to encourage you, don't miss Trivia Night. There will be a special surprise there. And finally, I would like to welcome the Community Working Group up to the stage to present the award ceremony, Aaron Winborn Award. Awesome. All right. Hello, everyone. Hi there. So my name is George Demet. I'm the chair of the Drupal Community Working Group, and I'm here today with the fellow Working Group members, Mike Inelow, Jordan Afong, and Alex Burrows. So we're a group of volunteers whose job it is to foster a friendly and welcoming environment for the Drupal project and to uphold the Drupal Code of Conduct. We do this by helping resolve conflicts between community members, as well as providing resources, consultation, and advice, and recognizing and supporting effective and inclusive community leadership. In short, we do whatever we can to help improve the health of the community. Alex. We're here today to give out this year's Aaron Winborn Award, which is named after a long time Drupal contributor who lost his battle with ALS in 2015. The award recognizes an individual who, like Aaron, demonstrates personal integrity, kindness, and an above and beyond commitment to the Drupal project and community. Because of his work on Drupal media, as well as humility, generosity, and enthusiasm, Aaron's contributions continue to touch us all. The CWG accepts nominations from the community, and we vote on them as a group together with past winners, which include Kathy Thais, Gabor Hodge, Nicky Stevens, and Kevin Thall. This year, 18 individuals were nominated for the award, and over the next few weeks, we'll be contacting everyone who was nominated to let them know about the value and how much they are valued in the community. In addition to public recognition, the award includes a scholarship and a token this year. And also, this year, it includes a handmade piece of art made by our own community liaison, Rachel. All right, so I get the fun part. So this year's winner is someone whose contributions have helped create a more welcoming and inclusive community. So please join me in thanking and welcoming to the stage Leslie Glenn. So now we get to watch Leslie stand by and say some nice things about her. So Leslie has over 30 years experience in the software development field and has been working with Drupal since 2011. She's been involved in Drupal project management, site building, and client support. Within the community, she has organized and mentored Drupal sprints, has offered trainings at Drupal camps and Drupal cons, and has volunteered at as well as helped organize many camps around the United States, from home base in Boston. Multiple people nominated Leslie for this award this year. One of them wrote, and I'm quoting, if you have ever attended a North American Drupal con, bad camp, nice camp, a Ned camp, designed for Drupal, or any other major North American Drupal event, then you have seen Leslie. She's a constant inspiration of our community and each one of us should work and act. Another one of her nominators wrote, Leslie is a dependable, passionate, kind, and giving individual, and the Drupal community is extremely fortunate to have her. I've been lucky enough to know Leslie, the majority of my time, that I've been in the Drupal community, and I'm honestly hard pressed to think of an event where I've seen Leslie where she isn't volunteering in some form or fashion. She sets a great example for all of us, that volunteering just a little bit can make a huge difference. So it's for this reason that we are proud to present Leslie with the 2019 Aaron Winborn award. Thank you all so much. There's never, in a million years that I ever think that I'd be standing up here receiving this great honor. I would be much more comfortable standing at the back door back there, counting people coming in to the to the Aquino today. But thank you to all the wonderful people in the community that helped me over the years learn how to be a good community member. All the past volunteers, camp organizers, Drupal Con organizers, everybody that's helped me out. I want to say one quick word. I was lucky enough to be at Drupal Con. I mean, I'm sorry, at Nice Camp at the UN in 2013 when Aaron Winborn was able to give the keynote speech. Aaron was in a wheelchair. He was used in assistive technology. But he still spoke to the audience, told them about the media module, how proud he was of all the volunteers that helped. And now we're proud of all the volunteers that have helped now and bring that into core. He'd be so proud of everybody that helped out with that. Also Aaron spoke about, he was in a wheelchair. He was used in assistive technology. But he spoke about how he wasn't able to work anymore and how disappointed he was in that. But how he was still going to stay and continue contributing back to the Drupal community. And that was very inspirational for me and for a lot of other people that were fortunate enough to hear him speak that year. So, volunteering has been my way of giving back to the Drupal community. It's given me back so much more than I have ever given to the community. So thank you again to everybody. And as you continue this week just be nice to everybody like Aaron was, say hello. You know, reach out to somebody at the lunch table that's alone. And I'll go back to your communities and just volunteer and help out. So thank you very much. Thank you so much Leslie. And thank you to the CWG for organizing these awards and honoring some of our most amazing volunteers. I'd now like to welcome up Lynn Kaposi from AQUIA to introduce our keynote speaker today. Good morning. Congratulations to Leslie. Well done. Congratulations. So I'm excited to be here today as I was thinking about this yesterday. My first Drupal Con actually was in 2009 for those of you who may remember, in Washington, DC. So what a quick 10 years it has been. So absolutely thrilled to be here today. I'm the chief marketing officer from AQUIA. And thank you for those of you who were able to join us last night at the AQUIA party. Hope everyone had a good time. Who knew how many great ping-pong players we have in the crowd. So congratulations to the ping-pong winners. So I am not a developer but I am a marketer and I've spent a long time marketing Drupal and AQUIA. And at AQUIA I've had a great opportunity to work with so many different organizations. Large ones, small ones, all different industries who have really seen their businesses change based on Drupal and really have great business impact from using Drupal. My personal favorite I want to share is an application that's been doing some great work from the folks back home for me at Boston Children's Hospital. They have a Drupal application called Open Pediatrics and I can personally say that this particular Drupal application is a training vehicle for doctors, for nurses, for researchers and for caregivers and around the world I know that it has saved at a minimum hundreds of children's lives. So for me, it's a great opportunity to say thank you to you for helping to make that happen. Okay, what's going on at AQUIA? Just my quick commercial so bear with me. So if you haven't seen us lately or you haven't talked to us lately please come by our booth. We have a lot of new things that are going on. We make the best personalization product with Drupal ever so you can come see in our booth Lyft 4.0. You can hear the story of Wendy's and her stories. So please come by. You can also hear what we're doing in terms of lightning. We have a couple of presentations from AQUIANS throughout the couple of days. I just want to talk about a couple of them. One which I would invite you to come see is shockingly fast site development with lightning. So that's one that you might want to participate in. This is one of my personal favorites unpacking a personalized experience and so this is a great opportunity to have a great personalization using Lyft and with Drupal and you'll hear from both sides the marketer and developer working together in terms of a great personalization story. We do have a raffle at the booth if you want to come by and participate. One thing that we're doing this year is we decided not to give out chachkies but instead what we're doing for every person that comes to our booth we're donating $5 to the Girls Who Code organization. I thought that was a good decision as well so I'm glad that you support that. So come by our booth and I want to give as much money as possible to Girls Who Code. So a lot going on again please come by. The other thing that we have which is brand new for us is we're actually previewing at our booth the AQUIA developer studio. It's brand new. It's designed to save development time and effort in terms of building Drupal applications very quickly. So please come by. You can get early access to the developer studio code so you'll be able to right there if you want to you'll be able to use that and access it. So please come by. We have a great presentation that's happening on that. So I have the great pleasure of introducing Driz for the Driz note this morning. We all know he's Belgian born he's the founder of Drupal the pioneer of open source. In Driz's keynote this morning he has some great announcements that he'll be making. And one of the things that I think is equally as important the road to Drupal 9 is kind of what happens between now and then. So he'll be spending some time on that and as always he'll update beyond the code talking about community values and principles to life and the efforts to promote Drupal to the world. So it's my distinct pleasure to be able to introduce the founder of Drupal the founder and CTO of AQUIA and my friend Driz. Good morning everybody. Leslie congratulations on your award. I was actually crying as I was listening to your story and still emotional about it apparently. Sorry about that. Tim Lennon actually talked about you know as part of his intro he talked a little bit about diversity and inclusion and I wanted to talk a little bit more about that today as well. And so not too long ago I actually had a conversation with the Drupal diversity and inclusion leadership the part of that team and they actually said something to me that was really profound for me. It got me thinking and I've been thinking about it since. It's kind of special in a way because I've been doing open source for 20 years and so they told me something that kind of changed my mind about open source or part of open source and so I wanted to kick off my keynote with that topic before I get into some of the product updates. And so what they told me is that diversity in open source is actually much worse than diversity in the technology sector. And maybe to some of you that isn't a huge surprise but for me it was kind of new. And so if you look at some of the data and you can see it on the screen in the technology generally one out of five developers aren't men but in open source it's actually much worse. Only one in 20 identify as not male. And so seeing these statistics obviously makes me wonder how we're doing in Drupal and we don't have good data but regardless clearly there's a lot of room for improvement in this area. Why is it so much worse in open source? And there's obviously a lot of different factors to this but one of the factors is the issue of time. And so there are systemic issues that basically negatively affect underrepresented groups. For example, women still today often spend double the amount of time doing unpaid domestic work or in certain racial groups there's serious wage gaps and it affects how much these people can contribute. Some of them have to work more hours some of them have to work maybe two or three jobs to provide for their families and it's preventing them from contributing as much as maybe other people can or prevent them from contributing at all. And so the issue of time is a big issue. Free time to contribute to open source is a privilege and I used to believe I used to say, I used to write about this actually, I used to say that everybody could contribute to Drupal that the only thing that you needed was a willingness to learn and so today obviously looking at this data talking to different people about this I've come to realize that that is not true because open source isn't actually a meritocracy because not everybody has free time and so I believe that we have an obligation to try and do something about that especially those that have time we can do something about this today because everybody deserves the opportunity to contribute obviously we can't change all of this overnight we can't fix years and years of systemic issues and societal issues but there are things that are in our control as individuals and there are things that are in our control as organization that we can start changing today so before I go there let's talk a little bit about why this matters because there's a lot of reasons why diversity and inclusion are a great thing some of you may be skeptical in the room because as you probably know Drupal is used roughly by one out of 30 websites in the world what that means is that we serve billions of people right if you think about this notion if you visit more than 30 websites on average you'll have hit a Drupal site most people visit more than 30 websites and so basically we almost touch everybody in the world and these people that we touch with Drupal they are very diverse and so the best way to build software for all these people is to be diverse ourselves as a community of contributors that's the best way we can do it and for those that contribute to Drupal core we do have blind people contributing to Drupal core and it's been amazing because it actually helped us build better software and how do we apply that to everything we do and this is not just me saying this this is backed up by a lot of research Harvard did research on this all of these organizations another organization McKinsey they said that diversity improves collaboration because it actually reduces bias it reduces groupthink it helps organizations deal with conflict much better it's also proven that it unlocks creativity when people feel welcomed and people feel safe and comfortable they're much more willing to share ideas to propose ideas and I've experienced that myself in various organizations and groups like if you feel comfortable you're much more willing to share so these are just a few examples of why diversity and inclusion matters obviously it's not only good for our community but it's also good for all the people that we touch with this why we want to do this and so those that have time to contribute we should really try and make an effort to welcome other people in the community and there's a lot of different ways you can do this you can intentionally try to welcome people you can mentor people from underrepresented groups when they ask you to and you can also make space if you're in a community organizing rule you can present organizing rule you can make space to give them time to present or lead sprints these kinds of things the things that we're starting to do or have been doing now for several years with the Drupal Association a few weeks ago I was reading up on issues in the issue Q&A came across this coat review from I think it's pronounced amazing about this review was the kindness and how helpful he was and I was literally blown away by these comments and so it was a great example of how many of us can behave in the issue Q and this is really important because other research research from GitHub has shown that one out of five people we experience negative behavior when contributing to open source actually stop contributing at all so imagine how many people you can lose and how quickly you can lose many great contributors so this is something that all of us can always be aware of organizations can also do a lot of things obviously you can pay your employees to contribute so people don't have to work at night or on the weekend you can pay them full time you can pay them part time to different programs that allow others to contribute so these are just some of the things that you can do as an organization of course Drupal itself doesn't sit still we're constantly looking to do more things to improve our own diversity and inclusion we've extended the commit credits to include non-code contributions that's been huge we have updated gender fields on Drupal.org to not be a binary field so people can choose from more options and self-identify we keep updating and tweaking our code of conduct, our terms of services we've expanded our Drupal Scholarship program Tim talked a little bit about that and as Tim also talked about we keep increasing the diversity of our speakers not only is half of the speakers from unrepresented groups but almost 40% are also first time speakers which is a great statistic as well obviously education and open dialogue are very important so we have a lot of sessions about this as well and you can go watch some of these sessions today these are just the sessions today about diversity and inclusion so I encourage all of you to attend those especially if you wouldn't otherwise have chosen to attend one of those sessions so with that I want to progress into the next section so we have a lot of people contributing to Drupal many of whom are here today and together we're one of the largest and most thriving open source communities in the world so we should lead by example we have over 1,000 organizations contributing to Drupal it's a massive number if you think about it how many other open source projects have thousands of people we have companies like Pfizer we're leading a core initiative around workflows we have companies like Hook 42 and they wrote the book on Drupal 7 multilingual we're also sponsoring the simply test.me testing infrastructure 1x internet they co-organized Drupal Europe and employ a Drupal Association board member 3rd and Grove they're sponsoring a full-time core committer Drut they sponsored the creation of a sort of a sprint kit which is used to mentor and onboard new contributors in our community Thunder was building a distribution for media websites and on so many great contributors there's also over 10,000 individual contributors to Drupal again this makes us one of the largest open source communities in the world people like Asgar who are promoting Drupal in Pakistan as a way to make a living for those with limited resources it's an amazing story Fatima, part of the Drupal diversity and inclusion leadership team she's also working on governance she's also contributing fixes to Drupal core contributes in many ways Narcisse was doing Drupal trainings in the Democratic Republic of Congo has been doing that for many, many years Hezes who creates the Drupal console project which is used by many Poonam who has led multiple trainings and also led 50 women in technology and in many ways in India these are just some amazing stories and I can keep going and going and going but together as a community of people all around the world organizations all around the world we've made some amazing progress in the last six months since my previous dream and so I want to give you a quick update on all of the progress that we've made first of all Drupal 8 we have 35% more Drupal 8 sites compared to a year ago the platform is also really stable because we have almost 50% more stable Drupal 8 modules compared to a year ago which is really fantastic news for those that are looking to migrate to Drupal 8 they may not have been able to yet because some of the modules weren't ready so more and more modules are getting ready very quickly we're also less than three weeks away from launching 8.7 which is going to be a fantastic release yeah so let's talk a little bit more about that so at Drupal Europe the previous conference introduced this kind of mountain which is representing the Drupal 8 product strategy it's like where do we want to go from a product point of view to this framework in this presentation again to help you understand the progress we've made and where we want to go next so first I'd like to talk about the first strategic track which is to make Drupal easy for content creators and site builders and you can see some of the initiatives that we have on this track and then for each of the initiatives by the way we have road maps and plans and so it's kind of like it cascades down let's look at layout so I'm going to show you a video of the progress we've made in the layout builder this video actually will use umami which is another initiative so it's kind of nice to see those initiatives work together if you will so I'm going to hit play and we're going to watch it together and then we'll talk about it umami is a website with recipes one of umami's recipes was just featured on the tv show because the featured recipe is getting so much traffic from people who are watching the tv show we want to take advantage of that we don't have time to involve our development team it's too slow as an umami editor I've been tasked with creating and adding a new banner on the recipe page that links to a special offer I'll use the layout builder to do this this banner is new content that doesn't exist elsewhere on the site so I start by creating a new block since I'm using layout builder I immediately get a preview of what the banner will look like it looks good but I think it would be better to replace the existing image with the new banner so I delete the old image and using layout builder's drag and drop I can move the new banner into the place that the old image was in it can be cumbersome to move large items like this so I use the toggle preview checkbox to show small textual representations of the block instead this makes it very easy and fast to move things alternatively, I could use the keyboard or screen reader to navigate and use the layout builder because it conforms to web content accessibility guidelines recommended by the World Wide Web Consortia this means it's accessible for everyone if you are a keyboard user it's actually very fast in this example, the block is being moved using only the keyboard the layout builder supports all the basic use cases that you've come to expect but it also supports more complex workflows for example, you can send layouts to improve a workflow as such, this recipe has remained unchanged throughout this editing process now that I'm happy with the way the page looks I can publish it right from the same interface staging layouts is not something that many systems support but Drupal's layout builder does in this example, we showed a fairly simple workflow but because it leverages Drupal's powerful workflow engine it can handle very advanced workflows too I now see my new banner on the published page and it looks fantastic as you can see, I was able to add just a few minutes and with Drupal's workflow integration I was able to do that safely no need to involve our developers yeah let's look at another one instead of editing the layout of a single page let's edit the layout of a collection of pages this is particularly useful for large sites with hundreds or thousands of pages Umami did a usability study on its recipe pages and one of the takeaways was that users get confused with the white space below the image the UX and design teams have recommended that we display the recipe information next to each other rather than stack below each other we have hundreds of recipes on our website and it would be very tedious to update them one by one fortunately I can use layout builder to update all recipe layouts at once by modifying the default layout for all recipes here we are looking at the layout template for a recipe I've added a new four column region in between the image and the ingredients and now I can drag and drop the recipe quick stats into those columns after saving the new default layout I go to my content list page click on a random recipe and I can see that the new layout has been applied much better being able to edit templated layouts like this is a powerful differentiator from other layout builders and it's a huge time saver for sites with lots of content there you go in some amazing work I actually do believe we leapfrogged the competition with this because not only what you just saw not only can we support basic use cases like maybe one of pages but we can also support all of these advanced use cases now like templated layouts like you saw or these layout workflows these are things that are not available in our competitors layout building tools the fact that the layout builder is accessible is huge too and you guys saw that there's something that we should all be very very proud of it's hard work but we did it and the good news is that this will ship with 8.7 in 3 weeks yeah it's awesome in total 123 people contributed to this and I can tell you from spending time with them or some of them not all 123 but some of the bigger names on this screen they worked weekends to get this stable for 8.7 like this team deserves a big round of applause about 68 organizations supported many of these individual contributors so also let's give them an applause as well next I'm going to talk about the layout builder and the layout initiative which originally was started by Aaron as Leslie mentioned and so I have a video about that as well I'm going to play it now this is where the media library comes in handy I can edit the article scroll to the bottom and click the add media button the media library opens and I can see media used elsewhere on the site one of the existing articles on our site we use Drupal 8's media library which makes it really easy to create and reuse multiple kinds of media as an umami editor I was tasked with adding some mushroom photos to the end of an article about mushrooms elsewhere on the site one of the existing images is of a mushroom so I go ahead and select that I want more than one photo though so I'll upload a few more I can upload as many files at once as I need to so I choose 3 images of mushrooms once they're done uploading I noticed that one of them isn't a mushroom that's okay though because it's easy to remove that item before saving once I enter any required fields metadata in this case I can save and immediately insert the new media into the field but I choose save and select to add more media this field allows images and remote video so I see a tab for each of these media types I switch to the remote video tab and paste a URL for a video hosted on Vimeo I now see both my images and video in the widget where I can rearrange them to my liking once happy I save the article and scroll down to see my additional media displayed as I would expect a lot of what you saw is stable and the initiative actually made more progress in the last 6 months than maybe in previous 6 months chunks so they've really accelerated their progress some of these things are stable some of them are experimental and some of them are still in progress the biggest thing we probably have to do is have the WYSIWYG integration so they can easily embed images or videos from within the WYSIWYG tool in Drupal so we'll keep working on that for 8.8 which will be roughly 6 months from today in total 310 people individuals have come together to make this happen which is a crazy number and 122 organizations have given many of these people time to work on that next I want to talk a little bit about the administration UI which is a newer initiative but last year I spent a lot of time actually talking to not just users but also Drupal agency owners and so one of the biggest items of feedback that they gave me is that it can be hard to sell Drupal between quotes because the UI looked a little bit dated and they would tell me like end users, customers, potential customers they're looking at more modern experience so we decided to start this initiative and it's really important because I do think a lot of people when they look something that looks a little bit dated they make assumptions about how the technology actually is under the hood but the reality is Drupal is really awesome under the hood we're just not good at showing it off through our UI it's also another surprise that it does look a little bit dated because if you think about it we started working on the current UI maybe almost 10 years ago when we started working on Drupal 7 and while we've made updates to it we haven't really kind of done a major refresh and so I believe it's holding back Drupal's growth and so we decided to make it a priority and so the team's actually done a great job making progress and they came up with mockups and style guides and all of these things they've done usability testing you can see some of the before and after here might be a little bit too small but the summary of it is that it does look a lot more modern it feels a lot more modern there's actually much better use of space it has better accessibility it's better because it has more contrast it has more space to click all of these things and so I'm pretty excited about this we don't quite know when it will be ready but we're hoping to target 8.8 or 8.9 which could actually be great timing because it's getting close to the release of Drupal 9 and it would give Drupal 9 a fresh coat of paint if you will this is an initiative where we'd love to get more help I mean it shouldn't a lot of you are experts in front of development so we would love to get more people involved so we can get it done sooner than later so if you're looking for ways to contribute this would be a great area I'll talk more about the contributors once it's actually in-core so hopefully next time I'll go into a little bit more detail about that so that's really the first kind of track to make Drupal easy for content creators and site builders it's important because for Drupal to be successful we need to be successful with every persona it's no longer enough to just win the hearts and minds of developers we need to succeed the marketers and the content creators the people actually the people spending up to 8 hours a day in Drupal creating content, managing content and the benefits are huge because it allows those organizations to be more cost efficient they have to rely less on developers to get certain things done and this is important for organizations small and large this helps the very small non-profits and it also helps the large enterprises and arguably it will help the small non-profits much more than the large enterprises so very exciting work I didn't talk about the workflow initiative here but they've also continued to make progress more things have become revisionable like menus and taxonomy terms and so lots of great work on that initiative as well so shout out to them so that's the first track let's talk about the second track the second track is to make Drupal easy to evaluate and adopt we've done a lot of great work on this you may remember from previous key notes where I showed all of the steps it takes to install Drupal I forgot the number but it was 50 plus we brought it down to three steps or one step very small number of steps but that team continues to make improvements we've also made a lot of improvements on Migrate so Migrate and Migrate API are the tools that organizations use to migrate from say Drupal 7 to Drupal 8 or from Drupal 6 to Drupal 8 or even from another platform to Drupal 8 and one of the key people on that initiative is a quiet one Vicky she's a long-term contributor of Drupal she's been very passionate about open source she actually won the New Zealand open source award last year which is really cool and so I had a chance to interview her all the way in New Zealand I didn't go to New Zealand but through a Google Hangout and so I'm going to play a little video interview with Vicky right now so when I look back at what I started working in migration this was back in 8.0 I started writing migration tests as my starting point and I have found that the tests I wrote then and the ones I write now are largely the same so that proves the API is doing its job doing it well what has changed are some of the development tools that makes it easier we have more specifics like process plugins that allow us to do a bit more and to cover a few more edge cases that kind of thing and over time in the contrib community the tools have expanded and grown to cover more to fix bugs so we started out with a good base and over time it just gets more robust each time each iteration and in the sense it's more complete because we're covering more of those edge cases and getting wider out and further out can handle different sources of CSV, JSON etc etc are all handled of course we claimed ourselves stable in 8.5 so from there on it's been just building on that base adding bug fixes edge cases so there's really since 8.5 there's no reason that people should hold back on migrating it's certainly ready to migrate and ready to migrate now waiting for Drupal 9 will not assist the migration process there are a few edge cases that still need to be finished off primarily with multilingual and for those cases as well you can start your migration now come talk to us on Migrate Stack and look at the issues to see where you fit in the edge cases many multilingual sites have already migrated and if you're not one of those edge cases then please begin your migration yeah for those of you that follow the commit stream if you will of all of the code changes to Drupal there's not a week that goes by without several commits to the Migrate API and so if you have looked at migrating to Drupal 8 maybe a year or two years ago have a look again because the tools have really advanced so between the module readiness that I showed earlier and the maturity and the progress on the Migrate API do check again because we should be a lot more ready for you to migrate today mentioned the out of the box initiative that initiative initiative is actually completed they completed its goals I should say but they've also been making more progress they're completed their goals but they're continuing to make it better which is really awesome they have added a Spanish translation and they did that in no time which is a great testament to Drupal's multilingual capabilities they added a welcome tour to improve the accessibility of the Umami initiative and the theme and many many more things and so it's really exciting to see this get better and better as well 187 people contributed to this it's amazing and behind them, or behind many of them there is 86 organizations as you can see a lot of volunteers contributions here so obviously this is really important especially the out of the box because it makes it easier for organizations and individuals to discover and learn Drupal instead of having to go through all of these steps before you have a functional Drupal site that shows the power of Drupal you can now get there in just 30 seconds and a few steps so that's good for the grassroots adoption of Drupal if you will because people can do that themselves it's good for digital agencies organizations that need to demo Drupal to a potential Drupal customer or potential Drupal user and so you can use this to help sell Drupal and so I think that's fantastic that we've made this much progress and that with 8.7 that's really ready to go so great job for all the people involved with that so the next track is to make there's different things in this track but it's to make Drupal more relevant and to increase the impact of Drupal and the item that I want to talk about here is API first because we've spent a lot of time talking about the six month feature releases previously and I'll touch upon that again later but we achieved a major milestone for the API first initiative and that's that JSON API is now committed to Drupal 8.7 yeah it will be stable so it's shipping as a stable module in just three weeks and it's really very important I think for Drupal's relevance for many many years to come but it allows you to do for those that are not familiar it allows you to get content such as articles a programmatic way through web services like you can see on the screen so that's really useful when you're building a mobile application or a single page JavaScript application or maybe when you want to push content to a digital kiosk or any kind of channel or platform or device Drupal's JSON API implementation is extremely complete it respects all of the permissions in Drupal it supports reading and writing content it plays nice with Drupal's versioning and translations and can literally be used for any piece of content in Drupal it's probably the most complete implementation of JSON API in the world it's really exciting and it leverages it builds on years and years of work and it leverages the entity API the field API the configuration and type data APIs and much more and so it's deeply integrated it's robust it's not sort of slapped on you know it's really in Drupal and goes to the core of Drupal and that's super important because it extends our leadership in API first you know there's a large competitor that we have their name starts with an A and ends with B they announced GraphQL support like a few weeks ago and not like they released it a few weeks ago they announced it to be released like later this year and so think about Drupal we've had GraphQL for years we've had JSON API for years and now we're shipping with JSON API out of the box for every site to use just in three weeks and the impact of this work will be big right so we'll set up Drupal for success in the next five to ten years because it helps with different frontend applications but it also helps with backend integrations and so the use cases are pretty vast and as you can see in this slide we support all of the different configurations that you can think of which is pretty exciting 146 people worked on this and they've worked on JSON API specifically for two years the result of two years of hard work it was all started by Mateo and Wim and Gabe really jumped in as well and so the three of them I would say did an amazing job pushing this over the finish line a lot of organizations were behind this as well which was great to see so thanks to those organizations too so that's that track the last track I want to talk about here is sort of the green track which is about reducing total cost of ownership for developers and site owners and there's a lot of different things on this track and we've made progress on almost all of those things but I also believe there's more we need to do on this track I feel like as we kind of complete a lot of our goals on the other tracks we need to focus or refocus some of our efforts on this track because it's really important for Drupal growing adoption is a priority for us and making it easier and cheaper for individuals and organizations to use Drupal is pretty important so let's talk a little bit more about that and I want to dive into this track and I want to touch upon two different things one is the upgrade from Drupal 7 to Drupal 8 and then is the upgrade from Drupal 8 to Drupal 9 so let's start with 7 to 8 so first question is how many of you have a Drupal 7 or maybe have a customer that's still on Drupal 7 that's a lot of you so no surprise there so it's something that we need to talk about first of all no panic because Drupal 7 is actually still community supported for two years and seven months two years and seven months and after that a number of vetted vendors for at least three more years so that will be commercial support but support will be available for three more years and so that means that Drupal 7 is supported for at least like another five years at least another five years which is in my conversations a lot of people don't realize that they feel like they need to move off immediately now let's talk a little bit more about that we tried to figure out what's a good kind of like analogy that we can use here but one of the challenges that we've had in the past is when a major version goes end of life you need to change tracks you need to get on the next track and it's not as simple as getting up the train and getting into the other train maybe it feels a little bit more like actually moving the train not just the passengers it can be hard because you have to rewrite custom code because we made API changes you have to actually migrate your content from Drupal 7 to Drupal 8 and depending on your situation that can be hard or it can be relatively easy too especially for large organizations large websites this can be pretty hard now a lot of organizations are starting to migrate now here are more and more organizations that are starting to migrate and I decided to focus on complex organizations because that's where most of the pain is so the first organization I want to talk about is the state of Georgia and Nikhil, who is a chief digital officer is going to talk a little bit in the next video about their experience moving from Drupal 7 to Drupal 8 I'm Nikhil Deshpande, I'm the chief digital officer for the state of Georgia and I head the digital services team who works with state agencies and elected officials and we host all of their sites on a Drupal platform we have been using Drupal 7 since 2011 we have a digital platform that hosts about 110 websites as of this day making sure the content is well served from an agency perspective to our citizens which is Georgia's population is about 10.5 million so we have a pretty decent traffic hitting this platform in all of the 110 websites so the decision to move to Drupal 8 was not that easy because Drupal 8 was so different from 7 and also when we invest in a large project we have to show the rationale behind it but as we started learning more about Drupal 8, it really met the overall digital strategy and the requirements that we had set for the state which is we already have a federated model with Georgia bubbling up content from agency websites for example JSON API we basically can now connect websites and share content across each other accessibility for example for us is non-negotiable as government we have to make sure we comply to a certain level of accessibility so having known that Drupal 8 in its core itself is a great knowledge to have and also user experience in general I saw that it was mobile first and it's a basic build which is great because our mobile traffic has been spattered for the last few years and also seeing that the responsiveness of Drupal 8 also seeped into the back-end editorial experience as well because we have editors updating content using several devices I think overall the core was better inclusive of modules and dependency on content which is great, love content modules but that was also really good that it was a well-rounded solution for us to begin with and last but not the least the community, the community is growing we have more and more partners and individual contributors I think the community really was the last piece of the health of it made us decide to move to Drupal 8 As far as contributing back is concerned, the whole idea for us to implement open source was the whole contribution aspect of the community comes together and makes this a better product so I think it is our responsibility to make sure if we do something it needs to go back to the community so we have done that with Drupal 7 but as we were working on even Drupal 8 we only selected partners that have done a significant role and jump up of contributing back and that was one of our selection criteria to be honest with you but so far we have about 36 patches contributed back I want to say we are working on making sure that we contribute some of the updates to the media module and I think we have block Blacklist contributed back so far and again as we go and work more on our platform we will be contributing back but I'm really happy that we have done that so far and the fact that everything that we are building we are building from a mindset of contributing it back to the community awesome, yeah there's a lot of different things that I like about this video one it's honest, they said it's hard but it was worth it I hope you heard that in the video I also like that they are contributing back and also like that they said the partners that contribute back and I've heard that from others and I talked about that last time using Pfizer as an example they've learned that working with agencies that contribute back gives better results because chances of them really knowing what they are doing is much higher and so a couple of great anecdotes there Nikhil and the team or maybe not all of the team are actually here this week and so I'm sure you can go ask them questions from Drupal 7 to Drupal 8 I have one more video that's the example of Pega which is a large technology company publicly traded company and so they also shared their experience going from 7 to Drupal 8 so I'll play that now I like cake and it was the best choice we could have made the plan was to move our two core digital properties to Drupal 8 the properties that receive millions of visitors our digital presence needs to support the business in going after our biggest strategic problems and solving them these are moving targets we need to get the most velocity possible we need to get the most velocity we can from running a portfolio of 10 distinct websites through one technical platform the first thing we realized was that we couldn't swallow this whale hole we needed to have smaller bite size chunks that we could work with so we ran D7 and D8 sites in parallel until fully migrated so we adopted an agile methodology hired a scrum master and packed on some PM and business analysis done right not even close the second thing we realized is that we couldn't do this alone or about as far from the vanilla migration as possible so we brought in partners to augment our staff in key areas we had thousands of pages of content all needed to be migrated to new templates we had many complex integrations including analytics, multi-language federated search goodbye beans, hello paragraphs and we gave back to the community there are a lot of really talented folks out there and they supported us during some of our most difficult challenges looking back, I think this was a case that the mountain looks a lot steeper than it is and you're sure some of the terrain was a tough go but we did it and it feels great our websites are faster and much easier to maintain and theme they're clean, well architected they make the job of our developers much easier Drupal 8's content authoring cuts our self-service time down by a third making it much more efficient for our content authors in reality we didn't have a choice we've got to keep pace with the evolutionary needs of our organization and we see the switch to Drupal 8 as a generational improvement it's the kind of thing I encourage everyone to just jump into did I answer your question? would I migrate to Drupal 8 again? yes but just not today that was a good video, it's a funny anecdote I reached out to Derek one of the people in the video and said hey can we do an interview for some of the questions I'm thinking about next thing I know they came back with this video which was amazing so thanks for doing that it's a great video and again it's very honest if you look at it through the right lens this is a complex organization with a lot of integrations and they decided to do it and they came out being very happy it's faster, it's easier they reduced their costs there's a lot of benefits to upgrading to Drupal 8 you can see some of them on the screen some of them were echoed by people in the video I'm not going to go through all of them here but go talk to different sponsors in the exhibition hall if you want to learn more about why you should migrate to Drupal 8 and why you should migrate today last thing I want to mention real quick without going into the details here there are tools available in the community that can help you with this migration from migrating code to migrating content and data so check out those tools if you haven't, they'll help you and these tools keep getting better too another question how many people are on 7 or have a customer on 7 and are waiting for Drupal 9 how many are going to skip a release some people so I want to talk a little bit about that one of the things that we've changed is that once you are on the Drupal 8 track once you move that train from the 7 to 8 track you're going to never have to change tracks again so that's pretty powerful because they're just going to keep the train on the track and new releases are going to come out and the upgrade from 8 to 9 or 9 to 10 will be easy so again I speak to a lot of people that don't really understand this yet so I wanted to reiterate that so in conclusion here for this section and it's fine to stay on 7 if you don't want to move, that's fine it's supported for quite some time however, there are a lot of reasons to migrate to Drupal 8 and knowing that the upgrade will be easy there's real benefits in upgrading sooner than later because you get to take advantage of these of these new features on track after you upgrade to Drupal 8 there's really no reason to wait for Drupal 9 because the upgrade will be easy so let's talk a little bit about that in detail the path from 8 to 9 because there's a lot of questions about that as well and so I want to make sure I try and address some of that first of all, Drupal 9 will ship in like a year or two months or so that's pretty close I'm feeling a little anxiety so most people are pretty excited here except maybe one emoji that's a little bit more terrified but for the most part it should be exciting the target is June 2020 however, we have the option to fall back to December 2020 just in case we need more time to prepare but things are going really well right now and so June 2020 looks very likely I would say just as a reminder there is two reasons why we need to bump the major version number from 8 to 9 1 is because we use third party dependencies like a symphony and symphony we use symphony 3 specifically and symphony 3 will be end of life at some point and so we need to move to symphony 4 or symphony 5 and doing that migration requires us to increase our major version number of API changes but we also get all of the benefits of symphony 4 or 5 so it gets us better dependencies so to speak and the second reason is that we need to drop deprecated code and I'll talk more about that in a second but we have a new innovation model now where we can innovate and add new features and ship new capabilities like the ones I showed, layouts and media but to maintain backwards we do manage deprecated code and at some point that becomes overhead so dropping that deprecated code improves maintainability improves performance improves the developer experience so the way we innovate as a quick reminder because this started with Drupal 8 is that we now have major and minor and patch releases and we do a minor release every 6 months is an example of a minor release it can come jam-packed with new features so the way that actually works in a little bit more detail is as we add new code to these releases we may deprecate old APIs you can sort of see that here visually on the screen and we keep doing this but at some point we will have to upgrade these third-party dependencies we don't want you to use insecure versions of those so let's take symphony for example at some point we need to go to symphony 4 or maybe symphony 5 and when we do that we have to bump the release from 8.9 in this example to 9 and then we can also actually drop all of this deprecated code and sort of clean up some of our code base and that's what we will call Drupal 9 so what does that mean well it means Drupal 9 is basically identical to Drupal 8.9 minus the deprecated code plus the updated third-party dependencies that's really what it means so there's not major new things in 9 compared to 8.9 and that's important because any Drupal 8 module that uses deprecated code will continue to work with Drupal 9 yes and so that means that the upgrade from 8.9 should be easy alright so it's kind of a big deal because again 7 to 8 can be pretty hard but Drupal 8.9 will be easy now there's a little asterisk there can you see that I can zoom into it and it's assuming no deprecated code is used by these modules and so I want to talk a little bit more about that because the call to action that I'll get to in a few minutes is that we as a community need to start managing deprecated code well alright so what is deprecated code? it's a good question it's a fairly high level but here's an example of maybe something that was in Drupal 8.4 file unmanaged copy it's a function and at some point we decided to change it to a service model as you can see here it looks a little bit more complex maybe but it has all sorts of advantages that you don't have with the original and so we added the Drupal service thing and we deprecated the file unmanaged copy and so what that means is that modules need to be updated and in this case you need to do a search and replace if you will from file unmanaged copy to Drupal service yada yada yada so that's an example of deprecated code and so then the question is when Drupal 9 gets released the original file unmanaged copy will stop working so by the time Drupal 9 is released you need to have done that search and replace so that's kind of the idea and so then the question is how do I know if my site uses any deprecated code how do I know that my site will be ready for Drupal 9 and so good news is there is a bunch of tools so Matt Gleman from the commerce guys he actually built something called Drupal Check you can download it and you can run it against your module and when you do that it will tell you all of the sort of errors that you have meaning all of the uses of deprecated code in your module you can see it's pretty easy you can see line 40 of this file I have a call that needs to be replaced with something else that tool is available today and I encourage you to use it today yeah the other thing is like there's really no reason to wait for Drupal 9 to do this because again if you do this today and you change your code today you actually get to benefit from these changes today as well right because you would use the new code in Drupal 8 already I would also encourage you to integrate this tool in your developer workflows in your automated developer workflows so that you can always keep checking what's deprecated and what's not deprecated there's also another tool that we've been building which is a more detailed tool it's the upgrade status module and what it does is it basically will use Drupal Check but it will scan each of your modules one by one as you can see here and while it's scanning you can actually start looking at some of these error logs this is all from within Drupal so if you're a site owner maybe less technical you can go in and check hey are we ready you can actually from there you can link to documentation and you can actually see what you're doing on your screen and it will tell you what to change so it's very easy to figure out what to change and how to change it you can export it as well get a full export of all the deprecations in all your site's modules you can send that to your favorite developer and so it's a great little tool and so you can install it on your site and if you're maybe less technical or you prefer sort of a UI based solution you can use this to see if your site is ready and if there's no deprecations if there's no errors it should mean that the upgrade is easy assuming we can actually catch all of the deprecations and so it's pretty cool Dwayne from Pantheon actually used this tool and he ran Drupal Check against all 7000 contributed modules that's a fun thing to do I bet but basically we looked at that data a little bit more but basically Dwayne said I think it was 44% of those 7000 modules so a little bit less than half of those modules they actually have no deprecation violations today which means they should already be ready for Drupal 9 which is pretty good and then you can see the orange thing which is a little bit more than a quarter these modules have only either between 1 and 5 deprecations they should be relatively easy to upgrade I actually upgraded my own site or have some of my own modules and it was very easy for me in my case I should say because all of my deprecations were search and replace some of them are a little bit more involved than search and replace but in my case they were all search and replace and my site was ready for Drupal 9 in 10 minutes and then about a quarter of the modules of the 7000 modules have 5 or more deprecations so they need more work and so what this all means is in terms of call to action we should stop using deprecated code in core and so we have a little bit more than one year to remove all of the deprecated code from all of these modules including our own custom modules not just the contributed modules we're also going to make Drupal 8.8 the last release to deprecate code and so it will be stable if you will in terms of no new deprecations being introduced and so that allows you to kind of use 6 months of the stableness to really get ready for Drupal 9 I will say that we should look at ways to expand Drupal check to also scan Twig and JavaScript which it doesn't do today it's focused on PHP code so that's an area where we would love to get more contribution and so that's a little bit about the upgrades from 8 to 9 so hopefully you'll understand that once you're on 8 the upgrade to 9 should be relatively easy another thing I would love to see us work on is automatic updates it's something that we have some progress on but arguably not enough I personally believe that it's one of the most important things for us to work on making Drupal updates easier is really important and today it's fairly complex still here's an example of a minor update or a patch update you need to do all of these commands obviously you can script them but you have to update code you have to do that on your local host then deploy to production and so really it's a lot of steps too many steps and it requires a developer and you may have to do this multiple times a month so how do we make that easy and so I hope that this week we can spend some time on that I hope we can refocus some of our energy on this problem we need to work on composer support and core and contrib we need to find help with some of these initiatives good news is though the European Union has decided to provide some funding for this which is pretty exciting so I feel pretty good that we're going to make progress and I hope that in Drupalcon Amsterdam in six months I'll be able to stand on stage and actually give some sort of demo that would be my goal so obviously I would need your help with that but that would be fantastic and I hope that the Drupal 8 release cycle alright so obviously all of that work is important because it helps with security it helps make it easier for organizations to maintain Drupal and again it benefits organizations small and large and again probably more beneficial for small organizations who can afford to have developers on staff very important work and lots of good progress and so this kind of sort of sums it up a little bit all of the different things that we've been focused on as you can see we've been working our way up the mountain to the flag we've made a lot of great progress and personally I feel pretty pumped actually even though I may not communicate that well but I feel pretty pumped about all of the progress we've made between layout and media and preparing for Drupal 9 and all of these things and I really feel like we've found a rhythm and a cadence and a heartbeat every six months we're shipping new features we're innovating things are growing I feel like we're ready for the future with API first and things like that and we're making Drupal easier and easier to use we're making Drupal easier and easier to maintain excited that the benefits basically everyone so to recap Drupal 8.7 will be released in three weeks and it's jam packed with innovation Drupal 7 has community support until November 2021 and we'll have commercial support after that for at least another three years there are many reasons to upgrade to Drupal 8 now and you should if you can Drupal 9 is targeted to be released in June 2020 and updating from 8 to 9 will be easy assuming we manage the applications well and we will I've put all of that together in this little timeline which I'll share in my slides when I share the slides in my blog maybe something you want to print out hang up next to your bed or your cubicle send to your manager maybe but it puts it all kind of together in an easy to use visual and then the call to action you know let's work on being more and more diverse and inclusive of others something that we all can help with it's something that all of our organizations can help with let's start removing the use of deprecated code and let's start removing it now the benefit doesn't come with Drupal 9, the benefit comes today because you're using better more modern APIs today and last let's try and refocus on the automated upgrades problem I think we've done a great job across the board all of these tracks amazing progress and I wish we could really make a little bit more progress on the automated upgrade problem and I think we can and so let's try and do that and make it a focus the next six months between now and DrupalCon Amsterdam so with that I'd like to say thank you yeah thank you


that together, Filipinos and U.S. Marines are coming through several islands in the Philippines. My name is First Lieutenant Adams, I'm the Ex-O for Charlie Company, the 3rd of all combat team. We're here for the Latorra Campaign in the Philippines, which is an exercise within Valkitan 24. After two weeks of integrated training between the U.S. and Filipino Marines, we got together, conducted some bilateral planning for the Latorra Campaign, which was a joint bilateral exercise between the U.S. Marines, Army soldiers, and the Filipino Marines, moving through several islands in the Philippines. The U.S. and Filipino armed forces flew from Burgos to Fuga Island, from Fuga Island to Kaleon Island, Kaleon Island to Bosco Island, and then from Bosco back to Burgos in a local snorte within a span of four days. This training, specifically the Latorra Campaign, was able to show that Marines' full capabilities during a series of events throughout the Latorra Campaign not only improved our warfighting capability, but also developed our relationship with the Filipino Marines, because we were committed to our mutual defense plans, and it shows a mutual understanding about the way we train and how we can continue to work together. The biggest lesson learned during the Latorra Campaign was that together Filipinos and U.S. Marines are a stronger team when they integrate in planning and execution. Our ability to work together, communicate with the local populace, and train together demonstrates that as a team we are stronger together.