 Okay, sorry about that. I think I'm back. I had to turn another laptop going so I can record a session. Sorry about the delay. I think we were about three minutes late, but I will get started. Hopefully everybody can hear me okay and see the screen that I'm sharing. If you have any issues like curing or seeing the screen share, please make an order on the chat and we'll just get started. So again, my name is Ray Paik. I'm the community manager at GitLab. This is our actually our first anniversary of our hackathon and we started this in the Q3 of last year and I think David will be joining us in a few minutes. He's the director of community relations and he's also my boss. So he'll be joining us in a few minutes but it's exciting to kick off the fifth hackathon that we're sort of celebrating. So hopefully everybody had a good summer and ready to get started with the hackathon again. So the typical agenda that we have go over the quick reminder on the community code of conduct. I'll talk about various hackathon logistics and happy to answer any questions that you may have. And feel free to stop me if you have any questions or comments or concerns. You don't have to wait until the end. I have a Q&A section listed towards the end of the agenda but don't feel like you need to stop me. I don't feel like you need to wait until the end. Feel free to stop me if you have any questions. Just a quick reminder on the community code of conduct. Like all open source projects or most open source projects, I should say, we have a community code of conduct. There's a link there under the third bullet. If you want to read the bullet text, it's not terribly long. It's about a page of the website but basically says we are trying to foster an open and welcoming environment for everybody as they're participating in virtual, physical, face-to-face or online discussions. So we just want to remind everyone to be respectful. And if there are any concerns that you want to express, you can reach out to aliostericonduct.gov.com and just let us know that you observe something that shouldn't be part of the GetLive community and we'll address that right away. This is a standard practice, whether it's a virtual or face-to-face event. We want to remind people of the community code of conduct at all of our events. But if you have any questions, please let me know. Quickly, just six. If you participated in other hackathons before, this should look pretty familiar. This is a two-day online event. I mean, we do have a kickoff session that's starting right now in the wrap-up session at 2200 UTC on Thursday. But I mean, you can basically do your work. Based on your time zone, I know the MRs have already come in from the Asia-Pacific region, which I was happy to see because it's already in some parts of the APEC, it's already middle of the afternoon. So it's not surprising that some of the MRs have come in and pinged me with the hackathon mentioned. So we'll have a kickoff session and a wrap-up session. But I mean, you can basically do your work or submit your MRs during the two-day window, depending on where you're located. Any questions or if you want to have conversation with either me or other contributors, if you haven't already joined the Gitter Channel, I'll show you the screenshot in a minute. And you'll see a lot of activities typically happening with people asking questions and having discussions. So that's a good place to be if you're not part of the Gitter Channel already. And we also have three tutorial sessions, and I'll talk about the speakers in a minute. We actually have one right after this session. If you're interested in end-to-end testing, you might want to join that call as well in about 23 minutes. Then we'll have a discussion on the GitLab design system. If you're interested in UX and user interface design, and also we'll talk about the GitLab package stage. I think those sessions take place in about 10, 11 hours from now. And all the recordings, if you're not able to join, because of the time zone, if you have other commitments, you can watch the recordings in the hackathon playlist under YouTube. So you can catch all the sessions there if you're not able to join us in the Zoom session. As I noted, the Gitter Channel, if you're not part of this already, there are a couple of channels, GitLab HQ and contributors. I mean contributors is designed for people like you that are part of this session that are interested in contributing to GitLab. The last time I checked, there were closer about 300 people on the channel. I mean, we started with around 30 to 40 people during the last first hackathon last year, and the community has grown in the Gitter Channel. So you'll see a lot of people asking questions about specific issues, questions about GDK and anything else. Feel free to jump in there and ping me or David. You'll see our handles there. And hopefully we'll find an answer or find somebody else who can answer your questions. So that's sort of the first place you should go for support. And the speakers that we have lined up, like I said, we have our next tutorial session for people that are interested in contributing to our testing. So Ramya, we'll talk about end-to-end testing. And so that'll follow this session. And then tomorrow morning, Pacific time, we have Tori Davis and George coming to talk about the GitLab design system. I think during our first hackathon about a year ago, we had a session on UX design, but I mean, there's been some changes on how people have been contributing to our design system. So do join that session or watch a recording. So pretty excited about that session. And then about a 30 minutes following that session, we have Tim Rizzi, a product manager for the package group, coming to talk to you about the GitLab package stage. So continuing the tradition of various product managers coming to meet the community members. So in terms of MRs and prizes, when you do submit an MR during the two-day window on the 28th and 29th, feel free to mention either me or David. And you can type things like CCR, PIC, and deep planella. And just remind us that the MR is for the hackathon. And basically, we have an issue. And I'll switch the window where we're going to have a list of MRs that have been submitted for the hackathon. And you see that three of them have already been submitted, like I said, from the APAC region. So we'll keep a running tally of MRs here. So, and the prizes, the rules should be somewhat similar to the past hackathons. I mean, anyone with a merged MR will receive a prize. And we have a grand prize for a person who has the most number of MRs merged over the next couple of weeks. And we'll also have an award for the second place winner. Because I mean, I think we started out just giving you a grand prize. And a lot of people have been coming relatively close to the grand prize. So we started awarding second place winner as well. So the MRs needs to be merged by September 10th, 2300 ETC. So that's sort of the one from deadline that we have. That's not dependent on your local time zone. But this is sort of the one deadline that's common to everybody. We try to give people an ample amount of time for MRs to be merged. So please keep that in mind. And then I do believe that we have that highlighted in the main hackathon page. But if you have any questions on that or concerns, let me do it. Let me know. And the prize winners will be notified in an issue. So basically, we'll have a list of people who had their MRs merged by the deadline and that will also announce the winner there as well. So keeping with what we've done in the past. And then just also want to show, I mean, this is on the main hackathon page as well. But these are the prizes. Obviously, this is being the first anniversary of the hackathon. We wanted to create something custom, just sort of commemorating the event. So I think this is something that people like to use with a lot of mobile devices. So this is obviously a power bank for yourself or in a tablet that you can use. And I have something similar that I've been using for the past three or four years. And it's still working pretty well. So hopefully, this will be of the same quality. We have the fabric speaker lined up for the second place. And for the grand prize winner, as we've done in the past, basically, you get to spend $100 at our merchandise store at shop.gitlab.com. So you can pick a gitlab merchandise of your choice. Cool. So just moving on, just wanted to give a, provide a quick stat over the past four hackathons. This shows you the number of MRs that's been submitted during hackathons. And we had a pretty good clip of growth for the first few quarters. And then we took a bit of a dip in Q2. So I definitely want to reverse that and get up to the number that we are used to seeing in Q4 and Q1. I wouldn't mind breaking the record with the number of MRs, but do keep it coming. And people have been asking, you know, for the grand prize, like how many MRs were merged for those grand prize winners? So that gives you an idea, like it's been like between the 7 to 13 range, but that should give you an idea of how many MRs that people had merged to claim their grand prize. I think we can move on to the next slide. And sorry, this is a bit of an eye chart. But I think this is a wide blank. So if you go to the hackathon issue at this section here, it has a list of like suggested issues, I mean, good for like a relatively new contributors and put and lists of issues that are that are good for somewhat more experienced contributors. I mean, you're obviously welcome to any other issues or even on anything that issues haven't been open yet, but wanted to give people a starting point if you're not sure where to get started. So this hopefully is a helpful place for you to get started. But I mean, if you, like I said, if you see other issues that you're more interested in, or you want to create an issue that you want to work on, you're more than welcome to do that. This is just a restarting point that people can use. So feel free to use, look at other issue boards and find places where you can contribute. Let's see. And yeah, and that is very possible that on this on this issue, the other people might be adding like a different issues that that we want community members to take a look at. So come back once in a while to to see if there's an updated list. The slide may not be updated, may not be up to date, but this will be the single source of truth where all the issues are listed. Okay, and then I think I have a couple more slides. Last but not least, about getting help during the event. I mean, I already talked about the Gitter channel. Feel free to post questions there. But I mean, there are a lot of other resources where you can get help. I mean, not just during the hackathon, but in general, we have the merger request coach. So feel free to check out that page to find out what what a merger request coach is. But I mean, typically, if you're not sure, like who to ask for, who to go to for help, or if you want to find the right reviewers for your MR, you can mention the MR coaches in your MR issues to get their help. And I think I'm actually also in this group as well. So I automatically get pinged. So I mean, not just during the hackathon, but in the future, if you have questions about an MR that you don't think are being addressed in a timely manner, just feel free to mention the MR coaches. And one of us will be more than happy to help. And if you want to find specific reviewers and maintainers for different GitLab projects, this is a good link to go to. It's part of our handbook. It's relatively long. You'll see a long list of people, but it'll give you an idea where you can go to for help. So hopefully that helps. So I think I went through it real a little quickly. I just want to make sure that we got several people online. I want to make sure that people if people have any questions that you're free to ask, either raise your hand or type a comment in the chat window or go off mute and verbalize your question, that would be great. I'm going to give it a couple more minutes. It looks like everybody's good to go. We're ready to get started. Oh, it looks like there's a question. For the hackathon, during the hackathon, I mean, the first place to ask questions is probably I would start with the Gitter channel. Because usually either me or David, for example, we have a decent coverage in terms of time zone. David's in Europe. I'm in California, so one of us should be up watching the channel. So start with the Gitter channel. And if no one's responsible for several hours, then do ping the MR coach. But Gitter would be a good place to start with your questions. So cool. Glad I was able to answer your question. Any other questions or concerns? Cool. I guess we're good to go. Excited about our one year anniversary hackathon and looking forward to your MRs. And for those of you who are planning to join our next tutorial, I'm used to it. I see that Ramya, you're on too, but we'll see people again in about 10 minutes. And hopefully by then, I'll have my technical difficulties figured out with my laptops. But cool. Thanks, everybody.