 15 seconds to make sure it's recording. Yep, looks like we are. So hopefully people can hear me OK. Otherwise, just feel free to type something on the chat window to get my attention. Also sharing my screen with the hackathon kickoff slide deck and quickly go through these. But please feel free to interrupt me and David as we go along. And after this session is done, we'll also be posted on our playlist on YouTube so other people can listen to the recording. So again, my name is Ray Peck. And I'm here with David Plinella. And I think we have the intro slide and a couple of slides as well. But just wanted to do a quick kickoff of the Q1 hackathon. So this is already a third edition since I joined the GitLab team. So this is a quick agenda for the kickoff. And just wanted to cover logistics and answer any questions people have. So a high level agenda, just wanted to remind people about the code of conduct that we have at GitLab. And we'll talk about schedule logistics, MRs, and also places to start. And make sure we answer all the questions you have. And in terms of code of conduct, I have a link here that you can take a look at. Go to about.gitlab.com. And then there's a code of conduct page. I won't necessarily read through the full text of what's there. But I mean, it's basically, I mean, nothing should be surprising in there. We want to treat each other with respect. Want to have a warm and welcoming environment for all community members. So just a good reminder. I mean, a hackathon or other events are a good opportunity to give people a reminder of our community code of conduct. I mean, this is something that we feel is very important. And if you have any questions or instances, feel free to contact us at conduct.gitlab.com if you have any questions. But that's there for, all right, so let me enlarge the screen so people can see the slide better. Sorry about that. Ray, I think if you just click on the Present button on the slide standing to a bit metaphorically, everyone. Yep. Thank you. All right, so yeah, thank you, David. So OK, so that's that on the quick reminder on community code of conduct. So next slide, quick get a glance. As we've done in the past couple of quarters, this is a two-day virtual event. I mean, kickoff is starting right now, but I've noticed that people have already been submitting MRs for the hackathon. And I'll talk about where all the MRs are being kept track during the two-day event. And we'll have a wrap-up session around 2300 UTC on, I'm sorry, this should say the days are wrong. It should say Tuesday and Wednesday I'll change the slides. But we'll end on around 2300 UTC on the 13th. And during the event, if you need any support or if you want to just have a conversation with community members during the event, go to our Gitter community room for support and questions. But either David and I will try to jump on any questions that people may have pretty promptly. We'll also have tutorial sessions. We actually managed to schedule all of them on to Tuesday. And what we did this time around was invite several product managers from four product teams at GitLab. We have product managers from Manage, Verify, Create, and Configure. And it's similar setting to this kickoff session. We'll be on Zoom and we'll be recorded. And that will be posted on our hackathon playlist that the link is provided below. And if you want to see a detailed list of all the presenters and links to the Zoom sessions, just feel free to go to the hackathon page and should all be listed there along with the prior DMRs that I'll talk about and also with prizes. Moving right along, I guess I should have put this slide earlier in the deck. But I mean, the host for this two-day event is myself and David. And we're spread out geographically, so we should be able to have decent coverage. Should people have any questions, I see that another person has joined the call. So either on GitLab or Twitter, feel free to reach out to us if you have any questions in addition to using Gitter. Be happy to answer any questions you have. Cool. And then in terms of logistics, like I noted, I mean, Gitter is sort of the channel that gets actively used over the hackathon period, so ping either David or myself. Or I mean, there are a number of other people that have been very good about answering people's questions during the hackathons. So if you post questions there, even if David or I aren't able to get back to you right away, somebody should be able to lend your hand. So let me pause here for a few seconds. And I mean, David, was there anything else that you wanted to cover here that I may have missed? No, that sounds excellent. I mean, I'd say just everyone don't feel shy about pinging us on Gitter. You can also, if you submit a merge request, then feel free to use those same usernames to mention us on the merge request. Or if you're discussing something on an issue, same for an issue, feel free to ping either Diplonella myself or RPEG, which is great. And then, yeah, we'll be more than happy to help you. And then if necessary, then get you in touch with the right team members of GitLab who can further help with technical questions. Thank you, David. OK, so also some of the speakers that I mentioned earlier. So we have four product managers that will be talking to us or leading the tutorials. One of the things that I did in preparing for this hackathon was to I talked to all the product managers, not only to invite them to lead tutorial sessions, but also to identify some of the issues that really the community members help with. I mean, so that's sort of the inspiration where I got the inspiration to create what we call the priority MR. So these are some of the issues they wanted to list out to community members to seek out your help. So they'll have a chance to talk more about this in detail if you're available to join their sessions. And then they'll talk about those issues in other areas where they would more than welcome community members help. So I listed their talks in various time zones. So if you're not able to attend because of the time zone complex, the sessions will all be recorded and posted on the YouTube channel. So these are the four speakers. So we'll get to the MRs. And as David mentioned, when you submit MRs, I mean, feel free to mention both myself and David. We'll be happy to make sure that it gets reviewed by somebody on the right product team. So we'll be happy to do the triage. And we'll also be adding a hackathon label for your MRs that are coming during the hackathon period. And I opened an issue here that you can look at. This is where the issues will be tracked. So let me go in here really quick. So as I noted, I mean, the person from Japan already submitted a couple of MRs, and one of them actually already been merged on WWGetLab.com project. So this is where I'll be listing all the MRs that come in. So we're off to a decent start with the two that have already come in. But I hope to see this list definitely grow over the next couple of days. OK, back to the slides. So the prizes. So I mean, similar to last time around, anyone who has any MRs merged will receive a prize. And the following slide we'll show you the pictures of the prizes that we have ready for this hackathon. And the person with the most MRs will basically receive a grand prize. And the MRs must be merged by 2,300 UTC on Monday, February 25. So you have roughly 10 business days, I think, or roughly 10 business days from now to get your MRs merged. And like we did in the past for another typo, it will be notified by I'll create another issue to notify all the Q1 hackathon project winners. Oops, sorry, too fast. So what we did this time around, we definitely want to see the volume of MRs that have come in, as we've seen in the past couple of quarters. But we also wanted to highlight some of the issues that the product managers wanted community members help on. So I think like most of the product areas had identified issues, including documentation that we want to encourage community members to work on. The only ask is that, I mean, some of these may not be the easiest issues to work on. So we encourage you to just pick one of the issues that you're interested in and work on one of those only. If you try to tackle more than one of those, I'm not sure if you'll be able to complete them in a reasonable time frame. So if you're interested in working on one of these issues, you can just add a note to it in the comment, and we'll try to get that issue assigned to you. I believe two of the issues people have spoken for already. One is on a documentation, and the other is on, I believe on Verify, but let me go to that page here so people can see. Yeah, so I believe this documentation and this Verify issue that people have expressed interest in, but others are still wide open. As far as I know, I want to check a couple of hours ago. So feel free to go through these issues. And if you're interested, just express your interest and you can go from there. Let me go back here. And then I scroll through that on the webpage. So the prizes for anyone with the MRS marriage gets this, it's called a wallet ninja, but it's a handy tool. And this is actually TSA approved. So you can get it through airport security. And I can vouch for that because I had to carry this through security when I went to Pawsdam a couple of weeks ago and I didn't have any issues. I think somebody looked at it and see what it was, but she let me carry it on the plane. So it's a handy tool that was pretty popular at Pawsdam where we had the sand. And then people with priority MRS will get this insulated water bottle. It's gotten good reviews. And the grand prize get this nice duffel bag as a reward. So those are the prizes that's just listed on the hackathon page. And just want to recap quick stats from the past two hackathons because I got in some questions from community members. So just wanted to share a couple of data points. So if you look at the Q3 hackathon, the number of MRS that have come in were 22. And then if you compare that to the following quarter, I think the number almost tripled to 65. I mean, I definitely want to see a growth like this continue into Q1, but that's sort of the, I mean, this sort of indicates a level of interest that we've gotten from community members, which David and I were very excited to see. So those, the blue bar basically shows the MRS like a total number submitted over two hackathons. And the red bar basically shows for the grand prize winner how many MRS they had merged basically. So it went from like seven to 13, like we'll see what kind of numbers we see this quarter. But I mean, it's, you know, one of the questions I got from a couple of the community members just wanted to share the stats. Let me pause here real quick and make sure there are no questions or David, I'm not sure if I covered everything that we needed to cover. Sounds good. I mean, I would say something as well, even as we speak, we're updating the, some items on the GitLab hackathon page. So I'm thinking that we should probably add the presentation, right? Yeah. The kickoff at some point. I mean, I can do it during my day while you're sleeping. No, that's very sleeping. We're just in different time zones. Right. But yeah, I would say stay tuned to the main GitLab.com slash community slash hackathon page for other changes or notices that we do during the event. One thing that we're doing right now is we've noticed that the countdown needs fixed but we're working on essentially solving this as we speak. Cool. Yep. Yeah, definitely. Along with YouTube, presentations will get them posted on the hackathon page pretty quickly. Okay. I think I just have a couple of slides to go. So sorry, this slide is pretty busy but good places to start for newcomers. I mean, one of the things that you can do is just basically go to like a gitlab.com and do queries on like, for example, on CE. Look for issues that are accepting merge requests and has a backlog milestone. So you'll see a sample query there which I ran today and earlier this morning, my time in there I think there were about 12 issues. So let me click on that link. Yeah, it's the number still the same. So this is for community edition. So the reason why I picked these two labels and milestone is that with these labels and the milestone it's likely that somebody from the product team has sort of gone through the issue. Make sure that it's specced out in pretty good detail. And number of gitlab people have looked at this. So this should be like issues that are relatively easier for people to get started. And I also added a way to one. So this is like one is obviously easiest versus 10 which would be very difficult. So this is sort of one way to search for like issues for newcomers to get started on. And then going back to the slide, I also want to highlight a couple of issues that one of our core team members, Hanes, brought up as potentially good ones for first time contributors. I believe the first time is like a documentation fix. So I mean, if you are looking for ideas on where to get started, I mean, definitely look at these two issues or I mean, do a simple query like I did to look for issues that would be relatively straightforward for newcomers to get started with. So that's a quick recommendation. And the next slide. So I mean, this is basically a summary of what's captured in our contributing page. So if you go to about doc.gylab.com slash contributing, you'll have a lot more of these in detail but I kind of summarize depending on the area that you'd like to contribute in whether it's in development documentation or even UX design, you'll find links where you can get started. And like I said, these four different sections are in a lot more detail on the contributing page but I summarize them here and I'll get this slide posted, we'll get this slide posted pretty soon. And the next page also includes the information on the contributing page on where to get help. So we mentioned the Gitter community room number of times but there are a couple of other links here that can help you get started. And we also have Merge Request Coaches at Ready to lend your hand and basically details on how to find the Merge Request Coaches and how to get a hold of them. And it also reviews and maintainers of various projects. So if you ever get stuck and if for whatever reason David or I are able to get back to you in a timely fashion, there are other Git labbers that should be available to help you out during the hackathon period. So I believe that's my last slide. I noticed that there are several other people that had joined the call in the last 15 minutes or so. Are there any questions or comments? Let me see if I can read the question again. I see some on the chat Ray from Aaron who's asking which GitLab repos are part of the hackathon. I'm interested in GitLab charts and GitLab repo. I would say perhaps as a rule of thumb everything that's under the GitLab dashboard group that includes GitLab C, GitLab EE, GitLab Pages, GitLab Runner, I think the charts one is in there as well. Even if it's not out there, cool. So I think for your particular interest then that should be perfectly fine. In general, we put some more emphasis on triaging merge requests from GitLab C or GitLab EE just because we want to make sure that we don't spread ourselves too thin. Obviously, we'd like to look in detail at any merge request from the way the community throughout any repos. But yeah, for the hackathon, we're actually more aware that there are merge requests throughout GitLab dashboard. So yeah, if we don't happen to reply to you on a merge request after a few hours, feel free to go to PNAS or as we said, I mean, if you go to PNAS there are ideas, you write them on your request and go make sure that makes it to the hackathon. Cool. And then I see that question from Gokhan. Yeah, thank you. So I'll try to find your merge request on CE and make sure that's labeled as hackathonMR520. Thank you. Yeah, I mean, as David noted, like if it's, if you notice that it's not getting labeled and within reasonable timeframe, just feel free to ping us on Gitter. That's probably the quickest way to get ahold of us and then we'll make sure it happens. Cool. Any other questions or comments? David, are you trying to speak or? I'm sorry. It's okay. What else? I was just, that was just a question to Gokhan. Is that the URL from the merge request? I don't seem to find it just to make sure that we are looking into it before we wrap up the call. Oh, I bet the numbers are flipped. Five, two, one, nine, eight. I've been in chat. Oh, there we go. I see it. Yeah, I saw this earlier. I didn't realize this was for hackathon but let me just add that. Cool, thank you. And thanks for checking, David, before we signed off. Any other questions? Got six minutes left, but happy to end the meeting early. All right. Well, thanks for your time, everybody. Happy hackathon, happy hacking. And we'll see you guys online soon. Just feel free to ping us if you have any questions. Bye, everyone. Yep, bye.