 Hello, OLE representing rural communities. So I haven't got a lot of hard data, normally I've got all the spring data. And the reason for that is that we haven't quite finished the spring because we started the day late because of me being unwell. But we're almost there and a few items. It doesn't look that good with the in progress, but actually the in progress is almost there. So the download sites migrated and updated. This is not done because it's going to happen just after the minor upgrade on the 12th or after 12th of June. So that's planned for next spring now, but everything's pretty much ready. A lot of work has been going on this spring and fixing any things that we taught and a lot of work together. Proposing a solution for searching and filtering experience for the plugins directly for users. We'll talk a little bit more about that in the slides, but this has progressed a lot because, but it's the first time we're going to that process. So it's taken a little bit longer to set up the how we're going to consult the users around this. So the idea is that hopefully the first week of next print will have some prototyping going on so we can do development on that aspect in the next print as planned. Improvements to the user interface of Moodle org loads of things that we'll demonstrate in a minute. We'll talk us through it in terms of user interface. I've all done brilliantly. So developing a plugin to remove active users accounts and so that's been done and tested and staging. So it's kind of almost there at the moment and will be actually completed next print and creating the Moodle org active user reports. That's working fine because we're now using the default Moodle site statistics for user active logins, which is very reliable and we're happy we found that basically. And the last one is the one that we didn't complete this spring and will be completed next print. Next slide please. So I probably if I is here, I'll let her introduce these changes. Thank you. Hello everyone. This is Aya. I'm a developer in the community. And I will take you through some of the Moodle org improvements we have done this spring. So we have now an improved look and feel for the statistics we have in our Moodle org front page. We have linked it to the original stats site for Moodle org. We've also changed the plugin title. The plugin title was using a font that wasn't very clear in some letters. So we changed that and it's more accessible now. Something else we have worked on is the metadata for whenever you share a link from Moodle.org, it was not showing the correct Moodle logo. This is now fixed. And we've also updated the content translation plugins so that whenever there is an updated content on our Moodle.org site, you don't see the outdated information or content. You now see it in English until a translator is updating that and adding the most recent content. And we have updated some content in Moodle.org for the roadmap and feature projects. Next slide, please. So this is the stats on the front page. It's now linked and you can go to the stats site and see the whole information. Next slide, please. And this was the changing of the title. It's now more accessible as you see in the below image. Next slide, please. And this is the metadata change. It's now showing the correct Moodle logo for whenever you share a foreign link. Next slide, please. And this was the change in the Moodle roadmap content. I think you would have more information about the site. I mean, it's just updated and now we're going to make sure every kind of planning week we've got all the content updated in there. Great. Thank you. Next slide, please. I think back to you. Federico, if you're here. Yeah, hello, I am Federico. I'm the UX designer from the community team. Yeah, I asked Aureli to make like a quick jump here to basically to speak about the progress so far because that screen show that you see there is basically a link for the users on the plugin directory so they can join to an activity to share feedback and how they use the plugin directory. So this is like the first step on how we can improve like real, real traffic on the site to improve the experience on the site because we wanted to improve the point directory and we have different solutions for it, but we wanted to gather some user input. So definitely this is like, it's a big step because we're getting input from the user. So we set like different tasks and like the results we don't have like many users going through all the activities so not many users have actually finished the usability testing, but definitely we are learning a lot like what kind of challenges we share with the community and how they give feedback to us so we can we can actually improve it so definitely is a big step forward and I hope like we can actually bring this process on how we can gather feedback from the community and this being part of the actually design process and so we are not going actually slow. This was the first time and we did some estimation but it was a bit hard on the start because we have to do many things for the first time. But definitely we want to bring this into a smooth design process so we can actually improve the site to build the feedback and we have feedback, a few users not many but definitely has been like super super useful and it's really nice to see feedback from the community members and to see that they are like keen to help. So that's really nice. Yeah. Thank you. I think we have to do early. Maybe we have another slide. It's probably. Just the whole teams demoing today is not me. Yeah, hello. I'm Victor from the community team. The model or has a bus user table around five million users with which has been causing challenges in terms of managing users and running pays in a tiny manner. Our first action was to create a specific and isolate the script to remove a significant number of users that are already deleted, but who have had no duty on the site. So it's safe to remove them. And we are also being working in a proactive manner to implement a plugin that will continuously remove inactive user from the system. And the development of the planning is nearly complete. You can see that the workflow that it will follow and we are now on the final stage of testing before we can try out in the same site. And by regularly removing native users will be able to keep the user table more manageable and should better performance for all users on withdrawal. And next slide please. As already mentioned before we are now on the final stage of preparation to proceed to the with immigration shortly after the next minor release next week. So long time will will be necessary to meet rates and statistics and a few essential database tables, but it should be couples of hours and we hope. And we have already set up two new sites on our Kubernetes infrastructure. This size, these sites will host the moodle instances that users will access to download moodle packages. Additionally, they will serve the as the platform for our updates API and will store certain static files. After we have this new infrastructure in place, the current download server will be namet packaging and will be dedicated to just to packaging the creation of the packets and mainly will serve as a file server. This separation of tasks will enable us to optimize the performance and streamline our operation is a minimize cost. Well, that's me over to you. Well, doesn't have any Western.