 Okay, welcome to the Hackathon Kick-Off plus a QWERTY meeting. So this is the first time we're combining the two sessions and that probably explains a larger number of people on the call than usual. So I mean, I don't know why I didn't think about this before. I think we have incidences where the kick-off and the QWERTY meeting coincided and what I typically did was to reschedule the QWERTY meeting, but I think it makes sense to combine it to get the larger community together. So I'm hoping this will go well and then, I mean, maybe we'll make this a tradition going forward with future hackathons. So I'm sharing this slide. Let me get into the presentation mode so you can see it better. So obviously, if you've been to the previous Hackathon Kick-Offs, it'll be slightly different. We'll spend about a typical 15, 20 minutes just to kick off the Hackathon event and then the rest of the time, about 20 minutes or so, we'll have a bit of an abbreviated session for the monthly QWERTY meeting. So yeah, just a way of introduction. I mean, David, you're suffering from a cold, unfortunately. So I mean, David, do you want to quickly introduce yourself or? Sure, sure. Yeah, yeah. Yeah. Okay. I was telling the others in the call before that I'll just have my camera turned off this morning, but other than that, I should be fully operational. I'm David, Director of Community Relations, I work with Ray and other people in the Community Relations team, and I'm here to address any questions and to otherwise compliment any info that Ray wants to give on the Hackathon. Yeah, and I'm Ray. Work with your code contributors at GitLab. And I mean, obviously, like I'll talk about this in a few slides, but please feel free to ping either David or myself, particularly on Gitter or even your MRs during the next couple of days. If you open MRs or have any questions, our time zones are such that, I mean, we should be able to cover for one another while the other person is not working. So feel free to ping both of us and we'll be happy to help along with the QWERTY members that are on the call. We'll get to in a minute. So the traditional sort of agenda for Hackathon kickoff. So without further ado, I'll just go through them. Just wanted to remind people that we do have a Community Code of Conduct at GitLab. You can go see the about page to get more details. But just like every good open source community, we want to have an open and welcoming environment. So just want to make sure that, I mean, not that we've had any incidences in the past during the Hackathon, but if you see anything that's inappropriate, I mean, feel free to report that to the email alias conduct at gitlab.com and email actually comes to both me and David. And I mean, just want to sort of remind people the Code of Conduct like we typically do at whether it's a virtual or face-to-face event at GitLab. Also just a quick reminder there, logistics, I mean, this is, you probably found these on the Hackathon page, but the kickoff session obviously starting now, I'll have a wrap-up session at 2300 UTC on Thursday. But you'll basically have two days to, in your time zone, to submit your MRs. In addition to working on MRs, we also have various tutorial sessions scheduled, starting in about eight hours or so, I believe. So we'll have a tutorial session from the GitLab Secure team. And for the first time, what we're also doing is having office hours for a couple of the product teams. The package and runner teams have started their office hours in January. I think the package one was actually only like about a week or two ago. And they wanted to have their second office hours to talk to community members, to coincide with the Hackathon. And these sessions are typically a little longer than a traditional tutorial sessions. Some tutorial sessions usually go for about 20 to 30 minutes, but the office hours are longer with a lot of discussions that we schedule for 50 minutes each. And if you happen to miss them because of the time zone, time differences, recording will be posted on our YouTube channel. So I'll also add a link to recordings on the Hackathon page when they're available. Logistics and support. Like I mentioned earlier, I mean, feel free to ping David or myself. But as you can see here, people like Regendra and others have been very helpful. And also court team members as well, helping community members when they have questions. So we have quite a bit of, quite a community building on GitR. I remember when we first started this, we had about like 40 people. We're up to like 437. And that was Alaska. And I saw a couple of days ago. So you should have plenty of people who can jump in and help you out as you're working on MRs or have any questions like on GDK. Let me quickly pause there, David, anything you want to add there, anything I missed? Well, yeah. And then just a reminder on the tutorials starting later today, your time on the 12th. So we got Tim and actually, there'll be other team members from the package team joining on the package office hours on the, let me actually go here, oh, I may have missed it. Give me a second. Yeah, I'm going to go to the main hackathon page. So if you go to the tutorial sessions for like the package and runner office hours, they'll have links to the issues for the particular office hour they're holding. So I think Tim's gone ahead and listed like potential topics they want to talk about during the office hours. So feel free to take a look there and add any suggestions or comments before the call. So even if you miss it, Tim or others may be able to cover those topics on the call and you may be able to watch it on recording later on. But so I encourage you to take a look at those issues if you're interested in either package or runner office hours and going back to the slide. So I listed the time zones, various time zones like particularly in Europe and the US for the office hours and the tutorial from David on secure and defend. You may have noticed that we had to cancel one of the tutorials on get tips and tricks. Unfortunately, there's been a scheduling conflict. So what I'm working on doing with that session is to potentially have a separate session in a couple of weeks rather than wait until the next quarters hackathon. So stay tuned for that. I'll probably broadcast on Twitter. If I if we manage to find a time in a couple of weeks to have a standalone session outside of the hackathon. So stay tuned for that. And I think the first topic we already talked about. I'm just mentioned me and David. To make sure that we count your merge request on the issue on the and the MRS will be tracked and listed on on that issue there. So, I think that's all. To mention as well. If you don't want to have to remember that issue, you can always go to the hackathon page to the landing page and then you'll find the link to it as well. Perfect segue. So if you see this counter just click on this. And then it'll take you to the issue. And that just confirmed that I had the issue number wrong, which I should change on the slide. But yeah, so thanks for that reminder, David. So it don't have to remember the issue number. And then as you saw, we're already at 26 MRS. So we're already off to a flying start. So I appreciate, I mean, I noticed like a people that are dialed in here who are already submitted MRS. Appreciate that. I'll fix this link later on. I can fix it for you. Thanks. Yeah, thanks. So the prices, I mean, just before I move on to the next slide, just one thing I'm going to highlight. The only time we sort of enforce like a strict UTC time zone is the deadline for the MRS to be merged. It'll be Tuesday, February 25th at 2300 UTC. So when you submit your MR as you can work in your time zone, but just be aware, like if you have any issues or concerns about your particular MR being merged by the 25th, I mean, please ping me and or David and we'll see what we can do. And then, well, when we after the MR merge deadline, the winners will be announced in a separate issue so you can, you can, you'll be able to find an issue under the hackathon project. Cool. And then, you know, I think it'll be better to for me to show the hackathon page versus the images pretty small on the slide. The prices for this this edition of hackathon, the grand prize is the same. This has been pretty popular 100 dollars to spend at the at the get lab shop. And so that's for person who has the most number of MRs merged. And for individuals with the second most MRs marriage, this is sort of a nice looking power charging station for your phone, your pot and and and your smart watch and confirm that it works with both Android and iOS devices so there should be any issues there. So that's the second prize, a second place prize. And for everyone who has MRs marriage, I found this nice packable duffel bag. So, so that those are our prices for this quarter. And I thought it'd be better to share it on the on the web page versus on on the slide because the image is pretty small. And thanks David for updating the slides real time. So the question typically comes up in terms of, you know, how typically how many MRs are needed for to win the grand prize. So you'll see that stat from the past six hackathons and in the red bar, ranging from like seven to like, you know, we had a huge number like 28 last quarter. But that's sort of been been the number over the past past events. And I mean we actually crossed the 100 MR marked 100 merger crest mark during the last hackathon. So definitely want to keep that trend going and I mean, like I said, we're already up to a flying start at over over 25 so things are looking good already in the in the in the early hours. But so just wanted to share that with you. Think, let's see. So, oh, suggested issues for the hackathon. So, if you go to actually the issue where we keep track of the MRs at the top, we have like suggested epics and issues that we collected this through a number of people, number of team members and get lab. We have a couple of big epics on on the front end. And then we think we have an issue for internationalization. And we also have like issues with the label good for first timers if you click on that link, you'll get a query results on on the issues that have the labels, accepting the marriage request and good for first time contributors. So these should be relatively easy for a lot of, a lot of new people to to tackle. So, I recommend that you take a look at these issues if you if you're looking for something that you want to work on, but also want to reiterate, I mean, just because there, there isn't an issue like already created. You shouldn't be hindered by issue not being not already being open if you if you think of something that you want to work on I mean go ahead and feel free to just open an MR and just just ping us and get started. I mean, don't worry too much about opening a separate issue or finding one that that you think is the right fit. If you think there's something that you think could be improved on. So even if it's like a fixing documentation just get started with an MR and then just let us know. Let's see more on getting help we already talked about getter just wanted to let people know about a couple of other resources if you're not aware of them already. One is we have a group of merger quest coaches I think we're up to 10 people. In the MRs, you can do this mention to to get coaches attention if for some reason, your MR is not being reviewed in a timely fashion, or in an unlikely event that neither David nor I are paying attention. I mean that's another group of people that you can you can ping with technical questions. And if you want to see a full list of like reviewers and maintainers you can click on this handbook page. And you get a huge list of reviewers and maintainers that you can directly ping. I've said this number of times like you know it's completely appropriate to mention or ping anybody within get lab. If you have any questions and I mean don't be shy about just directly asking people questions and asking for guidance. So I want to encourage people to do that. I think that might be the last slide on the hackathon. David or even other court team members if you have anything else you want to add please, please chime in. While I pause. I just wanted to say thanks for the thorough overview. But yeah just remember everyone that we don't just say it. Everyone can contribute. We live by essentially so if you want to to contribute to the hackathon. And if you got questions feel free to ask anyone don't be shy about about it and will be more than happy to help both people from the kid lab team or people from the wider community. Just feel free to ask on on your major quest or on Gitter and then we'll get you will help you get started. Are there any questions regarding a hackathon. You can either verbalize it or even type it in the chat window. Give about 20 seconds for people to ask any questions. Do you have any favorite or particular issue you'd like to see fixed or worked on on this on this hackathon. I'm sorry I was at David can you repeat that please. Do you have any particular issue that you'd like to see worked on or fixed during the hackathon. Yeah I mean I think of the ones that I think this one for Internet nationalization this has been open for a while. So I definitely like to see somebody take a look at this I mean this was open like more than two years ago, like, I mean 2017. So, I mean this would be a great one for somebody to take a look at. Or, I mean, I don't, I don't know how, like, maybe this is needs to be done in like a multiple MRs but yeah this would be something that like somebody to tackle and then the other thing I noticed of the 26 MRs that came in. And none of them were addressing these like a front end like ethics that are listed here which surprised me a bit. I mean this one in particular, it's got a huge list of things like number of issues that Scott listed here. All of them seem to have like a way to one and looks like they're relatively easy to tackle if you're interested in front end, but yeah those are just some of the things that I wanted to highlight. Excellent. Thanks. Yeah, sure. All right, so if there are no other questions and we can sort of switch gears to the court team meeting. So, I mean, here's the agenda for, for the court team and we have a bit of an abbreviated agenda, because we combine this with the, with the kickoff. What I could do is, I mean, in case people aren't familiar with the court team and get lab, we could give a quick overview and the court team members. I think most with the exception of one are probably on the call. I guess we're missing two. But so we have pretty good attendance and in terms of like a regular agenda topics I'm going to talk about the community events that we have happening in q1. I mean one of them is actually taking place that David and I can talk about and David I think you wanted to give a quick update on the advisory council discussion we've been having since probably like a December timeframe. So those are sort of the two main topics and I have like one question that that I have for the court team members in the AOB section. So let me just quickly jump in here and then I encourage like, I mean not just me and David but the court team members do jump in as well so this is in this, this image you'll take it to the court team page. So this is a snapshot of the court team page and it's got, I mean pictures of all about one of the court team members there. I think it looks like we're missing Takuya and then today on the call by rest of the folks on the call. So we have one court team member from from among the get lab team members but the rest of them are people who have made me sustain contribution to to the get back community. I mean I think for me if I'm not mistaken, I think most people have made like pretty significant contributions for like a year or so. I think it's at least to to get lab and these people are nominated and voted on to be selected on the front of the court team so that's sort of how the court team members get form and basically their mission, I mean to simply put us to sort of represent the wider code contribution community. I think it's a month to discuss any issues or topics that are that are affecting the wider community. And let me pause here and I'll let any of the court team members sort of sort of jump in and add anything I may have missed. Thank you. Alright, cool. Thanks, Dennis. So you're probably the longest serving a court team member right so I mean at least like three years if I'm not mistaken. I think Robert was was there before me. Okay, cool. Right. Well, and, and we do meet once a month and the meetings are actually open to everyone I mean we had people join outside of the court team once in a while but it hasn't necessarily been a regular occurrence. So I think that that's why it probably makes sense to sort of combine the hackathon kickoff with the court team meetings so that we have more people participating and listen to the conversations that are happening. And the items are discussed in public. I mean if I, if I typically have my act together I would open an issue like a week before the court team call and start listing or collecting topics for discussion. And we also do have a wiki page where you can find the committee notes and and links to all the recordings. And if you happen to miss the court team meetings. You can go to the playlist on on our on our YouTube channel and I'm actually kind of amazed like I for our January meeting like a couple of days after I posted it I noticed that there were like over 100 people do who actually view the recording. So I know people do like a listen to and watch your recordings. And I encourage everyone to do that and, and, you know, if there are topics that you think that that have been like missed or that we should talk about them you feel free to go to court team group issues and and suggest a topic or for future meetings I definitely encourage people to do that. So let me pause there. See people have any questions or I mean court team members that you're free to add any other commentary that I may have missed. And even the meeting notes are our public it's a Google Doc that's completely open and open to everybody so you should be able to like view the Google meeting notes as well, and I'll paste it on the chat window here. So people can see it. What I suggestion. Yeah, go ahead. My suggestion is that we use the sum of the weight of the metric costs and the relevant issues, instead of the account of the metric cost for the price. Can we repeat that I think I missed some of what you're saying. I, yes, I suggest is that could we please use the sum of the weight of the issues instead of the account, the account of the metric cost for the price. So, okay, and encourage many people to contribute more complex issues. Yeah, I mean, I mean that's that's actually a fair question. I mean that's, I mean, I'll let other sort of court team members and David jumping as well. I mean, in the past, like if I don't think there's been a whole lot of controversy in terms of like somebody getting a first prize. I don't think there were cases where somebody just worked on like a completely simple issues and and just manage to like a rack up the number of MRs. So, I mean that hasn't been an issue in the past and the other concern I have is, I mean the weight or the complexity of the MR. I don't know who would be like a objective person who can sort of make that judgment. I mean I can see where, if there is a tie amongst like, I mean, in the past, if there was like a tie amongst two people I think I awarded like a grand prize to like a both people, rather than trying to I mean depending on like a level of difficulty. But I'll just, I'll just stop there and see if David or anybody else has any other, like your comments or suggestions. I think I think we discussed this in the past. And we decided against it in the end because the not all issues have a weight assigned to them and the signed rate is highly subjective so it might be difficult for one person but it isn't for someone who was familiar with the code. So it's really hard to assign the correct weight and I think in the past we just looked at the MRs and if there was someone who contributed, I don't know 100 documentation fixes and someone who contributed one really large feature that was highly requested. I think we always managed to award the same price. So I don't think there's that much, many conflicts there. Perhaps one thing that we could consider on the next, on the next hackathon is to have a special price perhaps on the most voted or the most, the one and the issue with most weight. But then probably it might be worth for the person working on that issue to give a heads up that they're participating in that categories or making sure that the issue that they're working on has got a weight or has got some popularity of some upvotes. Yeah, I think that's something like we talked about in the past to me something like a like an MVP prize. Yeah, I mean maybe I think we even talked about maybe after the hackathon court team members can just vote on like one of the MRs is one that we want to highlight from the hackathon but I mean that's, I mean that might be something like easy enough to do, or as a first iteration. Thanks George for helping with the notes. Well, Mingwan does that answer your question like. No, thank you. Right. Thanks. Yeah, I mean let me know if you have any of the feedback I mean that's that's definitely a good question it was actually brought up in the past, like I think on a Reddit forum as well. But, I mean, definitely something that will will keep thinking about. Okay, just moving right along to the next agenda topic. I want to talk about community events that are that have happened that has happened or are happening in, in, in February and March in particular. So, I mean, if you've been following on Twitter. I mean, David and I were just that Boston. About a week ago had a. I mean this is sort of this was the second time that we had a formal presence at get lab with a stand. And then this time we were also able to secure a burst of a feather session so I post a couple of pictures there and had a lot of good interactions and and hallway conversations with people that were at the event. And also there's a link to the retrospectives. I mean, in terms of things that have gone well. I mean, the interactions were great. I mean people were just eager to come talk to us, both at our stand. And to my surprise that the burst of a feather session on Sunday morning was there was like a full house. You can see the picture there. I mean, I don't think there was a empty seat like towards the end of the, into the talk and we kept it like a very informal without a formal like agenda topic but we're able to fill like a lot at 4050 minutes with conversations that that community members brought up. So the interactions were great. We also didn't run out of stickers this this year like unlike last year I think we more than double the number of stickers that we brought to the stand and we're able to keep all the visitors happy. Which is which sounds trivial but it's a it's a big accomplishment. And I mean, I also like the fact that a lot of the get left team members that are there that you'll see in the pictures are were active in the various step rooms and David and I both spent a fair bit of time on Sunday in the community dev room. There are a number of folks in the in the dev room for go community and then any been coach he's been been one of the organizers for monitoring and observability dev room. So our presence was definitely felt. But I mean there are obviously things that we can definitely improve. Next year. There are a couple of like logistical items that could have probably helped us at the stand. And so forth you can, you can read more about it in the retrospectives, but I mean David, am I forgetting any highlights that that, or, or even areas for improvement from from the event. I think that's good. I mean, if anyone happened to be at the event and is watching the video and participated at both or came to visit us on the stand on the stand feel free to add your notes as well on the retrospective. This will help us making sure that next time around we will keep improving the event. But yeah, it was it was a great event as well. It was also good to see. And also to have meetings with some of the projects that we've been working on in the past under my oceans to to get up to that extent we talked to the non folks to the eclipse folks to the KD KD team and and so it was it was great to see some familiar faces as well and to catch up on things that we're still need to work together on. Yeah, and then yeah I think a couple of the heroes came by as well I mean one of the heroes actually from Hamburg he drove like eight hours to to to Brussels so that was great to see the wider community members. And we definitely plan on being back there next year. Cool, moving on. So the next event that David and I will be at, along with several of our colleagues on the community relations team is event called scale in Southern California and events not online. I think last time I talked to Ben. He looks like he was available to come join us. It happens in a couple of weeks I mean this is another event that goes over the weekend. And what we're doing at scale is we're sponsoring half a day called the get lab community day. So we'll have like a hands on workshop on how people can contribute to get lab tutorial on on using get lab through the various stages and several members of the community relations team will talk about various programs that we have for the wider community, not just for code contributors but evangelists open source programs and educational institutions. So I have a working progress a blog post that people can look at that where they can get more detail and we're hoping to get this blog post published by into this week. So it's a very relevant issue with more detailed discussions on on the agenda topics that we're working on for the community day. So feel free to take a look and and add comments there or if you happen to be from Southern California area and you want to swing by. Definitely will love to see you at the event. And the next one later in the month I know a lot of the court team members will be attending is is contribute. And I assume in the next couple of weeks more details will be sort of sort of come out. I noticed that a lot of there's already issues, various issues for workshops that have been accepted and self organized like activities that you should be able to find at that issue, if you click on it. And just like we, we did last year we invited several wider community members outside of the court team and we expect many of them to join us. So there's like one individual that's still having like a visa issues, but it seems like the most of the others like they should be able to join us so we're definitely looking forward to that. David anything you want to add here, or. No, just say particularly for scale come and join us. To meet you. Yeah, and there's just only thing I want to add I mean scaled. I mean I went there for the first time last year and I think they, I mean David you have a lot more experience with this event than I but it's pretty similar in in, in sort of the atmosphere as it is in, it's in foster and a lot of the grassroots type of open source people. So, if you haven't been to it and live in the area. Yeah, would definitely encourage you to come, come check us out. Let's see. Well, without further ado, I'll turn things over to you, David, and on the Community Advisory Council. Thanks Ray. Yeah, I just wanted to give a quick update, particularly to the to the court meeting. There's something that I have. I put on the backburn for the last couple of weeks but I'm starting to retake it and I'd like to to give it push for our final review this week. In fact, I'm going to remove the working progress marker today. Essentially most of the proposal is already is already there. I think the only pending parties having a means for whether community members to to to propose issues for discussion for the council, but in general, and perhaps shouldn't have gone very into it for those who are just seeing this for the first time. The Community Advisory Council is is a proposal that came up of came out of the discussions that we had just before Christmas. We had some some challenges in terms of in terms of communication, some some common stresses as well. And we wanted to make sure that whenever we do any change in terms of policy or in terms of affecting the terms of service. So we have some guidance and early review mechanism from the from the wider community. So with that spirit, and that's where that proposal was born essentially to have a team of individuals that can provide that that guidance and essentially keep honest. Thank you very much for the on the presentation. So, if you want to add your feedback in there, you're more welcome to and will be really appreciated and say I'm going to wrap it up this week for the final review. And then finally, perhaps the most relevant update in these few weeks, as we've been talking to some, some individuals to join the council as the funding members. So, as I said on the slides, thanks, George and Jacobo from the core team for joining for the as representatives from the core team. And then during the during first time we also talked to some of the team members from Gnome and Katie committed to joining the Council, we spoke to Carlos Soriano from Gnome. And so I'll let the initial migration to Github. And then we had a meeting with the KDE team, and they are interested also in participating. It's just a matter of nominating member from from their team. So I'll be adding that to the, to the, to the measure was a proposal as a, as an update to the proposal later on today. And I noticed also a comment from Vitaly on the on the MR. For some reason, the review office is not working. But I had to look in too much too much detail. I did an update this morning to retrigger the deployment it seems that the review I'm still not not working so I'll have to dig out what's going on there. So in this case, you can see the deep on them on the most request. Indeed, so I think that's, that's pretty much it. Again, if you have any feedback, please feel free to add it on there. Any questions on this, or I mean I think kind of like you wanted to follow up in this last month, but not sure if that address all the questions you had in terms of where things are. I think most of the questions I had are addressed. I'll have to look at the measure quest again. I'll do that today. But I think most of the concerns I had were addressed. Cool. Thanks. All right, thanks. Okay. Just move on to the next slide. I mean just said one topic for under any other business. I don't know if people have any anything else that people want to bring up, but I think the vast majority of the court team members will be a contribute should be next month. Sorry. Yeah, I'm supposed to be on vacation next week too. So that would have been a, that would not have been a good thing for me, but just wanted to ask if we should just go ahead and do we want to, I mean, I'm okay the way we can keep the meeting that will be like a week or two before we converge on to Prague or I mean, since we'll have a lot of FaceTime and contribute should we just cancel I just wanted to pull people on people's preference. Like I said, I don't have a strong opinion one way the other we can still have the call and more FaceTime and Prague. I think it would be okay to cancel it, but I'll be at Prague so I'm biased I guess. I think it would be interesting from to hear from the people who are not in the court team who are on this call, if they want to have a recording for next month or if it's okay for them to that we cancel it just to get an idea. That's an excellent question. So, I mean people that are not court team members, I mean, do you have any thoughts on whether we should keep the meeting or would people be okay if there is sort of silence with no recordings until like April time frame. Yeah, I think we can skip the meeting. We can have it in the evening. Thanks for gender any other opinions or even if it's not recorded, perhaps an option might be also to have a dedicated meeting in person in any case, or even perhaps an unconference session where other members of the team and of the community and also joined or in there. I think that's a good idea. And then if you know whether it's a sort of even a sideline discussion over meals like we can, if there are any action items or interesting topics that come out we can always document in this like the meeting now it's in lieu of the actual meeting. So even if it's like a three or four bullet points on things that we wanted to we talked about or things we want to work on. Yeah, definitely add it to this Google Docs here. So in lieu of the meeting in formal meeting. That's a good idea. Go ahead George sorry. I'll let you type. Great. So that takes us to the end of the topics, like any questions from from anybody on the call. I'm sorry about the hackathon or to the court team. Well if not, I mean thanks everybody for joining. Happy hackathon and hope to see you guys online. I mean I'll definitely see many of you online during during the hackathon but hope to see many of you come back to the hackathon me. I'm sorry, court team meetings in the future. Sorry, I'm stumbling. Thanks. Cheers everybody. Cheers. See you.