 Hey everyone. So stop of the hour. Let's just wait a few seconds for people to join and I'll share my screen in the meantime. I'm stepping in for Sarah today. She's not able to present the functional group date for UX, so I'll be doing that. Let me present. Okay. So I hope you're seeing my screen. If you're not, just shout. So welcome to this functional group update for UX user experience. I'm Peter Murat of the Silver. I'm a senior UX designer here at GitLab and I'm just going to show you a little bit of what we've been up to since the last group update. So our agenda, welcome G2 accomplishments, a little sneak and peek and questions in the chat. So feel free to start putting questions now if you want me to answer them later. So first of all, welcome G2 to the UX design team. He's based in Chennai, India. You have some links there for his social media accounts. Feel free to reach out to him. Just schedule a coffee chat wherever, just to say hello. And he's our latest addition. And we've been, so the opening for the UX designer position was open since late November or mid-November. And we've finally been able to close that position first with G2 and then we'll have another person joining us later. And that's one of our accomplishments. So in terms of hiring, we've filled both UX designer positions after a lot of work and a long time and a lot of interviews. But I think that the work that we put into it just means that we have really good people with us and that's exactly what we were aiming for. So even if it takes too long, it's worth it. For the operation engineering survey, it's something that is part of our OKRs and the survey is now out. So we've had over 200 responses so far. And the idea here with the operation engineering survey is to identify the needs and pain points of this role to surface opportunities. So this is one of our OKRs. It's a, if you click there on that link, you see an issue into what we want with this initiative is to make operation engineers a first class citizen inside of GitLab. And this is just a small step towards that and this research will help us identify the main opportunities. The third point, improvements to the Kubernetes installation flow, something that we've already talked about and Sarah Donnell from UX Research also showed and shared a little bit in the previous functional group update of UX Research. So it's also something that's part of our OKRs and the whole UX team came together to look at the Korean installation flow which takes over an hour and we've identified together the short-term iterative improvements and all of them have been scheduled which is amazing and we hope that soon enough people will be using Kubernetes much faster and GitLab will be the go-to place for people starting out and to do auto dev ops. So here's a sneak peek at something that we've been working on. It's improvements to the styling of comments and system notes in both issues and merge requests and initially this idea and this issue was created by Annabel some months ago and now Hazel from the UX team is working on it and because currently it's very easy for someone to get lost in the middle of all the comments of the system notes there's just a lot of noise there and we hope that this issue which has a lot of discussion and you can go through it and see a lot of versions and iterations until we reached this final stage, this screenshot that you see here and we hope that this will improve this discussion tab a lot more. So feel free to give your comments there as well in the issue and let us know what you think if you like it, if you don't like it or your concerns or just thumbs up the issue. This is also an issue, one of the first issues where we are using the UX deliverable label just trying it out. So what this means is that for this issue which is scheduled for 10.6 it's what is scheduled is not the implementation of the issue but the exploration of the solution of the design and this is what we're aiming for to get done for 10.6, the milestone and after that we'll go through the implementation. And yeah, questions. Let me exit full screen and see what I have here. Thanks Scott. Lucas, I heard, will there be system note squashing? So that's something that we've, there's a lot of issues around that, squashing system notes or just plain hiding them or having another tab just for system notes. Currently we're just doing the styling. I think that's something that we have considered from time to time but at the same time we don't want to lose basically the whole history of what's happening because even mentioning issues and merge requests or adding related issues. So all of those notes and things that happen to an issue give you the whole context of what's happening. But at the same time, I know what you're saying. Sometimes it's just better to focus on the conversation. It's a difficult balance to strike. So I don't have a final answer for that, just that it's something that's in the back of my mind and maybe in the future we will, if we have a lot of upvotes and people wanting that we will think more about it. But thank you for the question. And then Dmitri Dizzy asks, when will design.gitlab.com will be live? So for those who don't know design.gitlab.com, it's where we intend to have our design system. So by design system what we mean is not necessarily just things that people think are design. So visual design and interaction design, it's much more than design. So currently we're migrating all of the documentation that we currently have in the user docs for, it's a UX guide that we have there and we're migrating that all to design.gitlab.com. And over time we will also integrate there the final code live. So we will have for each component for buttons, tabs, links, text files, everything that you will see every single piece of the UI that we have on GitLab. We intend to have dedicated pages on that design system that show you the usage, the guidance and also the live code. And over time what we want to do, our very future vision is to basically have a central place for anyone who wants to contribute to GitLab, they will have everything there, even product values and things like that. But right now we're just starting out with what is the more visual side of it and integrating front end parts. Answering directly to the question, when will it be live? So we're intending to have it live by the end of this month. So even it's something that is scheduled for this quarter and it's something that there's an issue already open about it and we have also a Slack channel if you want to just chat about specific things related to the design guide. So the end of the month hopefully that's what is scheduled. Yeah, and Dimitri just posted the issue on the chat that links to the whole domain things that we need to put design.gitlab live. Thank you. Yeah, exactly. John said in the issue that he would try to get DNS configured later this week. So it would be nice. Cool, cool. Yeah, it's something that we're very, very excited about. Actually this week on Friday, we're going to have a hack day just dedicated to both design.gitlab.com and also the pattern library, which is something that is parallel to design.gitlab.com and it's basically a sketch file. So it's where we host all of the visual design assets. It's basically like a big Photoshop file if you know Photoshop. A sketch is another software that we use here at GitLab and that is where we're going to develop visually all of the components and colors and buttons and things like that. And we're going to have a full day on this Friday just dedicated to exploring more of that and also writing down the documentation of everything that we can during those 24 hours for design.gitlab.com. And it's something that we're very, very excited about because design.gitlab.com as a whole will allow us to move much faster and have a much better communication first with the front-end team and front-end team with UX but also in the near future with product and we hope to expand this communication and have a central place for everything about building GitLab. So, Rebecca, can we help? Sure, I think, so I will share with you the epic, I think we have an epic for that or an issue at least. And maybe we will, I think it will be good to have someone look over the content and see what is missing or how we can write things better and also see basically how we can have a better synergy with the content team because maybe we're writing down some things that are also in other places. So, yeah, thank you. Thank you for reaching out and we can talk more after this call. And Gabrielle posted the link to the current iteration of design.gitlab.com. It's kind of a sneak peek so you can access the design system there. It's still in progress and it's not live in the final URL. So we're still refraining from sharing that link but of course you can use it and internally you can look it up. Thank you, Gabrielle. Anything else? Cool, so I hope you're enjoying GitLab's UX more and more as you use it and you find more things for us to fix and for us to improve because UX, it's a bit like performance. It's something that is transitional to the whole company. So it's not something that only the UX team should concern about. It's everyone's concern. So thank you for watching and I'll see you in the team call. Bye-bye.