 I'm Remy and I will present this edge team functional update and the edge team lead. So let's start with the details about the quality department. So the quality department consists of two teams. One is the edge team which was created in October 2016. The focus of the edge team is to increase the developer's productivity, improve the development process and workflows, and increase the quality of the code base and its maintenance in the long term. And the other team is the QA slash test automation team which doesn't actually exist yet but that way we are hiring for it. And the focus of this team is to improve the quality of the product in itself, mostly with end-to-end testing and automated testing and QA process in general. So for now the edge team is obviously taking a big part of this QA test automation team since we are still in the hiring process for this new team. And that's it for this precision about the quality department. Now to know our accomplishments. So I'm happy to welcome Jacopo Beshi to the QA team. He has contributed a lot of great features and also refactoring like backstage changes in the past year. So welcome Jacopo. Regarding community merge requests, I'm also happy to announce that we merged 90 merge requests from the community in 10.5 while we merged only 43 in 10.4. I think the reason is mostly that the back-end and front-end teams are doing an amazing job at triaging and reviewing and merging these community merge requests. Know that it's part of their Q1 key result. The interesting thing is that the backlog of community contribution has not decreased that much. That means that the community is contributing more than before. So that's a great news. Robert did an amazing job on the 10.4 release as well as Luke and Marine who was supervising them. So 10.5 was a great release from the perspective of the risk management. Then we merged 73 edge merge requests which is quite big compared to the size of the team. And given that Robert was focused on the release in January and still focused, but a bit less. And the last point is that I'm also happy that we already achieved, I estimate that we achieved 56% of the Q1 key results in 47% of the time of the quarter. And if you want to look at the details of these OKRs. So in the QA estimation, OKRs, we already achieved two key results. And we are already progressing on three other ones. I want to give a shout out to many people who contributed to QA that wrote a new QA test. Gregorz obviously was doing a great job at reviewing and leading the QA framework for now. Michael, Mike, Gabrielle, Philippe, Stan, Eric, Brett, Jenshin, Robert. And all these people contributed a new QA test in the past few weeks. So we are in a much better place on our QA automation effort. And yeah, we were able to make a Github QA production ready in January thanks to this hard work. So that's awesome. And on the edge side of the key results, I'm happy that we already started on all the key results that we planned. We are already making great progress on some of them, like in average, and the CE pipelines are already taking only 30 to 35 minutes right now. And I'm very confident that we will achieve an average version below 30 minutes at the end of the quarter. And yeah, we have already started the other ones and we are progressing well. So I encourage you to check out the links for the details. Regarding some concerns, so Mark will be a RIS manager for the 10.5 RIS in February, so right now. So that will obviously increase his triaging and bug fixing power. So I encourage everyone to try to triage a few issues every morning as a routine. And Robert will also focus on the release for 10.6, 10.7, and 10.8, so in March, April, and May. So that will obviously remove some productivity from the edge team towards the Q1 key results. But I think we are still in a good position to fulfill at least that. And yeah, so that's it. If you have any questions, let me know. I've also added some resources in the last slide. So I will check out the chats. If you have questions, don't hesitate to open your mic. So are we getting more contributions because a few contributors are contributing more or because we have more contributors this past release? Yeah, it would be interesting to see. I didn't compute this kind of statistics, but briefly I just, I think that we had a lot of documentation fixes from various contributors. So I think that's good. And we also had some recurring contributors that like George Tsiolis, who is from the community, is on fire. You can look at the merge requests that are open and that are merged. I think he has like 20 open merge requests, something like that. I don't recollect exactly, but we, so I think it's both of this. We have some people that will just contribute a small fix one time and people that are on merge requests free, basically. But that would be interesting to have more detailed statistics, obviously. I will try to gather that for the next update. You can try issues from here. Anyone can do it. Yeah, thanks for giving the link, Sean. Everyone should keep this link in their bookmarks. Yeah, I don't see any more questions. So I will wait a few seconds if anyone has anything to ask. Yeah, otherwise I will give you a 20 minutes back of your time before the team call. And I will wish everyone a great day and see you in five weeks. Bye-bye.