 Okay, so in terms of this print, we've committed to 71 points and we managed to complete 32, which is around 45%. And we do have currently 15 points in review while the rest of it is either being in progress or issues that are being addressed from previous feedback. We completed five stories and we managed to squash one back. Okay, in terms of the goals in this print, we had quite a few goals in terms of delivery. So we were aiming to introduce a simplified addition of great items and categories in the great book setup page. That's currently in progress. And we also had few discussions during this print about the requirements which put these issues on hold and hopefully we can integrate them early next print. We're also working on improving the usability of the filters in the greater report and we've managed to achieve that. We were working on implementing sticky footer in the great book and most of the pages were managed to integrate it. We all need to implement it in the great import and export pages, which hopefully again can be done early in the next print. We've managed to introduce new user tours in the great book to highlight the new features introduced in Moodle 4.2. And we were working on creating a generic select and search component, which is basically migrating the newly introduced select and search components within the great book into core so that the platform generally can benefit of these new features. And we're also working on addressing few regressions that were introduced in the previous releases and some of them were integrated and some of them are still in progress. And in terms of discovery, we were finalizing the prototype around the bulk moving of items in the great book setup and that was completed. And currently we're in the progress of understanding and mapping the teacher journey when it comes to configuring an external tool in the course level and hopefully in the next print we will have a prototype ready. Next slide please. Yeah, so this is a brief overview of the aim of the sticky footer in the great book. So by implementing the sticky footer in the great book pages will provide an easy access for teachers and students to the bill of election in the great book pages. Next slide. Yeah, and I believe it's time for demos so we have prepared few demos. I will start first and then we will demo the simplified additions of great items in the group. Share my screen. I hope you can see my screen. Okay, so first I'm going to demo the sticky footer so currently I'm in the user report in the great book. And once I select the user, you can see that at the bottom of the page there's a sticky footer where all the actions available, such as in this case is the navigation. They're available. So previously we had a big problem because they were not very easily easily noticeable because they were placed at the bottom of the page and users usually would have to scroll down the page to use these actions. But now they're always available to them. So we've done something similar in the single view report. So once let's say let's select the great item and you'll see all the available actions again in the sticky footer such as the navigation records per space selector and the safe action. And that's pretty much it around the sticky footer and I will quickly demo the user to integrate a report. So as you can see we are highlighting the new features introduced in 4.2 which is the search filter, the initials filter and also the newly introduced action menus. So that teacher can find these new features easily. And yeah, that's all from me. I will let Ilija demo now the simplified additional grids. Hello, my name is Ilija. I'm a developer in Alpha Team and also an integrator. Okay, I'm going to share my screen now. So the screen and share. Can you see my screen? Yep. All right, so I'll quickly go to the previous page how it looks like an integration. So this is the add great item form. It's on separate page. So you leave the page and when you set the changes you are directed back to a great report page or setup page depending where you started. And it's quite a few elements there which might be quite confusing. And some of them are hidden by default like they're advanced. And we're introducing a new model which is going to show only basic fields. And it will have a link. We do the old page with all the fields that are available for this for great item. So we're going to support actually both. So we have a model with basic information and the old page with all fields available. The initial prototype, we're trying to make it a model first, but since there are so many fields and it's kind of a scrollable model. So we decided to make this trade off. And yeah, this is it. So everyone, any questions? Yeah, it's wondering, does the information persist in the modal? Like if you type in the name and then click show more to transfer over to the form. Yeah, the plan is to carry over the data to the advanced form. Yeah, sorry. And Carlos and representing the movie steam on the LMS educational solutions and I'm going to provide a quick date of the work done during this spring. So next slide please. Reviewing the spring goals we are very satisfied with all of them only we have moved the effort of the study of the open batches 3.0 specification review for the next spring to give more strength to the next spring. And also to give more strength for the MWA study project. So this way we'll be able to create the statement of work for the next spring and start working on it. Next slide please. So repeating in detail the work done in the MWA project, a prototype has been prepared and technical studies being presented to MWA right now as I said before. Also the proposal has been shared with Luigi Sansonetti, the initial reporter who today is not able to attend the MWA meeting and he has given us a nice feedback and congratulate to Sarri and Julia for the proposal. In the slides you have all the links to the prototype also to the affinity map created by Julia and Sabia with all the core activities and the completion of the data that each activity has. And also I would like to summarize the main goals of the project. One is to let content creators have been able to define the default course completion criteria for all the activities and resources in the third site. That's mean that when the teacher start a course and create any activity he doesn't need to go to the completion criteria default to create all the settings for this course for each course. So it's going to be nice this also we try to create more intuitive description of the criteria for each activity and results by progressing this cluster so we are not going to present all the settings for each activity. So it depends on the settings that you are going to check this going to show more settings or no. And also as I said teachers will no longer be burdened with the task of configuring completion criteria setting for each activity. Next slide please. The viewing the work done in the maintenance of our components we have priorized some of the issues that we believe will help a lot with the community. You have in this slide all the list of the issues that we're working on, but we will like to highlight some of them. So what is about the scroll bar on the course page so it is going to pay issue that we have with the scroll in the content and we are not using the scroll of the process. That's mean that when you go to an activity and back to the course content your place on the top. So we are fixed these after a lot of discussions with UX we decide to add the process scroll bar for the content. So that's mean that you can go to the activity and back to the course and place in the same point that you were before. Also we have worked to solve a problem with their reports and X API with the effect the activity that affects a set of five or six issues is super. It's hard to work on that because sometimes we need to decide if we are using the standard X API in the right way or is if I think he's not using the standard X API so it's difficult to work on that but we are finding a solution. Finally, we highlight the work done to improve the performance in the mode level of data when you have a site with thousands of levels. Right now it's super fast to upgrade. And also we apply some UX little wins with adding instructions to survey was a progression also to move the role remaining settings from the course settings tool. We have a participant role page that we tell things that helps a lot of the community. So next slide please. And finally, as I mentioned at the beginning in the activity cars program we have work on lighting the foundations, the technical foundations to be able to build a new activity cars. So we apply new styling of the CSS during this spring. Also we improve the after link created a new budget integration and help a lot of the community plugins to do the things more easy with the after link. Also we've reintroduced the group mode icon. Right now we already introduced but but for the next spring we are going to add a new drop down component on the group icon to let change the group in the course content also is going to happen with the next spring. And also we are working on two proof of concepts. One is about the new drop down component that we need. And other is to provide a new way to go directly to some settings of the quick forms collapse all the settings that you need or hide all the settings and just to show the settings that you need in the quick form. So it's something that we need for the next spring. And also you have here the prototype and instructions to see the prototype we are not showing the prototype today. We prefer to show a little nice demo, how we are progressing with the project so next slide please. And it's time to the demo so right now or super Miquel is going to show us a little demo about the new styling with CCS cars and how we are progressing with that so Miquel over to you. Hi everyone, Miquel here. So let me share super quick. So this demo is more about study the rated with and with Savina presented a super presented. And last week in the US chapter about the new activity cars UI. And yeah, I'm showing how those mockups are starting to become a bit more real. So we have here and it was with with different examples of activities from the simplest one to and we are adding, you know, some extra information step by step. This could this will be the simple example of an activity and everything is working just as before, yeah, we are just moving things around and making it like a different. So we are adding here the completion, an example with a super long name, super long name with completion. And then you can you element here. We are now adding these states in just just below the name in just one line as commented. As Carlos commented, we have the group mode here, the new visibility is, especially also below them. The name, we have these new tooltips for the, the planning type here. Now, in this new section, we will have some examples with also with description so cars are becoming more and more, more big. And yet, this is how it is played is becoming real right now. Some examples with images in the description with restrictions. And lastly, a text and media examples over here that displayed a bit different and the new after link that is displayed now at the bottom. And this new element that it is about over here, for example, to show the post. And just to show you how is display in low resolution devices. And we can, we can show here how everything is displayed, you know, in a better way when we have less space over here in also like super complex example that name dates a grouping completion description and and everything. So, yeah, that's everything from me.