 Okay, well, welcome to the wrap up session of the Q3 hackathon in 2020. Again, it looks like this is going to be another record-breaking hackathon with thanks to all your contributions. So I'm just going to spend a few minutes just wrapping things up. Obviously, if you're in the Pacific time zone in the U.S. like I am, I still about nine hours left in the day. So expect more contributions to come in for people mostly in North America as in Europe and APAC and other regions is already the September the 4th. So just a quick recap. I mean, first of all, thank you not just to participants who contributed MRs, but people who led office hours or tutorial sessions. I mean, all of it was done basically on day one like, like to just have those mostly in day one so people have a chance to watch them and work on contributions. So I mean, after the kickoff session, we had a couple of office hours from the runner team with Steve reviewing a couple of MRs. One of them was actually on documentation, which I'm glad Steve selected because that showed you some of the review. I mean, part of the review process that's involved in documentation. A lot of times it involves feedback both from like engineers and also from technical writing team who are more of like technical document experts in terms of like a grammar and documentation style, but sometimes in some cases they need to check with the engineers to check the validity of the documentation update. So I think one of the examples show that and he reviewed another one in the second half of the meeting. So I mean, recordings all posted on YouTube channels, but you can access it directly on the hackathon page as well. So feel free to watch the recording if you're interested in contributing to runner in the future. On the package office hour call, we actually had a couple of like very active contributors who were able to look at some of the MRs that were sort of in the queue for review. And actually we found out there were about four or five of them that the ball was sort of in our cord in terms of reviewing. So we're able to sort of repeat the reviewers to get those process going. And Tim also talked about some of the things that are up and coming in where we want community members to help us with. So we had good discussions there. And the next office hour was with Sam and Jeremy on migrating pajama components. And if you haven't watched the recording, I mean, they talked about not just the UI and front-end side of things, but Sam actually walked through a demo and showed that for, I mean, one of the epics they have, I guess they have two epics for pajama components. And I think between two epics there are about 1,000 issues. And Sam picked up one of the issues and in about 10 minutes he was able to complete submitting an MR. So a lot of the MRs we've seen a lot of them come in to really take like a 10, 15 minutes. So if you still have time to work on something if you're interested in front-end or UX, go watch that video. Or I mean, even after hackathon, I mean, like I said, there are about 1,000 issues. So plenty of other things that you should be able to work on. And release management. I mean, Jackie, she's a product manager for release management group talked about release management stage in general, but also areas where we want community members to contribute. And we also talked about some of the triage and review process within the release management team as well. So I encourage you to get to know more about release management and some of the things that we look forward to creating members contributing to by watching the recording. So that's all on the, they're all posted on the hackathon page. So this is a screenshot that I grabbed like a few hours ago. So moving right along. So, yeah, so this is sort of the running tally of what we accomplished so far. And if you look at issue number 41 under the hackathon project, we have a list of, I mean, at the top, you'll see a list of issues that we encourage community members to work on. And then we also have a running inventory of MRs that have been submitted. I hope, hopefully I didn't miss any of them, but it won't surprise me if I go through my inbox again. There are some items that I missed, but as like 30 minutes ago, I think there were like a 243 MRs submitted and the day is not quite over for a lot of places. But so, I mean, already we surpassed the record from the last hackathon, which actually, obviously, I'm very happy, but so much surprise. I wasn't quite sure if we will hit across the 240 threshold even this morning, but we did. So we're at 243 plus. And out of the 243 MRs submitted, 75 have already been merged. Like there's a couple of hours ago, I haven't checked since then, but so already a lot of MRs been merged. So thank not just the contributors, but reviewers who promptly reviewed and merged MRs and provided feedback when necessary. Just like in the past, MRs were not just for the main GitLab project, but other projects in GitLab like charts, runner, Giddily, GDK, GitLab UI and our website. So definitely appreciate community members contributing to lots of different parts of GitLab. And like I said, it's very possible that I may have missed your MR. I apologize if I did that and feel free to ping me like on the issue or find me on Gitter and let me know that your MR is missing from the list. I definitely don't want to lose track of any of those. So just let me know. So probably the last slide here, but just a few more like the logistical stuff. So on prizes, you again have this screen shot of the prizes available for grand prize and second place prize along with the merge MR prize, which is given to everybody who has MR merged by the 15th. So the only like one of the things that we try to do is be respectful of everybody's like a time zone. So we didn't specify like which time zone that you're supposed to be working in while you're submitting MRs over two days. But the one deadline that we have, the applause for everybody across all time zone is September 15th at 2300 UTC. So check your time zone. So what 2300 UTC translates to, but your MRs must be merged by that time on the 15th. Ping us if you need any help by meeting that deadline for whatever issue, whatever reason you have issues getting things merged. Because I mean it's possible that there might be delays for whatever reason like the review process wasn't swift enough or responsive enough. Just let me know and then happy to make exceptions if needed and if it's appropriate. So keep that deadline in mind. And the hackathon date for key four. I mean, I think why I like this is, I mean, I like doing this hackathon in the early part of the week. I'm not close to the 22nd, like near the release time. So I think reviewers have a little bit more bandwidth. So I'm going to stick to the first week of the month in December. So for those of you in the U.S., it'll be a week after Thanksgiving, I believe, and a few weeks before people go up for the Christmas holidays in many places. So keep December 2nd and 3rd in mind and I'll probably update the hackathon page sometime in the next few days. And as usual, I'll look for announcements on Gitter, Reddit, LinkedIn, Twitter and other social, or whatever other social channels that you pay attention to follow, to follow GitLab. I'll be making announcements. And most importantly, if you have any like a feedback from this event or suggestions for the next hackathon, including like tutorial session topics and others, please let me or David Plinella know, either on the GitLab.com or on Gitter and happy to hear and listen to your feedback and make the event even better next time around. So I think that's it, except again to thank you. I'm just going to pause here for a second to see if people have any questions or comments. Well, if not, for those of you who are still working at things, I'll let you get back to work. And for those of you who it's already December 4th, I'm sorry, September 4th. I mean, thank you for all your contributions. And I look forward to talking to you again soon. Thank you.