 Hi, everyone. I'm Mick Hawkins. I'm a team lead in the LMS platform team. Next slide, please. So just a summary of our sprint. So we committed to 142 points and there were 26 brought in. There were 53 completed and we've got 27 in integration and 48 up for peer review or being peer reviewed. It's about a 32% velocity, which is slightly less than last sprint. We've completed one task and squashed 15 bugs. Next slide, please. So our sprint goals this time were to wrap up the issues that we carried over that were held so that we could focus on the 4.1 release. We've made some pretty good progress in that area. I think there's still a couple hanging over or in peer review, but majority of progress pretty well. We also aim to land guzzles so that it's available for some of the upcoming 4.2 projects. That one, the development work is done and that's up for peer review. We also wanted to work on some interesting kind of medium sized issues. Since we're not running project week at the moment, just so the team has an opportunity to decompress a bit and just focus on one task. So I think that was pretty successful. Everyone had an opportunity to do some of that work. And we also wanted to stay on top of peer reviews and spend some time on out of sprint peer reviews from the community and such. And I sort of put a question mark on that one. I think it went pretty well. There's 25 issues in the sprint that progressed past peer review and two thirds of the stuff that's currently up for peer reviews already in progress. So if it's not finished today, I guess we'll be hopefully wrapped up in the next bit of while. Yeah, next slide please. And in June, our integration lead not being available. I've sort of pulled together just some basic numbers for this. I hope they're correct. So 78 issues integrated and three rejected during the sprint. There were about three integrators per week available. And also just a couple of other updates. The 4.1 on sync period ended on the 12th of December. So all issues held during the 4.1 release have now been unheld. And our next miners come out on the 16th of January. So that's, I guess, one week beyond the standard, which is pretty normal for us to do at the start of the year because of public holidays and things. So I'll hand over to Simi now, I think, to go over some of the QA stuff. Hi everyone. My name is Simi. I'm the software task engineer in the platform team. Adrian, can you change to the next slide please? So yeah, just a quick update on the QA and testing side of things. In terms of development in the automated testing, we had a recent regression in the calendar exporting that caused many CI failure builds. And also I have been working on this MDL about adding some behind improvements. And one of those is to jump directly to the user editing page without having to, like it basically removes the necessity of adding three steps. And also I have been fixing some CI failures and things like that. One good news in the QA and testing side of things is that Angelia, which has been working with us, she's an external test developer. She will be joining the team and also joining, like, still working as external test developer, but she will be helping the conversion of QA tests should be had. She will be also be progressing her work, converting UI steps to data generators. And hopefully she will also start helping with peer reviews related to testing issues. Yeah, that's the update from the QA and testing side of things. I think next is Matt, I think. Yep, thanks Adrian. So I thought I'd give a bit of an update on the Matrix Chat integration, which is one of our big projects on our roadmap. And just sort of starting with some of the things we've completed so far. And also just because I forgot Adrian's great intro, my name is Matt Parrot, I'm the LMS platform manager. Yeah, so just an update on what we've done so far. We've put together a set of user stories that cover student, teacher and admin scenarios for the first phase of this project's deliverables. So we can use them to inform what we're doing development-wise. We've also met with the Matrix development team and an architect from them, which was sort of part of verifying our approach and some of our proposed workflows for the project. The feedback from that is that we're on track with what we're trying to do, which is great. We also discussed things like access level controls in Matrix and how they can map to things like user roles in Moodle, so for teachers and students and things. The Matrix team also made us aware of some existing and upcoming functionality to be aware of. These won't impact the first phase of development too much, but they're good to be aware of and will be useful for future releases. We've done some initial Matrix API testing and verification, so the main aim here was to check that the existing Matrix API supports the functionality that we want to implement in this phase of development. So things like creating Matrix rooms, creating users, adding and removing users from rooms, that kind of thing. This again was some good news and everything that we want to be able to do from Moodle via the Matrix API is possible, which is great. We've also done some investigation around user authentication workflows and options for various configurations around things like single sign-on. These can be pretty tricky and something that we need to be aware of from a user experience perspective as we move forward. We also looked at deep linking, which is what happens, for example, when you click on a Matrix room link in Moodle via the web interface or the Moodle mobile app. Just including the different behaviors depending on whether you're on a mobile device or a web device for Moodle and if you've got a Matrix client installed on that device or you're using a web client, for example. It looks like from our initial investigations, all of those combinations can be accommodated for, but again, this is something that we want to keep in mind as we develop. Moving on to things that are in progress. We're now taking those user stories that I mentioned before and converting them into trackers that the team can start working on. Also, as Mick mentioned, we're working on implementing the Guzzle PHP library into Moodle Core. It's up here, as he said, it's up for the peer review stage, which is great. This will be used in other places in Moodle, but it's going to be really useful for talking to the Matrix API as part of this project. Finally, the next steps. We've got a UX collaboration session internally this week that will help out some of the details from a user experience perspective. Finally, getting started with the bulk of the development tasks for the project. The best place to stay across all of that is the EPIC, which is listed there. Apart from that, is any questions for the team?