 so I can post a recording for people who couldn't attend and we'll just get started. So, all right, welcome everyone to the Q2 hackathon. I was just thinking like I was putting the slides together. It's hard to believe we've already gone past like three months from the last hackathon, so it's good to resume our quarterly event. I'll just go through a few slides in the kickoff sessions and talk about what we want to accomplish in the next couple of days. So, let me advance the slide. So, if you listen to other like a kickoff sessions or attended the previous sessions, so the agenda should be pretty familiar. We'll just remind people on the Community Code of Conduct and discuss several logistic items for the hackathon and if you have any questions, I mean feel free to interrupt us. You don't have to wait until the Q&A session until the end to ask a question either verbally or I mean feel free to type them in the Zoom chat window as well. And just a quick reminder, I mean we do have a Community Code of Conduct here at GitLab. I mean the events that we have, whether it's virtual or face-to-face, it's a good time to sort of remind people that we have a code of conduct. I mean not that we necessarily anticipate negative things happening during the hackathon, but it's good to remind people that we want to treat each other with respect and be a welcoming community. So, if you can read more details on the about.gitlab.com page, there's a page for code of conduct there. You can see the link and also email if you have any concerns that you want to bring up as well. So, just a reminder on the code of conduct and a quick introduction of a couple of GitLab team members that are here and David, I'll let you go first. David, can you hear me? We may have lost David for some reason. Dennis, can you hear me okay? Yeah, I hear you. Okay, so there must be a audio-video issue with David. But anyhow, so I'm basically a community manager at GitLab. I manage the code contributor program. I mean basically what that means is that I work with wider community of contributors that contribute to GitLab. And David is my manager, he's based in Germany. He's a director of community relations overseeing that just the code contributor program, but evangelist program, education program, community advocates and so forth. So, I mean, feel free to ping us either on Gitter or through MRs or issues. I mean, not only just through the hackathon, but outside the hackathon as well. So, this is who we are. And just we'll move on to logistics at a glance. So basically, obviously, this is a kickoff session that we're kicking off right now. And we'll also have a wrap up session towards the end of the day on Thursday, on the 30th. So, in addition to these kickoff and wrap up sessions, we also have three other tutorial sessions that are scheduled for the 29th. So hopefully, you'll join us as well. And all the tutorial sessions will be on Zoom and will also be recorded. So, if you happen to miss any of the tutorial sessions because of other commitments or time zone issues, you should be able to find the links on the main hackathon page. And I'll have a more detailed slide on this as well, but especially during the event, a lot of conversation and questions can be posted on our contributors channel on Gitter. And I believe that's our next slide. Yep. So, if you're not part of it already, join us on the contributor channel on Gitter. So, if you just follow that link, if you're not part of it already, you can join as well. It's pretty seamless. You don't even need to create a separate login. You can just join with your GitLab ID. And if you have any questions, as you can see, there are over 200 people that are part of the channel that are available to answer any questions. But if you want to get our attention, you can just ping either me or David with our handle there as well. So, cool. Moving along. So, speaking of tutorial sessions, I'll be leading another session tomorrow morning, Pacific time. So, this is something that I probably should have done in previous hackathons or at least a couple of hackathons ago. We have a lot of new contributors that are joining the hackathons and contributing new MRS for each release. So, just wanting to have a quick basic overview session on where and how you can contribute to GitLab. So, that will be me tomorrow. And then following my session will be Jason. He's a director of product focused on CICD. And he's going to talk specifically about GitLab release stage. If you remember from the last tutorials during the last quarter, we had, I think, three or four product managers talking about different product stages at GitLab. So, basically, we're continuing on that because those are pretty popular looking at the number of people that have viewed the recording. So, Jason will talk about the release stage and then he'll be followed by Joshua. I'll be talking about GitLab distribution and our monitor. So, feel free to join us. We have the Zoom links on the main hackathon page that you can click on to join those sessions. And again, if you miss any of those sessions, let me feel free to follow, watch your recording after the event. So, that's the tutorials. In terms of MRs and prizes, the logistics of these are pretty similar to past hackathons. If you submit your MRs between now and the end of the day tomorrow, I mean, feel free to mention either me or David by, you know, typing something like CC at RPAC, at DeepLinella. And I just may add a comment that this is for the hackathon and we'll be happy to add the hackathon label. So, we want to keep track of MRs for, obviously, for prizes and obviously for prizes. And all the MRs for the hackathon will be tracked on that issue. And right before the call, I checked and not surprisingly somebody in the APAC region, I believe the contributor is based in China, already got to start it with an MR that was open. So, there's already one MR that's listed there and we hope to have a lot more added to the list like we did in the past couple of quarters. Prices for merged MRs, like we did in the past, anyone with a merged MR will receive a prize. And there are a couple of other individual prizes as well. There'll be a grand prize for people with the most MRs merged. And I mean, if you look at the past couple of quarters, a couple of hackathons. And I mean, there are a number of people that are pretty close like a second place finisher. So, we decided to add a second place winner prize as well to whoever has the second most MRs merged. So, those are the prizes that are available. And the only caveat is that the MRs, they must be merged by June 10th, basically towards the end of the day, UTC. So, please be aware that deadline is well on the June 10th and that's highlighted on the main hackathon page. And similar to the previous events, the prize winners will be notified by an issue on the hackathon project and you can click on that link and see how the announcements were made in the past. Okay. So, speaking of prizes, this is on the hackathon page as well. But so, these are the three category of prizes that we have. So, following the tool theme, we had a multi-tool that you can fit in the wallet last time. So, everyone who has MRs merged will get a GitLab tool pen. This is probably a pretty handy tool to have if you actually go camping. The silver tip there is basically actually a flashlight. You can also see inside in the middle the screwdriver pieces there that you can use as well. And the second place winner would get a folio bag to protect your laptop. And for the grand prize, basically $100 gift certificate at our merchandise store. So, you can spend $100 to purchase any of the merchandise that are available there. So, those are the prizes. And just want to show some quick stats. I mean, one of the questions I get is, I mean, especially for the grand prize winners, how many MRs do they have merged in the past. So, I just want to show some stats. The blue charts basically shows how many MRs have been merged in the past three hackathons since we started in Q3 2018. Obviously, we had a great significant growth from, we had like a 22 MRs merged, 22 MRs submitted in Q3 and the last quarter we had 67. Hopefully, we'll see an even more impressive growth in Q2. And basically the grand prize winner, the numbers range from like 7 to 13. So, that's sort of the range that you're looking at. So, I just wanted to share that really quickly. And the other question that I get from a lot of the people that are joining Hackathon for the first time is, you know, the question is, you know, where can we find issues to get started? So, let me actually get out of the full screen mode and let's see. So, here's a suggested list. This takes you to an issue page that we're maintaining for like, you know, good issues for first-time contributors and experienced contributors as well. So, it's possible that this list will be updated over the next couple of days. So, we wanted to provide a link. And if you're interested in working on any of these issues, let me feel free to ping me or David. And then we'll be happy to like assign those issues to you and also remove the accepting merge request label. So, we don't have somebody else who jumped in and expressed interest in working on them. So, we have like a two categories for first-time contributors. I mean, you will see a query there. Well, let me actually go there really quick and share that with you on the screen. So, basically, it has a label of accepting merge request with a milestone of backlog. So, I mean, this milestone basically says the GitLab team members have looked at this issue in the past and this is something they actually wanted to add to their backlog in terms of priority. It also has a weight or difficulty of one. So, this is why these are issues that are good for first-time contributors because, I mean, one is basically the lowest difficulty or weight that you can have on issues. So, these are relatively issues that we think that people get started on. And I mean, there are like a 30 of them right now that if you're a first-time contributor or relatively new contributor that if you want relatively bite-size issue that you can tackle, I mean, this is a good list that you can take a look at. And for some of the more experienced contributors, we have not only the general category, but we have issues for like internationalization, documentation, and issue that's good for like open-source projects that you can take a look at. But feel free to take a look at these issues at your leisure and then, I mean, let me or David know if you're interested in tackling any of these. Looks like I have a question from Dennis. Oh, so does an MR need to be submitted before the hackathon wrap up? So, I mean, basically in terms of this submission, I mean, if you look at the hackathon countdown, it's basically based on your time zone. So, wherever you're located, I mean, consider yourself. It's safe to assume that you can submit the MRs up until like midnight on day two on May 30th, wherever you're located. So, you don't have to have it submitted. I believe it will be like three o'clock in the afternoon on the 30th of my time in Pacific time zone. But obviously, if you're in Pacific time zone, you still have like several more hours left in your day. So, just make sure that you have your MR submitted by midnight on the 30th where it be located. I mean, this should be fine. So, hopefully, that answers your question, Dennis. And let me get back to the slide. I think the question was whether you can still submit the MR after the 30th. I think considering what Ray said, I would say additionally that the idea for the hackathon is to have an event that is focused on two days of hacking. And the extra time that we give is because, obviously, some of the merge requests that are more involved cannot be just merged in two days. So, there's extra time for the discussion to get the new changes in and get it ultimately merged. But to qualify for the hackathon, the MR has to be, must have been submitted in the two days of the hackathon itself. Yeah, yeah. So, and yeah, I mean, thanks for adding that, David. I mean, obviously, I mean, there are certain MRs that, I mean, when we created an issue that we didn't think through all the obstacles that people would potentially run into. So, if the MR turns out to be more complicated than we anticipated, then we can look at exceptional circumstances as well. But I mean, like David said, if you can submit the MR by end of the day or 1159 your local time on the 30th, that would be appreciated. So, cool. Okay. I think I can move on to the next slide and then we go back to full screen. So, once you submitted an MR, if you have questions or need help, I mean, there are three areas that we wanted to highlight. We talked about Gitter already. I mean, people are usually pretty active during the two-day hackathon. So, asking questions there, I mean, usually somebody around the world would normally be able to answer your questions. So, I would start there first on the Gitter channel to post your questions. And a couple of other resources that I want to highlight. I mean, first is a Merge Request Coach. I'm not sure if everybody in the wider community are familiar with the Merge Request Coach. There's a Merge Request Coach page that you can take a look at, but basically these are GitLab team members. I mean, there are eight of them right now who basically wanted to help wider community members with the MRs. I mean, that's their main purpose. So, if you have any questions with your MRs as you're working on something, I mean, they'd be more than happy to help you with any questions you have. So, the simple thing that you can do on your MR is by just simply typing, whoops, sorry about that. Let me get out of the full screen mode. So, simply by typing at GitLab-org-coaches, and that basically pings everybody, all eight people in the MR. So, whoever is available or it happened to be awake at their relevant time zones should be able to jump on and help you out. So, that's an easy way to reach all of them. But you can also look at, go to our team page. Let me do that really quickly. And under the department, you should be able to select Merge Request Coach. And whoops, there you go. And you'll be able to find all eight of them. So, you see what their area of expertise are. I mean, for example, if I want to get a hold of somebody who's familiar with GDK, I mean, Taun is a gentleman that you want to get a hold of. But this is a quick way of finding out who the right MR coach might be for your area that you're working on. But like I said, I mean, if you want to ping, if you're not sure who to get a hold of, you can just mention the MR coach group by just typing this text right here in your MR or issues. And the other resource that I wanted to highlight is we also have a list of maintainers for various GitLab projects. So, if you click on this link for, I mean, different areas of GitLab, if you want to find out who the reviewers or maintainers are, we have a full list that's completely public. And you are more than welcome to ping any of these people in your MR as well if you have a question. So, just wanted to highlight these three areas where you can get help. And I mean, don't be shy about taking advantage of resources that are available. I mean, they're there for to help wider community members. So, I mean, I would not be shy about pinging anybody within GitLab. So, that's a completely appropriate thing to do in our community. Okay. And think that's all the slides that I have. David, was there anything that I missed or glad that you're back online? But feel free to add anything I may have missed or I didn't cover anything. I think that was pretty much it. I think we touched all of the points we wanted to talk about. I know what stress again, what you've already said, please do not feel shy about pinging people. That's what we are there for. So, do it on the major quest, on the major quest. Do it on on on Gitter. And you'll see that folks will be more than happy to jump in and help you on your major quest. If you're working on a major quest, we love to hear about it as well. So, feel free to to mention it on the Gitter channel as well. And finally, I would say we had, if you looked at the stats from race presentations, we had about 70, more nearly 70, Marchi quests submitted on the on the last hackathon. It would be, I think it would be a really nice goal to have 2400 this time around as a nice strong number and I think that there's something that would be feasible. So, yeah, I feel free to submit your major quest and we'll be more than happy to look at them. Cool. All right. So, I don't see any other question on chat, but any other questions from from people that are on the call that we can answer? Like, again, I mean, feel free to type them on chat or or you can unmute yourself and ask your questions. I mean, if you remember a question that that you weren't able to ask after we end the session, I mean, feel free to post them on Gitter. And then, I mean, time zone wise, I think between David and I, we have pretty good coverage. So, we should be one of us should be able to jump on Gitter to answer your questions or find somebody else who can. Cool. All right. If there are no other questions or comments, I mean, just want to say thank you and wish you happy hacking. And just ping either one of us. If there's anything we can do to help out or or if there's or if there's anything that we can do we can do better in the future. So, cool. All right. Well, thanks, everybody. We'll end the session and we'll we'll see you guys on on Gitter channel probably. All right. Thanks, everybody. Cheers. Thanks everyone. Bye.