 So, Jota and Matt, I'm on the off team as an analyst developer that likes to do front-endy stuff. So, overall, we've had 57 points committed for the sprint. We didn't quite get there due to obviously various leave taken by the team and whatnot. Obviously, it's a very funky time of year, but what can you do? A bit of velocity change in negative, which again is unfortunate, but the upshot is that we've made a lot of good progress on our epic for the 4.2 grade book. So, those numbers are the official story, but a pair of your numbers are even better. So, there's more points there. So, next. So, what we'll try and do is assist with 4.1. Pretty sure that was the sprint. If not, we're assisting with the on-sync. Either way, we'll assist with 4.1 stuff. We'll try to do our discovery tasks and all that sort of general sort of really nailing out behaviors and whatnot for the grade book, at least for the grade report to begin with because that's our first sort of stage of the grade book 4.2 epic. We've also implemented a sort of drop-down initials filter as well as doing some stuff like groups. And also, we've been working quite heavily on the whole UX design of progressive disclosure. Everything's tighter to progressive disclosure at the moment, so we've made a lot of good progress to that. So, next. So, time for a small demo. Wow, can't wait for the curse to always pop up. Let's see how it goes. Is it sharing? Oh, yeah, here we go. All right, cool, cool. Right, so here's where we've got up to this sprint. So, we'll see if this is a grade report. Initially, you had a whole list of stuff there, like group selector, initial selector, as well as some new features in there, like this little search. So, we can say, I want to search on Troy. I'll find all users that match with the first name Troy. Say I only want to select Troy's for some reason. I really like all Troy's in my report. So, now I can select all Troy's. But let's say, I don't want to search for Troy. I want to search for something else. Maybe people that may be there at this domain. Oh, well, when I search, I can now see I'm matching on email address. This will be enhanced in the future to show both the field batch matches as well as the value that matches. So, you'll see like email address with an at email or at mail or something like that. So, this is all very work in progress. And you can show that as well. So, you'll see all people have that mail. And this also works with user identity fields. So, you'll see here, I'm showing phones, mobile phones in countries. So, I'm going to say I want to search for users with phone numbers and these two match. Let's have a look at Brita. Wow, that's a phone number. Five, five, one, one, one, one, one. Cool. Right. So, that's one part. We've now got group selectors that actually no longer show in the page. We're now in our tertiary bar. Works as exactly how you would expect. So, you can select group A, group B, whatever. It doesn't really matter. It's very cool. So, that's in keeping with group selectors that we've did in the user report and the single-gear report. So, just bringing that consistency into the greater report. And now we've got, again, this is all dev code. So, please forgive me. I've got the initials bar that is now in the tertiary bar. I won't go into specifics how it works, but it's basically leveraging all the old back-end code, but some little tweaks here and there. And it still works as you're not in love with it. But instead of doing a redirect, whenever you click on the user, you'll know you can select both values, then a press apply, and you'll see those users. Awesome. Right. Now we've got some more stuff. Again, there's not much in the base demonstration, but there's lots of stuff in the demo. So, this is where all the time is going. So, don't worry. We've got this nifty little, where is it? There it is. We've now got users per page with pagination. So, you can really just trim down the data set that you're looking at at any given time. Obviously, you can paginate between it, but it works. And then we've also got this drop-down stuff in the... I believe Billy has been working on this, so we'll be moving to a drop-down model, or maybe it's gone to icons. I'm unsure at the moment, but we've also been doing work in that area. You can also see some changes here with editing. Well, that's sort of good stuff. That's about it for me. Next is LMS Education Team. My piece. Hi, everyone. I'm Carlos. I'm the team leader in one of the educational teams visiting Europe. So, next slide, please. This spring, in terms of points and numbers, it's good numbers, because these are literally tricky, because in the last spring, we focused helping the release with the integration and completely reviews. So, it's what's easy this spring to focus more on our projects. And also, we tried to balance this time the work on the two projects that we have and the maintenance of our components, and it was good. So, let's see. Next slide, please. So, we try to make these spring goals very broadly with the spring. So, we have two bucket issues. What is the FIP with the new library, and the other is with the batch year. Later, Sara will explain a little bit more. In terms of research and design course hierarchy project, we help a lot Setara and Sabina with the research and with the design and with doing the interviews and the co-design workshop. Also, we have done some small, big wins in terms of UX follow-ups on database projects and our components. We see later. And we have advanced a lot in the definition of the bulk edition course activity project. We already have a MVP prototype, which we are going to share next Friday with the MUA. And also, we have reduced a lot of the technical debt. So, it goes through the spring. Next slide, please. Looking at the small, big wins in terms of UX, we are ready to have this new information on the dashboard. So, the users who have capabilities to request a course or create courses or manage courses, they will be showing information that can help them in the process. Also, we are in a new setting that we can, any administrator, we can use to predict the quick start guide for any URL it was. Also, we have fixed a little issue that prevented case users go to the case course and add new topics on the discussions. Now it's possible to do it. And also, we've finished some work on the UX and the reactive panel to help in with the book of the new reactive course editor that we have on the course. Next slide, please. Talking about the UX follow-ups that we have on the database project, we are ready to help the teachers to work easily in the process of adding new options in the Barker menu. And also, all of you know that the database activity has a lot of legacy goals, so we are, right now, we are working to factor the URLs to follow in the mode of coding with practice, so that's ready. Next slide, please. And finally, we are helping a lot Setara and Sabina with the discovery, research and design of the Qt hierarchy. It was super good experience working and talking with the community and you have here some links about the code design workshop that run by Setara and Sabina with the community members. I appreciate that Setara and Sabina in the next weeks are going to explain a little bit more with more details how this code design workshop works. So next slide. Now it's time for Sarah to explain a little bit more the problems that we have with HP and Badger. So, Sarah? Hi, everybody. My name is Sarah Hona, and I'm a developer and an innovator at HQ. We have faced two different problems, one of them is with HP. We started facing this problem like one month ago, more or less. Some activities and content types, like the course presentations that have been created in HP.com, they are not working properly in model because they are using a new version of the core API of the HP libraries. We contacted the HP team a month ago, but we haven't got any reply from them. This morning I realized that yesterday they released a new version because they were using a new version in the HP.com, but no new version of the libraries that we have in core were in the repositories, but they have now this version, so at least now we can work on them. We don't know their plan, so maybe we know that next week they will be upgrading the HP.com again, so probably there will be more content types, not just the course presentation involved facing this issue. The problem is that we will need probably to backport to stable because otherwise people that try to use these contents in their model sites, they won't work because they are using a higher version of the library. Next slide, please. We are also facing up an issue with Badger. It was working properly until one month or some months ago, and then it stopped working. It's not working in any model version. We are in contact with the Badger support people. We are also in contact with the IMS, one tech support people to see how to fix this because it seems that they have changed something in their site, in their servers, but it's not easy to debug. It's like we are doing our best and we are trying to find the best way to fix both issues, this one and the HP. Next slide, please. Thank you. About the course editing, while Savina is working on the new prototypes for the bulk edition, we use all those first sprints to reduce the technical depth we have in the course. As most of you may know, we implement the new course editor libraries and web services for 4.0, and because of the amount of work that represents, we cannot migrate all the actions of the course to the new system, but the new system will help a lot with the bulk editing because all the new web services are meant to be bulk by default, so you can use it as bulk or as a single activity or section use. We keep migrating all the old stuff to the new stuff, and we implement all what is the duplication of an activity. Now it's using the new web services and their reactive components. The same happens with the deletion of activity, so now it's all brand new there. About the highlight and highlight topics, we made quite a change in the way we do it, and now all the implementation of the highlight and highlight options are completely in the topics format. We did something that we need to do for some time ago, but it keeps mixing. Some of the logic was on the topics and some of the topics was in the core libraries, so now it's all moved to the topics, so that means that there's a good example on core on how to extend the actions of the course, even with a new editor. That's a good thing, and it's not about the bulk editing, but because we are there already, we also make great drag and drop files into the course, so now it's compatible also with the course index, so you can drag files directly into the course index, not only in the course content, so it's a good thing in the end. And now I will pass you to Sabina, who will show you the prototype of the bulk editing. Thank you, Peran. Hi, everyone. I'm going to share my screen. I hope everyone is seeing the screen. Okay, so yeah, as Peran mentioned, I've been working on a proposal for the bulk editing course content project, and I've got a couple of proposals that I'll be showing to the MUA this Friday, but I'm going to show you one of the designs versions that I've created. So for these, we have the bulk edit button in the course index, so all the actions that will be related to the bulk editing will be around the index. The other version that I have that I'm not going to show today will be with all the interaction from the user done around the course page area, and what I'm going to be doing on Friday with some members of the MUA is showing them the two options that I have and getting the feedback in order to progress on the design integration process for the project. So basically, by clicking the bulk edit button, sorry, because my screen is a little bit small, so I guess you will be seeing this quite small. But yeah, you have the link on the slides in case that someone wants to try testing the prototype later on. So by clicking the bulk edit button, we will have the course index items with text boxes enabled, so the user can select any item. And a sticky footer will appear here with all the actions disabled. Yeah, some of the behaviors are weird right now because Figma prototyping tool is not great, but yeah, all the actions will be disabled until the user selects any of the items. So right now we have the option to select bulk edit activities, resources, or sections. But as activities and resources have different actions than the sections of a course, the user won't be able to select an apply bulk action at the same time to sections and activities. So once the user selects an activity or a section, then the text boxes will be disabled for the other items. So once we select activities, the text boxes for sections will be disabled unless the user unselect the activities and then they can select sections. And the same will happen if they select sections. Activities checkboxes will be disabled. So once we have any items selected, the actions will be enabled. We can select all or deselect, and by doing that we will select all the activities or all these actions depending on what was the first selections of the user. And we have four main actions for activities. So we have the visibility, duplicate, move to, and delete. And I've added a five item here for just thinking on the future and in case that we need to add any action to this behavior later on, we can have more options here. So we can edit the visibility of the activity, so we can hide it from the student view, we can make it stealth. These actions that the user will see in the model will change depending on the current state of the activity. So for example, if the activities are already hidden, then this option won't be shown here and we will have the option to make them visible. And of course all the copy, all the text that you're seeing here is provisional and we'll be working with the product experience team to create the final copy. So users can select the option they want and they will have a notification that will be stick on top of the page to inform what was the action that the user just did. We can undo the action quickly if the user was making a mistake. And again, we can continue with that. So every time the user perform an action, we'll have notifications. And for example, for stealth or any visibility actions, we will have indicators on the course index and of course in the course page here. So we can also duplicate activities, we'll have the same behavior here and all the actions performed within the course index and the course page. We can also move any items and this will be having the same way that the move functionality already worked for single items in the course page. So we'll have a model to select where we want to move and again, the notification here with the undo action. And lastly, we have the deletion action with the confirmation model that we are changing, like updating a little bit the UI to match what we did with the database. So we have the danger actions in red to warn the user. And once the user have finished selecting or applying any actions to activities, they will close the filter here. And we have the indications here. So I've changed a little bit the way in which we show the stealth or hidden indicator for an activity because we have complaints already about the size of the activity card. So I'm trying to squeeze a little bit all the content and make it smaller. So I've replaced the label that we had here for hidden or stealth with an icon. But of course, we cannot rely only on icons and what we will have is a tool tip just to explain what this icon means. But this way we can save a little bit more of a space. And of course, in the same way that the activities behave, we can do the same with sections. So once the user select a section, all the activities or resources checkboxes will be disabled. And we will have just three main actions for sections because we cannot, for example, duplicate sections in bulk. But we can hide, we can move in the same way that I just showed. We see that all the actions are being reflected on the course index and we can delete full sections. So by deleting and hiding or showing sections, all the activities within the sections will be also deleted or hide or made them visible. And yeah, I think that's it from me. I'm going to stop sharing and hand over to... Which is Moodle Cloud. Thanks, Adrienne. I'm Frances from the Moodle Cloud. I'm the product manager for our team. So yeah, a lot of our work, the last couple of sprints is infrastructure upgrades and things. It's not as exciting to show, but we'll go through. Next slide. Yeah, so just a quick summary of our... We've done 37 completed issues and 12 support issues completed this sprint. Next slide, please, Adrienne. So we had quite a few sprint goals. There was a few small things in there, but there's a lot of ongoing upgrades and things, as I said before. So the new sign-up server Ubuntu 22.04 is online and on staging, which is pretty exciting. We've upgraded all of our sites to Moodle 4.0.5. The Moodle Cloud, the dataset extraction has been deployed to our staging environment. That's still an ongoing piece of work. So we'll probably go on to the next sprint. Our sign-ups upgrade to Symphony 5 is also still in progress. That will hopefully go on to staging next sprint as well. And then we'll start testing on that as well. Another thing that we worked on was we changed our large plan to be renamed to standard. It's been updated on the new landing page, which is comparing the sort of premium hosting plans as well as our plans. That's sort of refocusing on, you know, hosting Moodle in the cloud rather than just Moodle Cloud. So seeing what other options there are. So it was a decision to change that plan, which is quite cool if anyone hasn't checked out that page. Our custom domain prifer concept is online, which is really exciting, and Matthew will talk about that later. Rainmaker testing has been completed and ready for initial deployment. The last one we did have in our sprint goals was at least one customer has been interviewed. We interviewed one customer, but they were Moodle employees. It doesn't really count, but it was kind of a test first initial interview. And we're going to start that all new process in the new year when we think people will be a bit more interested rather than at the end of the year period. So next slide please, Adrian. That was just a quick screenshot of. That's the new standard name. So if anyone wants to go and check out that page, it's Moodle.com slash solutions slash Moodle cloud. And you can see the new landing page there. I'll hand over to Matthew to go through the custom domain proof of concept. And next slide please, Adrian. Hi. Well, that's going to be a quite quick thing. It's unfortunately a bit less impressive to demo than compared to the amount of work that required. The main thing here is that we can now support other domain names on Moodle cloud. It doesn't all need to be Moodlecloud.com. Well, that's the proof of concept anyway. There's some among the work that was done there was identify everything else that's going to break when we deploy this and how to fix it. So that's part of the next sprint. And also I've built an idea of the customer documentation that we need to build and everything that goes with it. So at this point, I've got a site that runs off another domain name that we've owned for a long time. And yeah, it's running on staging. I'm very happy about it. There you go. Back to you, Francis. That's it. Any questions? Any questions?