 Someone give me a thumbs up if my screen is visible. Thank you. It's a full hour in here, so I'm gonna get started. Hi everyone, welcome to the group conversation with the distribution team. I'll be your host for today. And we'll go through a couple of topics. First, we are going to go through the team. We keep updating the distribution team handbook, so I would really urge you to check out our handbook and understand a bit better on what our mission and vision is and how we actually work. But I wanna say welcome to Robert Marshall, who joined us all the way back in August. The only reason why we are updating this now is our last FGU was in July. We, Robert has already hit the ground running, so he's already contributing to the team. He's almost a veteran. We do have two more open positions to fill. I do have to say that one position is almost filled because we are in the final stages with one candidate. We'll see if that works out, but I'm very hopeful. So if you still have people to refer, please check out the open positions and send them our way. Let's start talking about accomplishments. We're gonna start with the GitLab Helm chart. And I use the screenshot here from a comment by a user that is thanking quite a lot of our team. But Eric has been using our chart throughout beta, and I think it just shows how great it is to have a community out there, trying out your things, helping out. And Eric was one of the great users we had that allows us to understand better use patterns of our users. And we did manage to get our OKR filled with our Helm chart, general availability, which was announced on the 22nd of September. We do see that the chart usage is growing. If you take a look at the chart, well, the graph below, you'll see that practically once we announced general availability, the usage spiked. It is coinciding, like this smaller spike you see here, is coinciding with being a launch partner at Google Next with, I forgot how it was called, it was Cheese KE marketplace. Yes, that was right. And we got some feedback there that we were most deployed to partner solution, which was a great validation of what we are doing there. And the amount of use we are getting is also being reflected with the number of issues that we receive from users and customers. And that is actually changing and shaping our future development. I wanna highlight a couple of items that we did here. You can find the links there. But I think a couple of items worth noting here is, while we were receiving some feedback on how difficult it is to configure object storage in the charts, we decided we are going to shift our focus from one item to simplify this setup for all of users. And as an awesome side quest, basically, we have a way of announcing the applications for our users when we make a change of something. To put this in perspective, in Omnibus GitLab, we only added this year and the package has existed for four years, five years almost. And with charts, we added that even before the general availability was announced. So we did learn from our experience. We also are trying to stay on top of development inside of Kubernetes world. And we recognize that one of the items that the Kubernetes community is using more and more is an operator pattern. And we attempted to use that for our zero downtime automated upgrades. We invested a lot of work into that and you can check out this Friday's demo, which was really great and showed that we are on a good path there. We managed to upgrade GitLab without any downtime. And it was a pretty seamless experience. I'm gonna stop periodically when I see a question in the chat. So William says, got feedback most deploy partner solution for GKE marketplace. Who was the point person at GitLab that received that feedback? Any metrics to go along with this? So we were in a call with Google. When I say we, it was myself, Josh, Ellyran and probably a couple of others. I don't remember right now. And they, the Google GCP marketplace folk that was implementing this said, according to their numbers, the most deployed partner solution was GitLab after their default installation method. I forgot what it was, something. I don't remember anyway. Metrics that go along with this, they shared this in a call. So at that point, we were just happy to receive this feedback. We can follow up and find if there is something to share further. All right, moving on. Onto future plans. We shipped operator and a zero downtime upgrade just last week, but we did find a couple of items that are worth following up on before we decide whether we're going to enable this by default for everyone. One item that we found is that in certain edge cases, migration can start failing and then spinning new migrations and they can exponentially grow and stop your cluster from responding. And we wanna address that before we enable it for everyone. We also are receiving a lot of feedback about the documentation. And as I would expect, documentation is very simple. We tried to document everything as we went along, but obviously we had domain knowledge on how we operate GitLab. So quite a lot of questions are popping up. One thing that we are focusing on at this moment is getting Amazon EKS installation in order. First of all we have no documentation that is easy to use and Robert Marshall is actually working on that right now. And in parallel, we are trying to handle the similar situation for OpenShift because we know this is a platform that will see a high level of usage of GitLab. As I mentioned earlier, upgrade is currently very rudimentary. It is with downtime, but the bigger problem here is that users are not used to doing it. So even our basic documentation, there needs an upgrade even with the current situation. We, as I mentioned earlier, we worked on the GKE marketplace, but the GKE marketplace is evolving itself. So we now need to update our tooling to match what they are working on. And we have some great collaboration between us and Google there and we are going to put in some efforts to get that streamlined so that we don't lag behind with releases there. Going to move on to our next project, omnibus GitLab. I know that it's 10 minutes past. So I'm gonna keep talking until someone interrupts me in the group chat because this is a discussion. And I'm going to talk about omnibus GitLab at the moment. Due to our push for getting help charts to GA, we kind of put omnibus GitLab on maintenance mode, basically, but we still managed to do a couple of things. First of all, the item that I think is really important here is speeding up package builds that we constantly work on, but through that work, we realize that we have a similar problem in our charts building our Docker images. So we are working in parallel on both omnibus and the charts. And with that, we are also going to make sure that the assets that we built between omnibus and the charts or the Docker images are reused. So we shave quite a lot of number of minutes between different projects. And we are noticing that there is a lot of knowledge between omnibus GitLab and the charts that we can just reuse and streamline in one location instead of having it being repeated across two projects that are similar, not completely the same, but not that different after all. I also want to cover the collaboration that we are doing constantly with other teams. So cross team collaboration with quality, Gitaly and database teams. Whenever we find something worth improving, we try to help out. And I think like one of the biggest things I believe is the getting review apps for whole of GitLab in both CE and EE. This is qualities OKR, but because they're going to be using distributions artifacts, it is crucial for us to get that early feedback as soon as possible. Remy is doing amazing work there. I also have to call out the distribution team for pitching in and helping out. This is the same case with Gitaly and the database, you can see the links there on what we are working on and what we worked on. And this is a bonus slide that came in late. We are working on building up our knowledge base further. So we are starting back our distribution team training sessions and we are starting today with Let's Encrypt in the omnibus GitLab package. And the training is going to be held after the company call. You can find the invite inside of the GitLab team meetings agenda calendar, sorry. And you can join us if you want to. Meetings are recorded and they'll be shared on YouTube so you can watch it later. And you can find an issue that shows the future trainings that we are going to do. And that brings me to the end. Are there any additional questions? All right, no one is speaking up, no one is writing. So I hope you have a great rest of the day. Marin, good question before we wrap up. Here's David. In terms of the training sessions, do you think there's something that might be worth promoting more for outside of the company as in community members, watching them and participating in them? I don't see why not, because this training is public. It's on YouTube, it's on our handbook page. Anyone can find it and view it. If the content is interesting, I don't see why not. Cool, thank you. Thanks for speaking up. No worries. All right, with that, I'm going to end the call. Thank you very much for joining and have a great day, everyone.