 Hi, my name is Tim Lennon. I'm the CTO of the Drupal Association, and I'm here to give the monthly Drupal.org update. We thought it would be good to try out a video format for giving you our update on all the work that we've been able to do as the Drupal Association engineering team over the course of September. All of this work has been enabled by our very generous supporting partners. It's their support that makes it possible for any of this work to get done. The funding from our supporting partners directly supports the Drupal.org engineering team. So I'm personally grateful for everything that they have enabled and all the great work that we've been doing. The first update that I'd like to give is about issue forks and merger quests on Drupal.org. So back in 2018, we announced that we were moving the contributor tools on Drupal.org over to GitLab. And we've done that through a phased rollout process. So initially we moved over all of the repositories where the code was hosted, but it was sort of a transparent plus time and scenes feature. Then we enabled code viewing and code review tools in GitLab and we've been enabling additional features ever since. So the last major effort has been to turn on the ability to work in GitLab workspaces to make an issue fork to do your work directly in the GitLab UI and then create a merger quest and tie that all into the existing Drupal.org issue queues. So starting actually just after Drupal.com Global, we began the beta process for issue forks and merger quests. So we've had more than 150 contributed projects that have been using it in the beta test period and a number of people using it in core issues as well. So I'm super pleased to announce that we're going to be taking it alive across all projects and all core issues on November 10th of this year and going out of beta. So that should be a really great enhancement for recruiting new folks into the community and for making contribution easier for people who are used to the sort of merger quest pull request workflow. It should also be easier for less code savvy contributors who are going in to add either small spelling corrections or doc block updates or things of that nature. To do so without having to use local command line tools or anything like that. So it's really great. In addition to that for core issues specifically we partnered with tugboat QA and we're offering live previews of the merger quest code in a spun up Drupal instance for every core issue as well. So that's going to be a really great addition and we're looking forward to getting feedback from our core contributors about how that's supporting their work. The second item I'd like to update you all on is the lazy load initiative. So you may have seen something about this on Twitter. But basically the Drupal Association has partnered with Google to focus on improving performance of Drupal and thus performing performance of the web overall. So for our first foray into this collaboration, we decided to focus on some low hanging fruit. So lazy loading as you probably know Is an HTML attribute that can be applied to images and actually a couple other kinds of HTML tags and let's the browser decide, okay, we can load these images last during the page load or we can even choose not to load them until they're in the scroll window. So this creates a fast First contentful paint for web pages and we've been able to enable that for all image handling by default in core And that's been committed to core. So we're celebrating the success of that initiative. It's going to be released in Drupal 9.1 which comes out December 2 of this year. The third update that I'd like to talk about today is composer to support for Drupal.org packages endpoint. So as you know Drupal.org maintains a composer endpoint. For all of the Drupal projects that are hosted on D.0. So that's there's more than 40,000 D.0 hosted projects in the contrib space plus core And obviously people have been using composer version one to manage Drupal sites throughout kind of the Drupal 8 and early Drupal 9 release history. The composer team has been working on composer to which has incredible improvements in speed and efficiency. For running composer, which will make it work much better in shared hosting environments for smaller users make it easier for international users to just run composer in their local development environments. And basically just make that whole process faster and easier as well. So I'm super pleased to report that updating Drupal.org's endpoints to support composer to is already complete much way ahead of schedule. So you can already use all of those advanced composer to features when you're building your Drupal sites and they should all work for you just fine and and make that development process easier. Another update that I'd like to give in September, we had a second auto updates contribution week. So this is where The Drupal Association brought together Drupal core contributors contributors from type of three and contributors from Joomla to all collaborate on the update framework. That's actually an acronym to UF And implementing a version of the update framework in PHP. So this is an enhancement to the way we securely deliver updates and kind of a foundational piece of the auto updates initiative. So this continues the work that we did in the contrib space sponsored by the European Commission last year and is on the road of adding this auto updates feature into Drupal core Finally, we're going to begin doing some new work to help onboard contributors to the Drupal project. So we want to begin acting as matchmakers between people out there. Maybe you are watching this message who are interested in contributing more to to the Drupal project, but maybe don't know where to get involved, what initiatives are on the table. Or just how to get started. So we've done a little bit with some initial partners to sort of pilot this process, but we'd love to work with more folks. So if you yourself are interested in doing more contribution or if you have an end user client who you think might actually be interested in contributing back to Drupal. We'd love it if you'd reach out to us. You can contact me Tim at association dot Drupal dot org and we'd be happy to take it from there and get started. So those are all our updates from September from the Drupal Association and engineering team. Again, I want to thank you all for your support. It's what made all of this possible and I'm looking forward to getting touch with you again next month.