 minutes into it, we'll get started. So first of all, welcome to the Q3 Hackathon. It's sort of the starting start of the fall, I guess, that we're talking about summer being over. But glad to kick it off with the Q3 Hackathon. And in conjunction with the September Court D meeting, we took a month off in August with a lot of people's summer holidays. So a typical agenda like we had over the past couple of quarters, we'll just go through hackathon logistics, highlight some of the issues that we have. We actually have a lot, quite a few of them, a lot of issues that we want to encourage community members to work on. So we'll highlight those. And then we kept the agenda relatively light for the Court D meeting. So there's just a couple of items. But I mean, one of them is a follow up from the last call back in July. So we'll go through them in a few minutes. So let me advance my slides. David's unfortunately not on the call. He's, I mean, luckily for him, he's spending some time off with his son, finishing off his paternity leave, certainly back in a few weeks. So he'll just be sort of me as a host. So agenda for the Hackathon kickoff. And I have a separate agenda for the Court D meeting in several slides. As we always do with all of our events, whether it's virtual or, you know, in person, just want to remind people of the community code of conduct. We want to ensure that we have a welcoming and open environment for everybody that participates in all of our events. So I won't go to the details. You'll, you can read a full text in the second link there. There's also an email alias if you have any concerns. But I mean, just again, as a reminder, we do this with all of our events. Many of you may have been part of commit. Last week, you probably saw reminders there and all of our virtual meetups tail. So just a quick reminder on that. Whoops, sorry. So quick logistics. I mean, this should be, I mean, a lot of, a lot of you folks that are on the call are probably pretty experienced with hackathons. I do see one or two new names. So welcome. But so we, I mean, you know, so this is a two-day event. And then we want to make, make, you know, we do want to create like a situation where you have to remember what time zone you have to be in for the event. So you can just pick the 48 hours, September 2nd or 3rd, and whichever time zone you're in. So, you know, typically the MRs come in from like the Asia Pacific, because it's already on the, on, on September 2nd. But we do have a kickoff session, even though people have started working on MRs or submitting MRs. And we have a wrap up session on the, on the 3rd at 2200 UTC. But I want to encourage everyone to just work in your time zone. You don't have to, unless you want to, you don't have to be up at midnight trying to submit MRs. And again, we have a number of office hours. The package and monitoring, this has sort of become a tradition over the past. I think this is like a third time in a row. They wanted to have their office hours coincide with slides that are not visible. Sorry. Let me share it again. My Zoom is certainly weird. Let's do this. I don't want to delay this any further. I'll post the link here to the, to the slide so you can, you can see it. Sorry about that. My Zoom is pretty bizarre today. But thanks for your patience. So hopefully you've been able to open the presentation. So in case you can't see it, my share button looks like really different for whatever reason. But oh well. So we're on slide number five for those of you that are just opening up the slides. So yeah, I think I was mentioning that, I mean, package and runner teams have been having their office hours during the hackathon. So if you're interested in either one of those, either one of those, I mean, projects or teams, I mean, if you want to see what kind of, I think runner team typically does like a synchronous MR review, they'll pick up a couple of MRs they want to look at. And package team looks at, they not only discuss like MRs that are currently reviewing, but they also look at like areas that they want community members to focus on. And a couple new other tutorials, first from release management team and folks from the GitLab pajama teams will be on. They have a number of ethics or issues that they listed for the hackathon. But if you're interested in working on any of the pajama's related stuff, stay tuned for their tutorials and in about probably in about 11, 12 hours. And if you happen to miss any of the tutorial sessions, I mean, they'll all be listed on the playlist. I have the link there that you can take a look at. And I'll talk about suggested issues. I have a separate slide on that in a few minutes. So here's a reminder on the tutorial sessions. I mean, beginning with this kickoff and the quarterly meeting to all the tutorials, office hours, and the wrap up session on September 3rd. So everything should be up to date on the main hackathon page. And as presentation links become available, I just got one from Jackie for the release management tutorial. I'll have an MR to add that to the hackathon page. So as we get new materials or YouTube recordings that all be posted here under the tutorial page, tutorial section. Moving right along on slide seven. So the best place to get help during hackathon is on the contributors getter channel. And then feel free to ping me. Or I mean, typically, I mean, Dave is not here this week. But I mean, even if after I go to bed, we have a lot of community members in APEC and European regions. So if you have any questions about GDK or a particular issue, if you post a question there, there's a good chance that a lot of people that are on the call right now will probably be able to answer your questions. So that's the best place to start to ask questions and connect with other people. I was just checking, I think we're approaching like 600 people on Gitter. So quite a growth that we're going to have on the Gitter. So it's certainly a good place to hang out. And then we also created a bridge between GitLab internal Slack and Gitter. So a lot of it's made it easier for a lot of GitLab employees to just stay on Slack and responsive messages. So I certainly encourage people to jump on Gitter if you haven't done that before. And you don't have to create a separate login. You can just log in with your GitLab ID. So talk quickly about the prices and what you do after you submit your MR. And a number of people have already done this. When you submit an MR, just feel free to copy me or just mention me at our page. And then I'll make sure that they get counted as a hackathon MR. And I'll be, I started listing MRs that have been submitted. I think we already have like a 20 plus so far. I'll be listing them in the issue, issue number 41 under hackathon. And then you'll see a hackathon MR counter starting to count the number of MRs that have been submitted on the main hackathon page as well. So yeah, just feel free to get my attention on the MR or even on the issue where we're tracking the MRs. You can ping me. And let me also paste this link here in the second on the chat. So yeah, I think Regendre has done this already. You can ping me on that issue to add it to the list. And I'll be happy to do that. So prices for the MRs, I mean, I just, I'll talk more about that in the next slide. But, you know, once you submit an MR over the two day period, they need to be merged by the 15th. So you have, I think roughly, I mean, not quite two weeks, but, you know, at least like, you have two weekends and, and, and so I'm trying to count the days like roughly 10 days to get MRs merged. So 2300 UTC is sort of the deadline. But if you have any like issues, if you have any circumstances that prevent you from getting something merged by the deadlines, just feel free to let me know and notify the, all the prize winners via a separate issue under the hackathon project. Speaking of prices, so we're maintaining this similar structure. I'm on slide nine for those of you that are, let me pace it one more time here, because I see that a few other people I joined quite do that. There you go. So, so if you go to slide nine, so the grand prize is the $100 voucher that you can use on shop.gitlab.com to, to select the merchandise of your choice. And for the second prize, second place is for people who have the second most number of MRs merged by the deadline. Believe it or not, we have a self cleaning water bottle. If you're like me are tired of like a clean your water bottle at the end of the day. So this is battery operated. It's pretty slick. You recharge it with your USB cable and, and it cleans itself. So if you happen to win it, let me know how it works. I might try to get one of these myself. It looks pretty cool. It's like insulated and it cleans itself. Like, I think it takes, I forget how long it takes to clean itself, but it looks pretty cool. And for everybody who has an MR merge, you get a, get lab branded laptop sleeve. And it's, it might be hard to see on the slides. It's, it's better to, you'll be able to see better on the hackathon page, but this is a second anniversary. So I sort of noted that on, on the prizes just to celebrate our second anniversary of our hackathon. So those other prizes and, and just wanted to share some hackathon stats over the past couple of years. I mean, obviously we saw a crazy growth from Q1 to Q2. We had like the more than 100 MRs get merged between Q1 and Q2, or we saw an increase of almost 100 MRs between Q1 and Q2. And Regendre won the grand prize last time with a whopping number of MRs merged, like 82 MRs merged, but just wanted to give you an idea of how many MRs that we've been seeing over the past few hackathons. So yeah, certainly you want to continue to grow, then we'll see how we do. It'll be, I mean, I'm thinking it might be tough to be 240, but you, you've all surprised me before. So we'll see how we do this time around. I mentioned earlier we have a list of suggested issues. So you can see this on, on the hackathon issue itself, or if you, on the issue that I just posted earlier, where we'll be listing MRs that are submitted. At the top of the page, you have a list of suggested issues that people, we would like to encourage people to work on during the hackathon. And let me, so one of the feedback last time around doesn't look like Vitaly's on the call, like we typically had a lot more, like a front-end, epic set issues that were highlighted for the hackathon. And there was a request to build a list of back-end issues. And I think we're able to do that. There are, I mean, a couple of them that were suggested by Myra. And I think the create team added, like the last like a half dozen or so issues there for back-end. So I think there are a decent number of back-end issues that people can work on. And there's an epic for custom emoji at group level. And the front-end team, once again, have a long list of issues and epics that, that people can work on over the two-day period. And some of these issues were added by the pajama team. So if you want to get more info on this, you join the tutorial or listen to the recording. So I think George and Vitaly correct me if I'm wrong. A lot of these like a GI tooltip in view, like a lot of these tooltip stuff, I think these might be related to pajama design system, but I might be mistaken. So feel free to correct me. Cool. So yeah, we have quite a long list. I mean, we, I think last time around people pretty much finish all the issues and epics on the front-end side of things. But the front-end team did a great job of adding more of them. So we'll see how we do. But we have a decent number of issues that we want to encourage people to work on. So if you're interested in working on any one of these on the issues, just feel free to ping me or other GitLab team members that open the issues and be happy to assign them to you so you can start working on them. So that's the suggested issues on slide 11. So going over this slide 12, I already talked about GitR, but there are other area ways to get help in addition to posting questions on GitR or even mentioning me. There are merge request coaches and then the easiest way to get people's attention is to use the alias at GitLab or slash coaches. Mentioned them in the MR and I'm on that alias as well. So happy to, I mean, a lot of, I think, I forget what the number is. I think there are 15 MR coaches now, but I'll also be, I'll also be happy to chase people down if needed. But I think people have been good about sort of jumping on and helping community members on MRs. So feel free to coach, feel free to ping the MR coaches and there's a page for also reviewers and maintainers if you're interested. But I mean, just using GitR and just MR coaches, those would typically be, you typically be able to get people's attention if you need any help or have questions. So let me just pause here. I mean, that's sort of end of the slides for Hackathon. Let me just pause here and I don't know if other QWERTY members want to add anything or people have any questions. Hi. Hi, Maria. How are you? I'm good. Thank you. I have a question with I want to work in one of the backend issues, which we have to do a branch, right? We have to create a branch and then open an MR from that branch or? You have to work off a fork. So just create a fork and then just submit an MR from there. If you have any questions, I mean, those are like a perfect questions to ask on GitR and then or you can even ping me on the issue. But I mean, that's a good question. Work it then from the master, right? You should be good to go. Cool. We'll look forward to it. All right. Any other questions we'll do is I'll switch over to the QWERTY meeting agenda. So go to slide 15. We have a couple of newcomers here. So I'll just do a quick level set on or give people a quick overview of the QWERTY before we get to the agenda. So I mean, here on slide, sorry, I'm having a hard time seeing the page slide number slide 16. Oh, you've got a couple of links there if you need more background on the core team. But so there's a link to the core team that talks about the mission and the composition. So we have two GitLab team members on the core team, but the rest are from the wider community who made sustained contribution over a number of years in many cases. And we do have monthly meetings typically. And the calls or meetings are always open. And then feel free to visit visit like the wiki page that I still maintain where where all the meeting materials are posted there. So you're free to join the meetings. And I've been pleasantly surprised about a number of people that actually watch your recording, usually within a day or two. I think I mentioned this a number of times to other core team members like I'll see like 100 plus people actually viewing the meeting, which I'm constantly amaze. But so the playlist is there if you haven't missed a meeting. So that's just a quick info on the core team. Let's see. So in terms of like the official agenda, and one of the things we talked about in July was rebamping or rebranding contribute for prize. We used to have a label called contribute prize. And then the other item is we have an OKR item that the quality team opened. And then Rami, I think you've been doing most of the work. So I'll probably I'll probably let you address a lot of these. But we there are a couple of things that the quality team has started working on to improve responsiveness to community contribution and also help but like a label labeling high genes. So so we want to quickly talk about that or Rami, I'll probably have you address a couple of the MRs that you open. I think one of them's already been merged actually. Let's go get to that in a minute. So slide 17. So this we had a label for over a year called contribute for prize. I mean, this was to highlight some of the issues that we wanted to encourage community members to work on. I mean, you and then so this is something that we wanted to encourage community members to look at like between hackathons and and and still get a nice nice merchandise. And I think there are a couple of reasons why there hasn't been a huge uptake. I think yet couple is on the call like I think a couple like you're you're probably like the only one who actually like a claim to prize on on one of the issues with this label. I mean, one of them was I don't think like I mean, first of all, I don't think the prize was that exciting enough. It was kind of a generic lab merchandise. So we decided to customize it this time around to make it a little bit more unique. And then I mean, I think like I can't remember who maybe it was you, George, I contribute for prize made it seem like it seemed more transactional. People are just doing something to get a little merchandise, but we wanted to highlight the fact that this is sort of a challenging issue that we want to community members to work on. So we sort of relabeled or rebranded that. And then the other thing that I'll probably try to do a better job on is doing a better social promotion like after the hackathon is over. I think I've tried that when we first created this label a little over a year ago. I probably need to want to work more closely with our social team. I mean, if you've seen some of the social promotions during Gila commit, it's been it's been great as they always are. So I probably want to, you know, lean on their expertise to do a better job of sort of promoting this on a regular basis. And hope you like the merchandise. I have a slide here and you have an image and it's also on the Gila hackathon page. So they have we have a we wanted to create a sort of a custom prize. And then we wanted to sort of play around with the theme of community challenge. So basically it says raise a cup community challenge achieved. So I had a pretty nice message that our design team helped us with. And if you know what this is, this is basically a canister. If you want to, if you're a coffee lover or a tea lover, this is a nice container to put your coffee beans in and keep it fresh. So we sort of sticking with the caffeine theme here. You should like coffee or tea. So we we like the merchandise. So hopefully we'll have a have a better luck with this a better update. And then hopefully more people will take it up. And when I clicked on the the query for how many issues have this label community challenge, there are only like a 16 of them. It looks like like eight of them have been closed. But I'll probably work with like a product managers and even engineering managers to to see if we can apply this label to more issues to highlight highlight more of them. We'll see how that goes. So any questions on that? George or others, I think we've been talking about this for a few months, but I don't know if you have any thoughts, feedback or or if you like the merchandise or if not, but saying great, right? Yeah, thanks. So yeah, it was it was like it was either this or something related to alcohol and we decided to go with caffeine, but we'll see how it goes. But and we actually have this is sort of an interesting aside, like we we had two merchandise, one was related to alcohol, the other was related to caffeine. And then when we took a poll internally in Slack, like most of the US people migrated towards alcohol and non Americans like like the caffeine that are so the caffeine sort of went out. So interesting, like I don't know what that means, but that that's sort of how we came to this item as a as a prize. So let's see how it goes. So maybe we'll have more European contributors claiming the prize. I'm not sure. Let's see how it goes. Cool. All right, so moving right along. So wanted to talk about Q3 Q3 key result items. If you want, if you click on that issue, this is something Mac opened up and then I can't remember whether it was Kyle or you, Remy, there was like a detailed task that that we have listed there on the issues. So let me post this on the chat because I'm having issues sharing. So take a look at detail items there. And then there are a couple of MRs that that are listed on the slide. So first one is, I mean, this was already, this already went out, I believe, Remy, correct me if I'm wrong, I haven't opened an email, but if there's a community contribution MRs that doesn't have the DevOps or group labels, the MR coaches get pinged to add those specific labels. That's one of them. And then go ahead, Remy. Yeah, it was not yesterday. So same as you, I haven't checked my emails, but the goal is, so for background, we already have this kind of triage report for the quality department for new issues that are untriaged. So we are kind of using this logic to triage community contributions that don't have proper labels. And the most important ones are the stage, so the DevOps and the group labels. Because with those labels applied, then we will be able to ping the relevant EMs like injury managers or project managers on merge requests that we can get the merge request moving forward quicker, let's say. Yeah, I mean, it'll be interesting to see how it goes. And I think like in one of the issues I made a comment about, I mean, there are certainly like MRs like including ones related to documentation, where there's no, not always like a clear like a stage or group that you can assign to. I think one of the group label is actually called like group like unknown or like doesn't belong to a group or something. I forget what it's called, but I don't know if there's a similar one for the stages. Yeah, that's a good question for the stages. I'm not sure either. But I think for the stages, you can always find a stage that relates to the change anyway. But yeah, that's a good question. Yeah, we have the group not owned, I think it's called. Yeah, I mean, usually it's like whether documentation or MRs like the MRs that are related to APIs, like those aren't always like clear to me. That's that's actually basically, you know, when I typically raise a hand to MR coaches and like, I don't know who should be reviewing this. But I mean, there may always be like MRs where you know, you know, it's it's never going to be clear what the stages or groups are. But as it is right now, like, I think we still have like a plenty of MRs where these labels should be added, but it just doesn't happen. Hopefully, at the very least, this will improve the labeling hygiene and also help ping the right engineering managers for reviews if they haven't been reviewed. So thanks for doing that. I mean, and the next one, I'll let you talk about that too, Remy. Yeah, so the next one, the goal was to make the cycle, so the development cycle quicker and the review cycle quicker. So instead of adding the community contribution label daily with with our triage ops automation, we do that every every hour so that if you are, for instance, if you are subscribed to this label, then you will get the notification and you will be able to act quickly quicker than before on these major requests. So that's really a small change. But the goal is to to be more responsive to community contributions in general. Yeah, I think like I'm probably not the only person who subscribes, who's subscribed to the label, because I know some of the engineering managers do, like before example, like, I don't know if this is the case with package, but I mean, engineering manager could be part of the package team and they subscribe to the, you know, package label and community contribution and it just hits their inbox pretty quickly, right. So, I mean, I've been typically, I mean, timing-wise this happens around like a five o'clock my time in the afternoon. So that's sort of a good way to end the day. I'll triage him and then I'm done. But engineering managers don't have to wait for me. So that's, this is good. So I believe in working myself out of a job. So this is good. Yeah. Cool. Anything else on the OKR, Remy, that you want to highlight? I think, go ahead, sorry. Yeah, something that we can highlight is that in the engineering productivity team, we are committed to provide metrics, meaningful metrics in order to take the right decisions and also to enable other teams to take the decisions by themselves. And so for this quarter, we will create five new charts related to community contributions, as you can see in the issue. So number of contributions over time, number of contributors, number of merge request coaches over time as well, time to merge for contributions and number of features contributed to core. So yeah, that will help us see if all the other actions have an impact or not. And yeah, provide visibility into our work and also allow other people to help us in that change. And I think you're also planning a blog post as well, right? Yeah. I mean, I think I mentioned it on the issue. I mean, even if it's just a feedback, I'm more than happy to help with you on the blog. So yeah, yeah, one more thing is that we will increase the number of coaches. And the goal would be so ideally we would have coaches in or at least all the stages and even ideally like, at least one per group, that would be really awesome. But for now, yeah, also in the UX department, that could be useful to have coaches because there are many times when contributors need UX coaching. And yeah, I think that's that's a pretty much it for this quarter. Okay, for us, will you be able to for the meantime to merge community contributions? Will you be able to filter that by groups? So by departments, because for quite a while ago, the runner team wasn't as good. So there was a drastic difference between merging something into the back end versus merging something into the runner. Yeah, that's that's a great question, because that's exactly one problem that we don't fight quickly is that we cannot just have this matrix at the very high level, because it will give us visibility, but it will not give us the precision on where we should make changes and improve. So yes, that all the all these charts will be will have filters per stage and group, I think. And so you will be able to see exactly where we can improve in which group or stage. Yeah, I mean, this is a while ago. I mean, speaking of the runner team, I had a call with, like, Elliot, and we're trying to guess, like, which of the stages have, like, the most like community contributions. And I mean, what it turned out was that that exercise was kind of futile, because mostly like a lot of the mrs just didn't have any like a stage information. So it was hard to get you know, like a reliable information on like, because the answer is like, I really don't know, because like most of them I just don't even have the labels, the right labels. So so hopefully, you know, what what what we're doing here is it's going to help with that. So cool. Yeah, appreciate it, Remy. So I was really excited to see this. All right. And any other questions for Remy or anything else that we talked about? So again, apologies for my technical difficulties earlier today. So I'm going to double check if I need to fix something before bunch of tutorial sessions tomorrow. If you don't want to see this happening again. Thanks for your patience. All right. Also, nice to see like a new folks. I think Leon, you had questions on the chat, but it looks like your questions were answered. Leon and Maria welcome to the hackathon and Gilong. Thanks for joining from Indonesia. Like look forward to seeing a lot of mrs and court team members for your help during the event. And we'll do this again next month. All right. Thanks everybody. All right. Have a good day.