 All right, welcome to the Q2 2020 hackathon kickoff plus May courtee meeting. So just like we did in February where you decided to combine the kickoff with the courtee meeting, obviously the world has changed slightly since the last time with their hackathon. But good to have all of you on the call to give at least me a sense of normalcy. So I definitely appreciate that. So the first half of the call, we'll just talk about the hackathon that's already off to a roaring start. I don't know if people notice. We're already up to 20 plus MRs. So that's pretty awesome. So we'll spend about 15, 20 minutes talking about a hackathon and logistics. And then we have regular courtee meeting topics that we have at the second half of the call. And for those of you that are joining for the first time, please feel free to stop me if I'm not being clear about something. Or if you want to ask a question, and please feel free to type questions on the chat as well if you don't want to verbalize. So a quick intro. I mean, David, do you want to quickly introduce yourself? And then I'll do the same and we'll get started. Cool. So yeah, I'm David. I work on the community relations team. I'm based in Europe. And the way I participate in the hackathon essentially is covering for a time. Well, Ray is not there. Feel free to ping me on any issue with my handle diplomat. Cool. And I'm Ray. I'm based in California. And like David said, I think we have a decent coverage in terms of time zone. So if you ping either one of us, particularly on Gitter, we should be able to jump in and help out. And believe it or not, I think this is the eighth edition of the hackathon. So glad to get this thing going. And I don't know how many people are joining for the first time. We're sort of sticking to a usual routine for the hackathon with some tweaks. So this is the agenda. We'll talk about logistics, schedule, prices. And I also want to spend a decent amount of time on there are a lot of good issues that people have suggested from the GitLab team members. So I want to highlight those as well. I mean, a number of people who already started working on those. So I think we have a number of good ones, particularly from like a UX in front end that are good for like a hackathon, good bite size chunk issues. So make sure you'll spend a decent amount of time talking about those. Just a quick reminder on the community code of conduct. I mean, this is obviously a virtual event. But like we do at all the events at GitLab, like to remind community members about the community code of conduct. You see the link there that you can read the full text at your leisure. But I mean, just want to iterate that just like any good open source project, we want to foster a welcoming and opening and open environment for everybody to work together. And I mean, if you see any concerns or inappropriate behaviors, I mean, feel free to use that email alias conduct at GitLab.com. The email should come to both me and David. I mean, fortunately, we haven't had any issues in past hackathons and hopefully it stays that way. But just want to give people a quick reminder on the code of conduct. Moving right along logistics, I mean, obviously, this is a two day virtual event. I mean, we want to respect you at the time zone that you're in. So I mean, a lot of the MRs that came in, I mean, so far that I already mentioned, they came from Asia Pacific time zone for obvious reasons, like even before this kickoff session. I mean, the kickoff session is just sort of there to sort of kick it off to mark the beginning of the event. We'll also have a wrap up session Thursday evening. I mean, you're at the end time. But obviously, if you're in the Pacific time zone that you are like I am, you'll have several more hours to work on it. But that's just sort of unofficial demarcation of the beginning and the events. And just like we have done in the past, in addition to people working on MRs and hacking away, we do have a couple of office hours. The package and runner teams are back. Those teams have been doing monthly office hours. And I mean, it just made sense to coincide them with the hackathon to get more people participating. So they're back. And GitLab Monitor Health, there will be a tutorial on GitLab Monitor Health. I mean, there are a number of contributors that have been contributing to that group over the past couple of months. And I've already seen a couple of MRs for the health group. So definitely looking forward to that. I mean, Sarah, she's a product manager. She'll be talking to the community members about in case you're not familiar with the stage or the group. I mean, you should be able to get more familiar with it and where she's looking for community members to help. And if you're not able to participate in those sessions live, those are all posted on the hackathon playlist. I'm going to do my best to post them as soon as the events are over. And I mean, I've been pretty really pleased with not only the people participating in those sessions, but I mean, typically within 24 hours I'll typically see like 100 plus views on each of the recordings, which is pretty amazing. Whoops, I think I have a typo here. Let me just advance the slide. Sorry about that. I mean, that's just sort of a, I don't know, that suggested issues to work on. Bullet ended up there. But I'll talk about that in a few slides. And here are the tutorial sessions. You should have all the Zoom links. And this isn't the latest and greatest screenshots, but I think there will be links to the presentations or issues for office hours. So you'll have the latest information on the Hackathon Tutorial Sessions page. Let me pause here for a sec. David, do you think I, let me know if I miss anything here. Can I apologize for that? Yeah, go ahead. By the way, it was me doing the Ninja edit adding the same issues, bullet point in there. I just wanted to highlight it. But yeah, we can cover it later on the slides. I just wanted to make sure that people are aware of the fact that they can work on there on the issues that they're interested in. But there's a list of, there's great at least that product managers and engineering managers and also Ray essentially put together for that might be interesting for people to get started on. Cool. OK, thank you, David. Yeah, I mentioned Gitter earlier. So I mean, we're well over like a 500 people that are in the community in the contributor room. This is usually the best place to get help. I mean, not just during hackathon, but during regular times as well. I mean, there are not just me and David, but there are a lot of community members there. I mean, they can help answer questions on, like if you get stuck with something on GDK, for example. I mean, this is usually the best place to get help. So I mean, feel free to use it. And then I mean, during the hackathon, feel free to ping me or David that we can jump in and try to try to help you out during the event. Oops, hit the wrong button. OK, and just want to talk about the MRs and prizes. So when you submit an MR, a number of people have already done it. They've sort of used the routine. In the comment box, it just mentioned me or David. I mean, just mentioned that this is for the hackathon and we'll continue to track those on this issue. Let me just click there and show you the page. So yeah, your MRs will be sort of added to the list. And this is where we get to count of, as of at least 30 minutes ago, I counted like a 21 MRs and three of them already merged. Takuya, I think I was able to merge a couple of your quick documentation fixes. So thank you for that. So this is where we'll create a list of MRs to track. And then even in the issues directly, like a lot of people have done, just feel free to just ping me here as well. And then just bring it to our attention and we'll be happy to add them to the list. Let's see. And then on the main hackathon page, we have an MR counter. So you'll see it here. So you'll see the running tally of how many MRs have been submitted so far or during the hackathon. So and the prices. So this is pretty similar to what we've done in the past. I mean, we have a grand prize for most number of MRs merged and we also have a prize for a second place winner. And as I noted, I mean, in terms of like doing the work during the two-day event, I mean, we want to make sure that you're able to work during your normal whenever you normally contribute to GitLab. So it's just work during your normal time zone. The only time we'll have is like a deadline, enforce the same deadline for everyone is a deadline for MRs to be merged. And that's 2,300 UTC on May 26. It should be a Tuesday because Monday is a holiday in the US. I just want to get people on this additional day for MRs to be merged. But if you have any issues, like for whatever reason, you feel like there's a delay in MRs getting merged. I mean, feel free to reach out to me and I'll make sure that we'll find a way to expedite the review or count them as a MR that's been merged. And then I'll open a separate issue to notify the winners. And if you go to this link under the hackathon project, you'll probably be able to find issues from the past hackathons where we announce winners. So that's a quick logistics on prizes and MRs. So here's a quick screenshot of the prizes for the Merge MR and the second place prize. And the grand prize is like we've done in the past. This has been pretty popular, like $100 to spend at the store. So, and actually, Samantha's who's on the phone or who's online, she's going to help us with that. So thank you, Samantha. Appreciate that. Cool. Yeah, so hopefully you'll like the cross body bag. I was looking for something that when things sort of get back to normal, people can use either during commute or when you're traveling. But hopefully those days will come pretty soon. And also a charger, a wireless charger for your mobile. I mean, most likely your phone. But it's covered in fabric, which I thought looked pretty nice. So hopefully people will enjoy that. OK, just some quick stats. And obviously, we've been having like a phenomenal growth in terms of like MR submitted. And what you'll notice from Q2 of last year, actually about a year ago, we had a disappointing drop. And I think one of the issue was I actually, I think if I remember correctly, the Keith Hackathon last year was scheduled during the last week of May. And it turned out that, I mean, not just in the US, but several countries had a holiday that week. So I don't think a lot of people were very active. So it'd be interesting to see what happens this year. That's why I consciously decided to sort of pull it closer to the middle of the month versus like doing it in latter part of May. And a lot of people ask about, you know, in terms of grand prize, like how many Merge MRs were involved, so I just went to sort of share that data. I mean, we had a really high number in Q4, 28. But so you'll see the record there between like 7 and 28. So it would have been the number for the grand prize. All right, so yeah. And this is something that David brought up earlier. So if you go back to the issue where we track the MRs, if you look at the top of the page, this is where we have sort of recommended or a short list of issues that we think would be good for hackathon. And there's a query that you can easily do for issues that are good for first time contributors. That's one of them. And the second one on Gitter, I mean, this is something that I added. I talked to Eric on the Gitter team. And if you use an iPhone, like you'll notice that if you try to log on to Gitter, you can't use your GitLab ID. But you can on Android. So for selfish reason, because I have an iOS device, one thinker is community members to work on that. And then here's an MR that actually a community member did for Android last year. So hopefully you can use it as a reference. And that's one of the issues that we have for Gitter. And then here's an issue just like a cleaning up like old feature flags. And then if I go to this issue, I mean, one of the contributors from Indonesia already started working on this earlier today. But here are relatively quick and simple ones that you can help out with. This is also labeled like a good for first time contributors. So I marked off the ones that Gilang is already taking care of with his MRs. But here's a good one. And if you're interested in the front end, I mean, here's an Epic that's got a lot of issues listed here. And then, I mean, I'll tell you probably now, I mean, last few hackathons, the Epics and issues from front end teams have been like gold mines. I think last quarter we had about 50 MRs that were merged with a couple of Epics that the front end team created. So there are tons of issues here that you can tackle. I think our ruins probably started working on this even for some of these, even before the hackathon. But this is probably a good one for you to look at if you're interested in front end. And then we also have about a dozen or so UX related issues that UX team added here just a couple of days ago. So here are the ones that you can probably tackle. I don't believe anyone's started working on these yet. So these should be all available. So I encourage you to take a look at these. And then as David mentioned, I mean, if there's something that you want to fix, but I mean, you can't necessarily find an issue that's completely fine. It's not like having an issue is not a requirement. But if you're looking for guidance on things that are good for hackathons, it should be a decent list of things that hopefully will be good for a lot of new contributors and good buy size issues that people can tackle during the hackathon. Natalia, actually, do you have any thoughts on this epic for view event hub submit? Or I think it's like pretty. Actually, I've created a better epic for this. This is a part of the bigger epic. You can see an ancestor-refector-deprecated part. And then we can take another epic from there if we don't have enough for the front end, because we also want to get rid of slots in the view also lot syntax. So if you look for more front end epics, there is one more epic here. Yeah, a migrate view slot attribute. But I believe this should be tackled. And we need to add issues there, because there is only a list of components. OK, cool. All right. Yeah, it looks like Scott opened this couple of weeks ago. Cool. I think it would be cool to add some back end related issues to the list, because I've seen only front end. Yeah. Right. Yeah, I think, I mean, actually, Natalia and I talked about this probably a little over a week ago, because I think I reached out to the back end team, or at least on the back end Slack channel, and see if there is something similar we can do on the back end side of things. And I haven't necessarily heard back. But I think the part of the challenge is there's a lot more dependencies on back end related work. But yeah, I can certainly reach out to the Slack channel again and see if we can come up with something. But that's a good point. So OK. I think that's all I wanted to say about the issue. David, was there anything else that you wanted to mention here? Or I think there's also one for internationalization that's always been there for a while. Yeah, I wonder if we should. I mean, we had in the past a big list of internationalization issues on an epic. So that reminds me whether we should have a look at that. In any case, no, I don't have anything else to add to that. I'd be, given the progression that we've had with participation and a number of issues, a number of MRs submitted, it'd be awesome to aim for 200 MRs submitted on this edition. I think it would be great to showcase the work that our community is doing. Yep. Cool. OK. Sorry, though. Just a small note, if you've mentioned it already, apologies. But in the past, I've had a tendency to accidentally start work on an MR for an issue that maybe already has someone working on it. So that's something maybe for people to look out for and just triple check that not only, you know, it might say that it's accepting merge requests, it might not have a sign-e, but just double check whether anyone's made a note to say they're picking it up or if there's an MR in progress, and maybe just to add a note yourself if you are going to be picking it up. Yeah. Yeah, that's a good point. I mean, unfortunately, that does happen. I mean, it doesn't happen that often, but it does happen once in a while. I mean, if you're not sure if the issue is still, I mean, something that you need to work on and feel free to ping me or like other GitLab team members that are on the issue. And yeah, I mean, I think double checking is not a bad idea. I mean, what I typically try to do is when somebody expresses an interest, I would assign it to them. But yeah, a lot of times like issue sometimes doesn't get assigned right away to folks. But yeah, that's a good tip. Okay. Moving right along, in terms of getting help, I think I got like a one or two slides left here. I already mentioned Gitter. I mean, that's probably the best place to start in terms of getting help, but there are other resources as well like GitLab. There's a merger request coach that you can mention on MRs with this, you know, with this mention. Whoops, sorry, I hit the wrong key. And then you can also like a ping reviewers and maintainers. If you go look at this page, you'll see a table of like all the maintainers listed. And I mean, I say these over and over again, every time I talk to contributors or community members, it's a completely fair game to mention anybody at GitLab. I mean, don't be shy about doing that. I mean, I'm a GitLab employee, but before that I'm a community member. So we owe it to everybody to get back to people. So don't be shy about like I mentioned people in issues or MRs. But I mean, during the hackathon, I mean, feel free to mention me or David, that's probably gonna be sufficient. But in general, you can always like reach out to merger request coaches as well. And they should be able to help out and answer your questions. I mean, we do have like, I think the numbers up to 10 coaches right now. So we have a decent coverage in terms of number of people available like the front end, back end and other areas as well. So I think that's it. Wanna make sure, let me see if people have any questions on chat, don't see anything. But if there are any questions on the hackathon, just let me know. Pause for about 10 seconds for any remaining questions or court team members, if you have any feedback or comments that you wanna provide for hackathon participants, let me feel free to chime in as well. So if not, we'll just transition to the court team meeting. And as usual, I probably need some help with the note taking here. So let me post it on the chat window. So Google doc with court team members, if you can help out with note taking, I appreciate it. Yeah, all right. So in case people are just joining the court team meeting for the first time, I just wanna give a quick introduction of what a court team is. I think I did the same thing last quarter, but I'll spend a minute or so talking about or explaining what a court team is and the rest of the agenda topic that as I listed on the issue, excited about the two court team members. A couple of people already chimed in, so wanna welcome them to the court team. And I wanna talk about GitLab Commit, that's a virtual event that's coming up in, I believe that's the last week of August. So I wanna encourage people to participate on GitLab Commit, particularly with the CFP that's open till June 1st, I believe. And then a topic that's sort of been near and dear to Lee, I mean, particularly you just dialed in at like a four in the morning last week on a GDK office hour. And one of the things that we want to talk about was improving GDK documentation. I opened an epic for that topic. So I wanna spend some time talking about that and any other topic that people wanna discuss we'll make sure we cover those as well. So moving right along, just a quick intro on the court team. I mean, the first link is a link to the court team page. I mean, basically we're up to about 10 people now, I think with the two new additions. I mean, basically the main charter or the court team is to be the representative of the rest of the code contributor community. I mean, these are a group of people, I mean, that have made sustained contribution to GitLab for a number of years. And so, I mean, they bring a lot of experience and not just in terms of like contributions and not just in terms of like using our product, but you know, representative community, I appreciate the feedback that you've been able to provide over the past couple of years that I've been at GitLab. So, I mean, think of the court team members as representatives of the community. And the monthly meetings that we typically hold it on like a second Wednesday of each month and the meetings open to everybody. And then the agenda topics and all that is discussed in the public issue. So, if you click on the like a court team group link there, you'll see the meeting agenda and discussions from the past. And then we're one of the few groups, I guess, like GitLab that use a wiki. So, I post all the materials and notes on the wiki page for people that I think it makes it easier for people from other communities to consume. And then we also have a playlist of all the meeting that gets recorded. I mean, this has been pretty fascinating. I'm like, with very little marketing I'm amazed at the number of people that typically view the recording within a couple of weeks. So, I know this is, people are listening and watching the recordings. And so that's all available publicly. I mean, anybody can join the discussions anytime. But yeah, so this is, just wanted to give you a quick introduction on the court team. David, anything you want to add here on the court team? I may have like bumble along in a couple of places, but. No, I think, anything else that I can think of right now? All right, so as I mentioned, we have two new members. I mean, I couldn't, I think it's been, at least been more than a year. Last time we added new people to the court team. So, I mean, the other thing I didn't mention about the court team in the previous slide was that we have up to two people that are actually GitLab team members, but rest are from the wider community. So, I'm definitely excited to welcome Lee from the wider community and Natalia from the GitLab team. And I'm gonna, I don't wanna put you on the spot, but Lee and Natalia, if you wanna give a quick introduction, because I don't think you met other people on the court team or other people on the call. So, Lee, I'll, sorry to put you on the spot first, but if you wanna just tell us about yourself or you're located and how long you've been contributing to GitLab, that would be great. Yeah, absolutely. So, I think I'm based in the UK and started using GitLab a couple of years ago. I've run a small software development company and yeah, essentially probably six months after that. So, 18 months ago, I wanted some additional functionality and found out that, you know, through the open source project, I can actually contribute that functionality. And then got rather hooked, I guess. Cool, thanks for sticking with it. And I think, I mean, I think George and David, you may have had a chance to meet with Lee in London. I don't know if you did have a chance or not, but I mean, Lee, it was definitely nice to meet you at GitLab in London. Yeah, it was a great event. And looking forward to normality when we might get the opportunity to meet another. Yeah, well said. All right, well, Natalia, do you wanna do the next introduction yourself really quick? Sure, so I'm Natalia. I'm a senior fountain engineer in the process of promotion. So hopefully soon to be stuff. And I'm working for GitLab since November, 2018. And I actually met some 40 members at GitLab contribute last year. Hi, George. And also outside of GitLab, I'm a view core member. So it's one of the major JavaScript frameworks. So like two core members, I feel like a dual core right now. And thanks. There you go. Welcome. One company in Natalia. I like the dual core. Like some of the processor companies may try to hire you. All right, cool. So yeah, speaking of GitLab commit, and yeah, I mean, unfortunately this, I mean, a lot of the events, pretty much for the rest of the year, it sounds like not just like GitLab, but rest of the industry is probably moving online or virtual. So the GitLab commit, the only one we have on schedule is on August 26th. And it's gonna be an online virtual format. And then I have a link to the event page. And I mean, definitely wanna like encourage everybody, not just to participate in the event, but we also have a CFP that's open until June 1st. So got like a two to three weeks for people to come, like I think about like a sessions, I believe there are four tracks. If you go take a look, why don't I just go there really quick and make sure that I'm not just making this up. Yeah, I think there's DevOps, key studies. And so you'll see the details here in terms of event. So I definitely encourage people to think about like a submitting a CFP if you have an interesting topic that you wanna talk about. And I mean, George, you've done this a couple of commits last year. I mean, if you need help with the CFP or even putting the presentation together, I mean, feel free to reach out to me and David. I'll be happy to introduce you to folks in the marketing team. So I definitely encourage you, wanna encourage you to do that. And also, I mean, some of the things that I, I mean, what I've done in some of the events and the commits in the past is I think I've done like a two different panel type discussions. So if you have an idea for that and if you need me to help or participate in that, I mean, just please let me know as well. So I think like if you've been on Twitter, I think the announcement started going out in the past week or so. But let me know if you have any questions, but definitely wanna encourage people to participate or even think about giving a talk. I have just a link there on the presentation. There's also a virtual meetup. I think Emily Chin are organizing to provide some guidance on how to get selected to speak at heatlock commit. So essentially there will be some discussions and guidance around writing a good call for papers, CFP and then having good topics as well to, if someone is interested to submit a talk and then definitely suggest to check out that either the session live or to order recording afterwards. Well, yeah, I mean, I think the benefit of being virtual event, I mean, obviously we're not gonna be face to face, but I mean, there's no, I mean, you don't have to travel, which is kind of nice. Like it could be taxing at times. So hopefully, I don't know if we have information on the time zone for the event, but unless the time zone is on or us, I think they might make event participation easier because you can just do it from your desk at home. All right, well, thanks for that. I might join that meetup myself. Cool, so moving on to the next topic. I mentioned the GDK office hours. We also have a playlist for GDK. So, I mean, I unfortunately forgot to record the first office hour that we did two months ago, but the one we had like last week that Lee participated in, that recording should be available there. So we talked about a number of things. I mean, not just about documentation, but also about ways to improve GDK in general. I mean, we actually have a team of people that are actually dedicated to GDK. It used to be more of a volunteer effort within GitLab, but with Lucas and Ash that are actually working on improving the GDK itself. I mean, Lee, you probably remember other technical details better than I do, but I mean, I was excited to hear about things like a GDK pristine. Like if your GDK gets broken, like you just run a command to get a pristine install of GDK. So there are a number of activities that Ash and people are working on. So that's pretty exciting. And one of the things that I felt like an area for improvement was actually improving the documentation. And I'll go to that link for that EPIC, which I opened last week. And then Patrick and others like added a lot of different issues as part of the EPIC to improve the GDK documentation. I mean, one of the things that I think that's relatively easy to fix and I'm probably gonna start working with the docs team on is we don't have a dedicated page for GDK on docs.gitlab.com, which I think is unfortunate because I think a lot of times people can get sort of directed to the GDK read me page, which I don't think is ideal. So that's one of the things that I wanted to talk to docs team about updating and there are a number of things. I think Patrick actually went through the exercise of installing GDK on a couple of different operating systems and there are some corrections that he wanted to make on several sections of the doc. And I think Ash also talked about right now the setting up of GDK is separate from like the prerequisites in terms of documentation. And that seems kind of unnatural. So there are a number of issues here that you can probably take a look at for improving documentation. But obviously we welcome your ideas and feedback because you probably are a lot more experienced than actually using GDK than I am. But Lee, anything else that you wanna add here that I probably missed like a lot of details that we talked about last week with Ash? I think the survey is interesting to kind of collate some information around how everyone's developing, what operating systems, what tools they're using and kind of work out where some of the focus is. And certainly from my point of view, I believe I'm in the minority being a Windows developer. So kind of understanding the best way to get up and running and streamlining that kind of process. Yeah, I think like one of the things I talked to, I mean separately because Patrick couldn't join the office arrow last week was like, I mean, even like some of the operating systems that are listed there, we're not quite sure how well all of those are supported in terms of like GDK actually functioning well, but that's obviously worth investigating. So any thoughts from like other core team members on GDK documentation in particular? Yeah, hopefully we'll tackle some of these, at least some of the issues that are captured in the Epic in like this quarter, next couple of months. And I'll keep people up to date, but definitely welcome any feedback or ideas that you can add on the Epic or any of the issues that are listed there. Yeah, so I think that's about it in terms of the two or three major agenda topics. There are other topics that people want to discuss. Let me make sure that. Oh, one thing, God, sorry. Sorry, a little off topic, but this morning when I woke up, I had a quick look on my mobile phone at the HackFond page. I suspect this isn't specifically the HackFond page. I imagine it's the whole of gitlab.com, but it isn't very mobile friendly. I think the table was the specific part where it said about the prizes. I could only see the left hand two and a half columns. There was no scroll bar. So again, maybe that's an easy for a UI person, little MR to maybe pick up for the HackFond. OK, that's a good feedback. I mean, I have to admit, I don't think I checked the HackFond page on my phone, but something I probably need to do. Yeah, it seems that the table is responsive, but then at some point it stops me. Responsive, but yeah, I think that's a really good point. So contributions are welcome, not just on issuesforgitlab.com, also on the website and particularly on the HackFond. It's a page that gets more visibility during the event. I mean, I personally, one of the things that I would like to see in there would be more visibility on the list of suggested issues, so rather than them being a link that could be buried within the page to have the actual list on the front page itself so that people can just visually see the list of issues. But yeah, I'd say any contributions would be really more than welcome. Thanks for the feedback. OK, any other topics, anything else? Perhaps one last thing. If people are interested in knowing what's going on at the HackFond, or then refreshing the page to see the list of MRs submitted, then they could also subscribe to the HackFond label as well. OK, any other topics or feedback? All right, I guess we'll wrap things up. Happy hacking. I'll talk to you guys again soon. Thanks, guys. Thanks, everybody. Have a good day. Cheers.