 Welcome. I'm Carrie Lucina, the Director of Revenue at the Drupal Association, and I'm being joined by Tim Lennon, our CTO, and of course Heather Rocker, our Executive Director. Thanks again for tuning in. First, we'd just like to do some housework and just saying you can stay informed with us throughout the year. You can follow along by reading our monthly supporter email update where we talk about all the great work that the Association has been doing for the previous month. You can follow along on Twitter at Drupal Assos. You can join the new DA Slack channel, Supporting Partners. If you're not a member of that yet, please reach out and we can invite you to that group. And you can always contact your account managers, myself or Delana Lay. So the agenda is going to be some Drupal Association news from Heather, DrupalCon updates, and then a Drupal.org and engineering update from Tim. So first, we also just want to say a huge thank you to all of our supporting partners. Without you, none of this work would be possible. Also, thank you to our brand new supporters. It's always really great to see new names on this list. So welcome to CyberDuck, Unik, and Web Solutions Agency. And now I'll hand it off to Heather. Great. Thank you, Carrie. So one of the most exciting things that we wanted to talk about today was the slate of new board members that will start on November 1st and join our existing board. Wanted to give you a brief overview of who those individuals are and you can read more in depth on the blog that's on Drupal.org as well. Many of you know Leslie. What's great about Leslie in particular is how much community membership experience she's going to bring to the board as our community elected board member. Very excited that Leslie is going to be with us and excited to hear her input on how we can best support the community as we move forward. Grace, formerly with Microsoft in particular, she was also with my child's favorite thing, which was Roblox. And she is now at MongoDB. And so she brings to us great experience in developer relations. She's really going to help us from a strategic perspective. Owen has great experience as well. I keep saying great experience because they all have great experience. He comes to us with not only a good business background, but he's done a lot of work in the community around associations and camps. And that's a huge initiative that we want to be better supporting as we move forward. And so from a strategic standpoint, he's going to bring some good advice to us as we look at how the DA can support those initiatives as well. Lowly is here in Atlanta with me. She's with Equifax. I've known her over the years for her advocacy with women in technology, but she's also got really good experience in content management and brand promotion. And so we'll talk about the things that we mentioned in the webcast, which was around getting outside the Drupal bubble, helping other people know what we do and spreading the word. She's going to have really good input on how we can do that effectively, in particular with enterprise large end users. And Ryan, if you don't know Ryan, you should get to know Ryan. Not only is he a longtime community member as well, you may recognize that he has served on the board before. So he's been a community elected board member that has been reelected to the board outside of the community spot, which went to Leslie. And Ryan has agency experience, a lot of Drupal experience, and is very knowledgeable in a lot of things. And so we're glad that Ryan's going to stay on with us. And again, if you haven't met any of these new board members, most actually all of them will be at not only Drupal Camp Drupalcon Amsterdam, but in Minneapolis as well. So that'll be a chance for you to say hi in person on the road. So in an effort to get out of the office and into the world, we've been doing some fun things. In particular here in my own backyard, I got to attend my first Drupal camp. And Carol, who's our new director of marketing and outreach flew down to Atlanta to go with me. So we got to spend time with the fine folks at Drupal Camp Atlanta, got to see how the volunteers not only organized the effort, but how the sponsors participate. And if you haven't been to a camp event in your local area, I highly recommend it. It's a great way to not only get to know the local Drupal community, but to see how as businesses you can partner with developers and other Drupal businesses in the area. And then Tim and I got to spend some time last week in the posh settings of Google, where we were invited very kindly by Google to participate in the CMS leadership summit. So this was not only a good opportunity to hear what's happening in CMS as a whole, but we really got good time to collaborate with other CMS leaders and to share best practices in a few woes that we shared with each other as well. And so everybody's got challenges. We're not alone in that, but it was great to spend time with that community and see how we can better collaborate. And I will let Carrie talk to you all about our group of events coming up. All right. So well, first and foremost, we will see you soon in Drupal Con Amsterdam. Drupal Con is happening at the end of the month. Thanks again to the support of our partners, Coney Congress, and obviously all the amazing community volunteers who make Drupal Con happen. A few things that we wanted to highlight that are happening that week in Amsterdam are the supporting partner roundtable. This is an opportunity for us to come together as a group to network and share knowledge and discuss different ways that we can contribute to Drupal and all create more business value. We're working with a new format where we'll pre-sign groups and topics of discussion so people who meet together as a group and come prepared to dig into more meaningful discussions since it is kind of a short amount of time together. So please keep an eye out for those invites later this week. There's also that will be followed by the VIP sponsor and supporter reception also happening on Tuesday at 6. These are all in the conference center and you should have already received that invite from Coney. If you haven't already, please let us know. We also wanted to highlight that there's going to be a marketing contribution sprint on Thursday. So this is an opportunity to be a part of the team that volunteers to work together to create a lot of the stuff that you've seen happen around promote Drupal. They're developing a marketing strategy and materials to help the community at large grow Drupal adoption. So if you feel like you can help and contribute and want to join in that great work, please find us on Thursday. And then we have Drupal kind of Minneapolis happening next year, May 2020. A few important dates that are updated. We've extended the call for paper deadline. It was originally coming up really fast October 16, I believe. But we want to give everybody more time to submit their sessions. So we've extended that deadline all the way out to December 4 to give you plenty of time to participate and get involved. The early bird ticket registration is still November 22. And then we'll announce sessions on February 21, 2020. There are also a lot of ways to get involved. I included this link here. I would highly encourage you to just kind of check it out since it does get updated regularly. There are some speaker and session team members needed for various tracks. So if you are an expert in any of these track subjects or folks on your teams are, we would highly encourage you to check it out and volunteer to help shape some of the content and sessions around these topics. And now I'll hand it over to Tim. Awesome. Thanks, Carrie. So I'd like to do something slightly different for update from the engineering side in this update just because there's some news for the Drupal project itself and not just the sort of Drupal.org side of things and the association engineering team side of things. So there's a few items that I'd like to touch on. The first one being that Drupal 8.8.0 is almost here. So the alpha window for this release begins the week of October 14. So that's the point at which we essentially have a feature freeze on what's going into Drupal 8.8. And then we do the rounds of testing. Those of you who might participate in the kind of community beta testing initiative will likely be contacted towards the end of October to be asked to participate in that process for this release. The actual full release of Drupal 8.8.0 is scheduled for December 4. So before the end of the year, we'll have this next minor release with a whole slew of new features and improvements. I'll talk a little bit about those. One of the exciting things about Drupal 8.8.0 is it's kind of the last regular six-month release before we get into the 9.0 release process next June. So it's a really exciting moment. It's kind of putting the cherry on top of the Drupal 8.0 cake before we move on to the next one. So that road to Drupal 9.0, this is a little bit of a hard to follow image, but it's useful. If you check out Drupal.org slash road map, you can take a look. What you'll see is that in that December release window at the beginning of this chart, that's when 8.8 is released, 8.7 received security coverage all the way until the next release window six months later. And that six-month rate of release will be both the release of Drupal 8.9.0 and 9.0. And those will be essentially feature identical except 9.0 will have the backwards compatibility break that represents what that next major version means. So it's really exciting times. There's a lot more information about this release process. Again, on the roadmap, and there will be some blogs and other information coming out from the Core Maintainer team fairly soon. One of the key things that's happened in 8.8 that I'm personally really proud of because my team was heavily involved is there was a strong initiative to create better composer support in Drupal Core and to ensure that whether you started off by using a, you know, a tar or a zip file to download your site in sort of the old-fashioned Drupal 7.0 way or whether you used composer from the beginning, you're not going to paint yourself into a corner if you need to later on depend on a different library or require a composer workflow. So beginning with 8.8, it's going to be a really clean, easy to manage situation for people who are using composer or not yet using composer or thinking about using composer with their site installations. And all of the work of this initiative, which has been one of the major core initiatives, all of the key work is already committed. So we know it's going to make it into this release. There's still some work going on in that initiative, but it's really just little bug fixes and some documentation changes and stuff. So we know we've hit that milestone and that's awesome. So from there, I want to talk about the sort of regular Drupal.org engineering updates, but you'll notice that there's a lot of overlap here with Drupal itself. And that's because in kind of this modern Drupal 8.0 coming up on Drupal 9.0 era, you know, it's a services connected product. Drupal calls home to Drupal.org to get a lot of related things that it might need. And so Drupal.org in addition to being the home of the community is also sort of an essential service provider for Drupal itself, ensuring that that software works. So related to the topic above, we are updating the way that we package the releases on Drupal.org to take advantage of these new features committed to Drupal, again, so that whenever someone comes to Drupal.org to download, they're already ready to go with the sort of best practice scaffolding set up to use Composer in their site development in the future. Finally, or actually not finally in addition, we're also working on all of the infrastructural support for the automatic updates initiative, which is ongoing. So it's going to reach a first milestone as we come into Amsterdam in the end of the year, but there'll be ongoing milestones and additional enhancements that are still needed as part of this initiative. However, one of the key elements of all of this is ensuring that we can deliver trusted secure update packages, because as soon as we start automating anything that changes the code base of the site, we really want to be sure of that. So there's an issue you can look at if you're if you want to nerd out about security best practices. But to put it short, we're using sort of hardware security management key signing and package delivery and validation and automatic expiration, all the sort of cutting edge security stuff that will hopefully ensure that Drupal's security process is one of the most robust, not just sort of in the PHP world, but in the sort of CMS world in general. Similarly, of course, once we have that security infrastructure, we're actually going to have to serve the automatic update packages. And so when we're generating an automatic update, what Drupal.org is going to be doing is actually taking the current the new updated version, the previous version and generating this sort of meta patch of the difference between the two to deliver to sites through this automatic update service. So we're putting in place the infrastructure to generate that right now. And get us ready for this new set of features. Finally, we're doing a lot of work in coordination with the sort of Drupal mine readiness initiative, mostly led by Gabor. But in particular, we're trying to help audit and provide test data to all of our module maintainers to know whether or not their Drupal eight modules are ready for Drupal nine. And this is really exciting. There's a big difference between the transition from seven to eight and eight to nine for for a Drupal eight module to be compatible with Drupal mine. It just needs to avoid use of any of the sort of deprecated APIs that we're maybe no longer using in the nine release, which is a much easier lift. And as a result, as we started doing this automated audit, more than 40% of the contributed projects for Drupal eight will already work. They're already compatible with Drupal mine. And that was with essentially no effort required on the part of the module maintainers. And so we're continuing to regularly run this. This number keeps going up and up and up as as the Drupal nine readiness team alerts folks as to, Hey, here's the here's the major, here's the, the major reason that modules might still not be compatible. And usually it's just small little API changes that can be fixed pretty quickly. So we're really hopeful, actually, that there'll be a lot of almost a majority of Drupal eight projects ready to use out of the box with Drupal nine by the time we hit that release. So that's very exciting. And there'll hopefully be more news at Amsterdam and you can follow along at the at drop is moving Twitter handle. I also just want to remind everyone not to forget when Drupal seven and Drupal eight reach end of life and again, some of this release information. So again, Drupal seven and Drupal eight are both scheduled to have their end of life in November of 2021. So that sounds in some ways like a long way away and in some ways like it's right around the corner. So it's not too early to start thinking about your migration strategy into Drupal nine. If you're already on eight, it's going to be easy. It's not going to be significantly harder than the last, then then upgrade in a month to Drupal eight dot eight, it won't be won't be my very different. If you're still on seven, you may have some more work to do. So there will be extended support available. So if you search for say Drupal seven extended support, you'll see some information about the vendor provided extended support beyond this timeline. But either way, we're excited for Drupal nine's release again, June 2020. There is a fallback date. If there was some reason why we had to push that and that would be December 2020, but it's looking pretty unlikely that that's going to be necessary. So so yeah, just make sure to save those dates and be be ready to go with all of your own and your client sites as we continue moving forward. And thanks for your support of the engineering team without the sponsorship of supporting partners. We couldn't do any of these things that not only provide value to the community and the home of the community, but also are now increasingly providing direct value to Drupal itself. Carrie, you want to wrap us up? Sure. So thanks again for tuning in and obviously for all of your support. There are so many ways to stay informed. But we also just want to remind you that we're here. If you just want to talk, give us a ring, give us a shout. You know, even if you're not at Drupal con in Amsterdam or Minneapolis, you know, we'd love to hear from you. So thank you again. And we'll be sharing out this webcast for everybody who can't join us and reach out if you have any follow up questions. We do have a few minutes where we can answer any questions that you might have. I don't see anything yet in the Q&A chat. If you're looking for that Q&A function, it's again in the Zoom toolbar among next to sort of the where the mute buttons and things like that live. There's a Q&A button to open that window if you want to ask any questions. Or if you want to just drop any more more casual comments and thoughts, you can also use the chat window for that. One thing I wanted to throw out too, which is me asking a question of this group, but along the lines of us being out and about and advocating for Drupal and growing awareness, if you as a business have ideas about where you think Drupal should be, where the DA should be, where should we be speaking, what event should we be attending that you think would help not only the DA community but help your business as well. Let us know because we'd love to partner and be able to attend more things and get out there. But sometimes you're the best, you know best where we should be and what would help. So send those ideas to either Kerry or Delana. Feel free to reach out to me as well. I'd love to hear from you. Awesome. I think we're still quiet on the questions front. Kerry, do you want to give it more time or should we call it here? Yeah, I think we can probably call it. Right. Thanks again, everybody. We really appreciate your attendance. Thank you. Thank you, everyone.