 This is Aya, I'm from the community team. So for Moodle.org, we had two fixes, the sprint. One of them was the drawer toggle icon. It was overriding syntax. So this is now fixed on production. The other change is that we now have a new photo for the MUA banner. It's not yet deployed as we're still trying to make it look the best on the banner. So these are the two changes that happen in Moodle.org, the sprint over to you back already. Can we have the next slide? And I'll pass over to Federico on this. Hello, I'm Federico, I'm the UX designer from the Moodle community team. For this spring, we were working in, as we already said before, in some workshops with members, with the plug-in developers from the community. It was an amazing and a lot of piece of work because we run four workshops when we bring some of the problems that we're having with the plug-in directory. And we make some votations. And then we, from the most developed problems, we bring some of the solutions that they wanted, maybe, to share with us. So it helps to the brainstorming before. And then I worked with Arlie and Carles, and also Victor and Ayas, a more technical part, on bringing those problems and grouping them and making sense of all this information. So for the next steps, we want to hope that, as you see in the image below, is we put it at graph to see how we can have the most impact possible in the easiest way possible. So definitely, a lot of these solutions are really broad. But we want to make a clear focus and define them in a really clear way so we can actually have impactful experience inside of the plug-in directory. But be sure that this is the solutions that the users really want to have. So we will validate with them and continue in the process to be sure that our work is worth implementation. So we are not making the experience worse. Some solutions were super clear, and they have been there for some time. And some of the community members, they help us to set us clear that. But some of them, we want to explore a bit more so we can bring much better experience for the developer that is updating plugins and for the users that they want to install plugins from the plug-in directory. So yeah, it's a lot of work. Thank you. Thank you, Federico. Next slide, please. I'll try and keep it short so we have as much time as possible for the next team. So what we've done as well, this print was to upgrade all our community sites to the minor version on Moodle Association site, Moodle Association site to the minor version. Next slide. So these I'm going to read because this is not my specialty and Victor's only. But basically, this is what's been done so far on the server migration from the download site. If you're interested, there's the epic number on the slide. And we've got also the work in progress there. So in a diagram above at the top, the current status, the code packing and Moodle instance are in the same server as Etna. It's a Moodle 3.5 and can't be upgraded because it's an old server. It's the only site not hosted in a Kubernetes infrastructure. And in the diagram below, which is what we're moving to, we've got a new architecture, one server only to create and share the packages and the Moodle instance and the APIs in the Kubernetes infrastructure. We will store the packages in the PetSner because of the high data transfer cost download for AWS. The other thing that has been done as the screenshot shows here, we're also working on making sure the theme from Moodle.org, the customized theme is also applied to the download site. So it's the only site currently that hasn't got the same look and feel as the other Moodle community sites. So today, I'm going to show you the filterable events plugin that we were working on on Mobile Academy. Basically, the plugin purpose is to enable the users to filter events by their own spoken language or a certain host they are looking for or maybe inside a certain course. I will share my screen and show you super quickly a demo. So basically, the plugin is using a lot of the core calendar Moodle code. It's similar in a lot of aspects except that we are enabling some custom fields on the events so that the user can look for events. So basically, the plugin starts here in the home page of Academy site. We have the upcoming filterable events plugin that is showing the most recent events that are going to happen. The only difference is that we are prioritizing these events by the host, which is Moodle Academy in this case. And then when you go to the main plugin page, you can see it's the same layout as the calendar. The only difference is that we have a filters component here where you can filter by certain things and these things are fetching from custom fields. So the new events that we have created has its own custom fields where you can dynamically add a new one here and it will automatically be appended in the filters for it where you can filter all the events by these information. And we have created, as I told you, we have created a new instance or a new event type. It's not related to the core calendar event and it has its own custom fields and everything. We also have a past events view where you can view the events that have already passed and we are planning to add here like a show recording button to be able to see the event recording or the session recording after it has been done. And the monthly and the views are basically the same as the calendar, nothing new here. The only thing I want to add is that this model academy is based on model work place, as you know, and whenever a new appointment session is created, we observe the event of creating a new session to add the session as a filterable event. So people can also filter by it and search for them and, for example, search a certain course that they would like to see the events that are happening in this course. And yeah, that's basically it.