 Now, OK, with that public service enhancement, we'll get things kicked off. My name is Ray Pake. I manage the code contributor program at GitLab. And welcome to, it's hard to believe, I'm saying this sixth edition of our quarterly hackathon. So last hackathon of the year. Excited to see the continued growth. So David Planella and I will be giving you a quick overview of the hackathon. We'll go through some slides. But if you have any questions, feel free to stop us. Either you can voice your questions verbally on the call or type it in the chat window. So we'll answer it in the real time rather than having to wait till the end. So quick introductions. So let me go into a full screen mode so hopefully you can see this better. So again, I'm Ray. I'm based in California. So you can see my Twitter and GitLab handles there. And David, I'll let you introduce you to the attendees as well. Hi, everyone. I'm David. I've got the privilege of working with Ray and other program managers in the community relations team. I'm based in Europe, in Cologne, in Germany. So feel free to ping me if I can help with anything during the hackathon if Ray's still about to start his day. Yeah, so I think we have like a good coverage being in two different continents. So any questions you have, just feel free to ping both of us. One of us should be up and around, be able to answer your questions. So thank you, David. So I'll quickly go through the agenda. I mean, if you've been participated in past hackathon or listened to previous recordings, the agenda should look pretty familiar. We'll do a quick reminder on the community code of conduct. This is something we do at all of our events, whether it's for shoulder, face to face, and we'll go through logistics and detail items on the hackathon real quickly. And like I said, you don't need to wait until the end of the session for Q&A. So feel free to stop us if you have any questions. So on community code of conduct, like all good open source project, we do have a code of conduct to make sure that we have an open and welcoming environment for everybody in the community. So I'm not gonna go through the full text of the code of conduct, but you have a link there that you can visit. I mean, we never had any instances that during the hackathon, we definitely wanna keep it that way. But even during or even outside of the hackathon, if you have any concerns or see something inappropriate, feel free to send an email to aliasconduct.gitlab.com and that email actually comes to me and David. So if there are any concerns that we need to address, we'll jump on it right away. But I mean, this is again, I mean, there haven't been any issues here. I don't wanna raise any concerns, but each time we have events, whether it's virtual or face-to-face is a good time to sort of remind community members of our code of conduct that we wanna adhere to. So moving on, a couple of slides on logistics. Obviously, we're doing a kickoff session right now. In about 40 hours, we'll have a wrap up session like a 2,300 UTC on the 14th. And in between those kickoff and wrap up sessions, we have a number of exciting tutorial sessions scheduled. We have speakers lined up for GitLab GL or replication GitLab managed stage, Multano. Not sure everyone's familiar with Multano, but if you're interested in data analytics or if you're even data scientist, I mean, that's something that you probably wanna listen to and watch recordings of. I mean, that's been gone through a lot of evolution over the past four quarters. So we're pretty excited about that session there. And then we also have a couple of speakers to talk about our new GitLab Heroes program or initiative that you probably wanna listen to. If you happen to miss any of these sessions, the recordings will be posted on our playlist. And feel free to check them out there. I usually try to post them within 30 or 45 minutes of session being over, so you should be able to find them there. And last but not least, if you haven't checked it out yet, I mean, go to our contributors Gitter channel. That's where you'll find, I mean, not just me and David, but a lot of our contributors sort of being present there. A lot of questions and answer that gets resolved. I mean, even I wake up in the morning, I'll go to the Gitter channel and I'll note that the question's been asked and it's already been addressed by somebody else in the community, which is great to see. So it's a great resource. So I encourage you to check that out in terms of support and network, even networking with other community members. I'll move right along quickly. I just wanted to show you the Gitter channel if you haven't checked it out yet. Last time I checked, we're well over 360 people that are part of that channel. I remember with our first hackathon, little over a year ago, we had like less than 50 people on that channel. So we've seen enormous growth over the past year or so. And then if you need to individually like ping us, let me feel free to ping like David or myself, Deeplanella or Arpeg. You can also do like a direct messaging or individual conversations. So that's a good way to get our attention. And then you don't need to even create a separate account or log in. You can just use your existing GitLab ID to log in. So it should be pretty straightforward and simple. But it's like I said, it's a great resource and I encourage everybody to check it out if you haven't done so before. And before I pause for a minute, just wanted to show you all these speakers that we have lined up for tutorials. Like I said, we have speakers for GEO, The Managed Stage, Meltano and GitLab Heroes. So Fabian Zimmer, he's a product manager for GEO. He'll be, he might actually be doing this with another coworker of ours, Tom and the GEO team on the engineering side. So we're looking forward to that. And then you may have seen, if you checked out past videos, you may have seen videos on the Managed Stage, but there's been a lot of changes on Managed Stage with several different new groups that are underneath it. So the group manager for Managed Jeremy will be there along with Garcia who's on the engineering side of things. So there'll be the two speakers and on Meltano, Yanis, I mean, he's got slides which is already posted on the Hackathon page, but he's also gonna do a live demo, which David and I have seen at GitLab Commit in London about a month ago. So I encourage you to check that out. And obviously a lot of you folks that are listening in or watching this recording, a lot of you have contributed to GitLab through code, but John and Emily will talk about other ways that you can contribute to GitLab, whether it's like a speaking at events about GitLab or writing blog posts and various posts on GitLab as well. So I'm excited to have both Emily and John come talk about, not only give you an overview of the heroes program, but resources that are available that we offer to the heroes. So you'll see the various time zones for the sessions there, but if you happen to miss them because of the time zone issues, I mean, watch the live stream, I'm sorry, watch the recordings later on. I'm gonna pause here. I think I spoke a little too much or a little too fast as well, but let me pause here. I mean, David, did I miss anything here or like anything else that's worth pointing out? No, I think that's great. I think one, perhaps one thing to, and I think you're going into this in the rest of the presentation, but feel free to check out the, if you're interested to see the progress of the Hackathon, feel free to check out the Hackathon page on about.gitlab.com slash community slash hackathon where you'll be able to see live how many measures were submitted. It's a way to see which things people are working on and how well we're doing in terms of comparing it with the activity with the previous one. It's a fun thing to watch as well, so I tend to do it quite often. Yep, cool. All right, thanks. Okay, so moving right along. So merge MRs and prizes. So a couple of things we wanna mention on the MRs. When you submit an MR during the Hackathon and me, feel free to mention me and David so we can add a Hackathon label to the MR. I mean, I'll talk about this in a minute. People in the APAC region got an early start on the Hackathon and the way I found out about their MRs were that typically, they either mentioned me on the merger quest or the other way that happened for this Hackathon was that somebody just pinged me on Gitter and said, hey, Ray, I just submitted an MR and it's for the Hackathon. So please try to grab our attention. And then the Hackathon MRs, like David was saying, the counter will be on the main Hackathon page. It'll be up in a few minutes. And then if you wanna see an individual list of them, you'll actually see it here. So I'm gonna go off full screen for a minute. So we, I mean, believe it or not, we already had like a 14 MRs that's been submitted so far, which is amazing. So yeah, and then four of them have already been merged, which is cool. I mean, a couple of these were, I mean, three of these were like a documentation fixes that I was able to merge by myself. But yeah, so they'll all be listed here after we add the Hackathon labels. So I mean, please feel free to just ping us when you submit an MR. So let me get back to the slides here. Nope, sorry. Yeah, and prizes. So there are, as we've done in the past, like a two or three quarters at least, there'll be three categories of prizes. Like anybody who has MRs merged by the deadline, I'll talk about it in a minute, we'll receive a prize. And there'll be a grand prize for individual with the most MRs merged by, I mean, November 25th, basically. But we also have a category for the second place winner. So I'll go over the prize in a minute. You may have seen it on the Hackathon page. So this worked out pretty well. And for second prize and the Merge MR prize, we were able to get a customized prize that's not available on the GitLab shop. So hopefully you'll enjoy that. So on the MRs, so in terms of submitting an MR, like we didn't want to do anything like unnatural for community members. Like we didn't want you to have to think about like which time zone that you have to time your MRs in. Like we want to just have you continue to work in your own time zone that you're in and you're comfortable in. So when you submit your MRs in the 13th or 14th, just do it in your own time zone, like whatever hours that you work. So I mean, what happened was that person in India just created something like shortly after midnight on November 13th and just ping me on Gitter, which is fine. So any window, any 48 hour window between 13th and 14th in your time zone is completely okay with submitting an MR. But we're gonna have a strict deadline when it must be merged by based on the UTC time zone. So 2300 UTC on November 25th. So you'll have roughly about 10 or 11 days after you submit your MRs to get them merged. I mean, if you have any issues for whatever reason, the review is not happening quickly enough or there are any like a tooling issues or whatever issues that you run into. If you feel like you may need additional time for your hackathon MR, just let me know. And we'll definitely look into it. And I'm happy to make any exceptions if it's reasonable. But I've just let us know at a time, but we'll be sending out reminders through various social channels to have your MRs merged by November 25th. And the winners will be notified via an issue. And if you go to the hackathon project and you'll probably be able to find the issues from the previous editions of hackathons, you'll probably, you'll get a chance to see how we announced winners in the past. But shortly after 25th, I'll create an issue with the list of the winners. So I think that's that. And then yeah, in terms of prizes. So the grand prize basically you get to spend $100 at the GitLab store, which has been very popular. So you can basically get any GitLab merchandise of your choice, things like hoodies, t-shirts or other items that are on shops. And the second place winner is, I mean, they call this a music box, but it's pretty cool. It basically is a Bluetooth earbud plus a speaker with a nice GitLab design there. It looks pretty nice. And people, everyone with the MergeMR is, they call it a tech organizer. So on one side of it, you'll get to organize your, I mean, various cables like headsets and USB cables and other stationery items. So on the flip side of things, you should be able to put your tablet in there in this trap. So hopefully you'll get to enjoy it. And again, that's, you know, it's got to, we customize it with the GitLab logo. So cool. And those are their prizes. And just wanted to go quickly over the stats. I mean, in Q3, I mean, about three months ago, I mean, we basically blew past the previous record in terms of the number of MRs that were submitted. So the blue graph shows the number of MRs that were submitted over the two day period. And then, I mean, basically, beat the previous record in Q1 of 2019 by like almost 50%. And people had questions about how many MergeMRs were typically needed for the grand prize. So it ranged from between seven to 13. But yeah, so just wanted to give you a sense as to how many MRs were required to win the grand prize. So hopefully they'll give you an idea. Obviously, you know, want to see the continued growth in the number of MRs. And it'll be awesome to cross a hundred threshold in terms of MRs. I think there'll be a great accomplishment. But we're already 14, that's in. The hackathon just kicked off. So I'm pretty optimistic. I think there may be a question. Let me see. How many people participate? Yeah, in terms of, I don't remember the number off the top of my head, but in terms of like the winners for the past hackathons, it ranged between like 20 to 30 people that we sent MergeMR awards to. So the number of people that actually participate are probably larger than that. Like there are people who submitted MRs, but didn't win a prize for whatever reason. But hopefully that answers your question. So let me type it in there as well. But so that you can see it. Well, I was, I would highlight also that as he was saying, there's other people that participate, not only submitting MRs, but there's people who are participating on Gitter for instance, helping those who want to submit their first MRs for instance, or those who are commenting on issues, including MergeQuest coaches, which are the team members who help get this MergeQuest merged. So I'd say it's difficult to say for exactly, but let's say, I don't know, if we were to say like 20 to 30 people working on MRs themselves, then perhaps you could add it up to 50 if you include those helping there. Yeah, thanks, David. I'm typing that into the chat window as well so people can see it if they're cool. Okay, so as we've done in the past, we also have like a number of issues that we suggest for a hackathon. And then let me actually go back to this page where we keep track of merged MRs and in this section right above, we have various links with links to suggested issues that people can work on during the hackathon. And well, we also wanted to highlight like a number of engineers and even product managers have labeled certain issues with the label first time contributors. So if you click on this link, like you'll get you to a query with labels accepting merged requests and good for first time contributors. So if you're interested in working on, I mean, first of all, take a look at these list of issues and see if any of these you might be interested in working on and just let us know, like David or I know that you're interested in working on this during the hackathon and we can definitely like assign these issues to you once you submit an MR. So that's one of the things that we want to highlight and there are a number of, what, sorry. There are several other issues here for UI UX. I mean, if you're interested in like working on like a Maven or a container registry, there are a few issues that you can look at as well. Sorry about that. I have a problem with my mouse, but there are also issues that we have like highlighted for more experienced users but do take a look at those. I mean, these are just guidelines if you want to work on something else like an issue that's not on this list or I mean, there may not be an issue that's been opened. I mean, that's completely fine. We accept all contributions, but we just want to give you a guideline or suggest a list that you may want to take a look at if you have a hard time deciding what to work on during the hackathon. Let's move on here. And David like already covered some of these. I mean, during the hackathon, I mean, hopefully David and I can answer most of your questions and we're available when you have an urgent question, but there are other resources. I mean, Gitter, we already talk about like a community members are definitely a good resource. And the Merge Request Coach that David talked about is well, if you're not familiar with who these people are, I mean, there are a couple of links here that you can check out and find out who they are and where they're based. I mean, these are GitLab team members, but they're specifically, I mean, volunteering to help with community contributions. And for whatever reason, if your MR is not getting reviewed in a timely fashion or it just fell through the cracks by even me and David, I mean, feel free to mention like GitLab Merge Request Coaches by typing at gilab-workslashcoaches and then you'll get coaches attention and I'm actually in that group as well. So if I happen to miss your MR, then I mean, this will definitely get my attention. So that's a good way to ping people if people are not being responsive. And then the final thing, you can also find the appropriate reviewers and maintainers of various GitLab projects by going to this link in the handbook. It's a pretty long list. We probably have like over 300 engineers at GitLab right now, but if you're interested in like, which of the engineers are responsible for which of the stages of GitLab projects, that's a good page to start looking at, although it's pretty long. So I think that's the end of the presentation. David, anything else I may have missed or anything else you want to bring up? I can't think of anything else. I'm really good at doing the contrary. All right, thanks. And yeah, and I'll, any other questions that people want to like ask verbally or like a type on the chat window, I'll give it 30 or 40 more seconds for people to ask questions you may have. I mean, if you happen to like, you forget to ask me a questions if you think of something later, obviously just ping us on Gitter. I'll be happy to answer them as well. Just one more check on any questions or comments. If not, well, thanks for your attention. Happy hacking and I'm sure we'll be seeing you online over the next few days. Thanks very much. Thanks everyone. Everyone, bye-bye. All right then. Thanks a lot. That was really good. Thanks, David. Bye. All right, cheers.