 All right, so welcome to the August core team meeting. Thanks for joining. Hope you're all having a good summer. So I sent an agenda topic on the issue, I think it was yesterday or maybe it was a couple of days ago. I think there was like one suggestion to the topic from Yakopa, which I appreciate it. So roughly this is the agenda. We're gonna talk a lot about the, about a lot of events, but we'll talk about the hackathon. Not sure if you've seen an announcement on the GetLap Heroes program. Wanted to talk about that briefly. And some of the upcoming events that I think I either, like I posted on Slack channels or give everyone a heads up on. And if we have time, obviously we can talk about other topics, but was there any other topics that you wanna put forward here? Or should I just get started with the slides? Yeah, I just started the topic about the single goal base in the last slide, but yeah, we can talk about it. Okay, cool. Okay, cool. It's Danny here. Sorry, I just interrupt. It's Danny here. I've just joined GetLap here in Sydney, Australia. Oh yeah. So I got this invite. Am I supposed to be on this call? I mean, the call is actually open to anybody. So you're more than welcome to stay. I mean, it's a public call. But I mean, if you have other things going on and that, I mean, you feel free to drop off, Danny. So I appreciate your... Yeah, I mean, I'm interested in listening in this hackathon actually. Okay, cool. Okay, just stay on and you're welcome to stay. Okay, thank you. Cool, good bet. And thanks for joining. So I guess we'll get started. So first on the hackathon that's coming up in roughly a couple of weeks. So, I mean, this basically happens on 28th and 29th, I mean, depending on your time zone. So people like to, Takuya will usually get an earlier start with his contributions. So you'll see the event page made updates with prizes and announcements on, why don't I just go there really quick. So I'm going to go on tutorial sessions. And so I'll probably make an update. I have an addition. I talked to Ramya actually from the quality team. And I think I'll be able to add her tutorial session right after the kickoff. So keep an eye out on this page for latest info. So that's happening on the 28th and 29th. You may have seen this. The social promo started, I believe, yesterday. Definitely seen it on both LinkedIn and Twitter. Oops, sorry. So, and I'm actually one of those weird people that are, that's not on Facebook. So if you're on Facebook, I mean, please let me know if you've seen the advert or campaign on hackathon on Facebook. And then I think like each week, there'll be like a new postings that are going, that are going to be posted leading up to the event. So I think, I mean, Ben, I think your feedback was on feedback last time. So we just wanted to make sure that was included this time around. So hopefully you can confirm that's there. I mean, one of the things that was sort of disappointing from the last hackathon was that the number of MRs significantly went down that came from the community members compared to Q1. I mean, I don't expect the number of MRs to always increase and be on a huge upward trend all the time, but definitely want to see this bit of a rebound for Q3. So I want to encourage everyone to participate in a couple of weeks, but let me know if you have any questions. And I think one of the comments that came from Miyakopo, and I'll click a link here so people can see it, was, I mean, obviously with all the prizes so far, it's been, I mean, solely based on the number of contributions that people made or a number of MRs that have been submitted or merged. And Miyakopo, you brought a good point about what about like a difficulty or the quality of the MR versus like a simple changes. And if there's a way to put some weight on like either level difficulty or how challenging it is. But I mean, Miyakopo, go ahead. I don't know if I was able to paraphrase what you're trying to say here, but... Yeah, yeah, I think you pretty much explained everything. My point was that, as you mentioned, we count SPR just by number, but most of the time, every PR has different weights. So doing that, I think, is not completely fair because encourage mostly doing small PR, especially during the ACATON, just to go up in the ranking. That's right. Yeah, I mean, interestingly, this was actually brought up by, I think, last quarter. I think it was on Reddit, because I mean, Reddit is one of the other channels that I make announcements on the event. And people asked about there's a potential for gaming, right? I mean, you know, instead of doing just one or two MRs, just break everything up and just, you know, increase the number of MRs so you can win the grand prize, for example. And the comment I made was that, I mean, I acknowledge that the possibility is there, but I have yet to see cases where people kind of abuse the rule, so to speak, just to increase the number of MRs that get merged just to win a prize. And I mean, the prize is, I mean, the grand prize for the last couple of quarters has been like $100 on shot.githlab.com. So it's not a huge sum of money to entice people to game the situation. But I did, you know, acknowledge that maybe there's something that we need to think about in terms of maybe a creativity or a difficulty of the MR that was, or difficulty of the contribution that was submitted during the event. I mean, one of the things that I was thinking about was, I mean, almost similar to the way we award MVPs, like maybe amongst just the court team members, like, you know, let's say in Q3, there are 70 MRs submitted and like a 50 of them are merged. Maybe the court team members can look at the 50 of the merged MRs and just pick one that you think was like interesting or that was like creative or it was challenging. And then we give out a separate award for that. I mean, that was something that I just thought about after I saw, I started to comment. Comment, yeah, Coppo, but I'd like to hear everybody's thoughts and see what they think. Yeah, I think it's more fair to use the weight. Yeah. Yeah, we just need to ensure that, at least during the, during the HECA zone, every MR gets a weight signed for the reviewers, I guess. Yeah. I mean, that might be like a difficult thing to do because I mean, let's say you have a weight between like one to 10. I mean, the concern I have is that, I mean, one person might think this is a seven and the other person said, well, it's not that challenging, I might give a five. So I don't know if that's, I mean, or I mean, maybe that's one way of doing it. Like you look at the MR and you sort of wait, put a weight on it, each of the court team members and then like average score and see which one wins. I mean, is that what you're thinking, Hones or? Yeah, I mean, you have to be careful of that. On the other hand, I'm not sure if we need to be so detailed about this. Yeah. So let's say you can say 10 to six is high difficulty and then someone and that's just like three steps or something like that. Yeah. Then it doesn't matter so much if it's a six or a seven just to get a general reading about it. Right. I mean, I think I, I mean, the one of the reasons why I suggested MVP as an example, it's not so rigid, right? I mean, you basically people make nominations or suggestions and then you sort of do a vote but that's pretty, I mean, you basically do a thumbs up and thumbs down vote on the nominees but it's, you know, but I mean, there's like a one person who sort of decides based on denominations, right? So, I mean, maybe that's something I mean, we can consider this time around, but let me know if you have other thoughts. Like Remy, did I cut you off or like, I wasn't sure if you're agreeing in general or if you have other thoughts. No, I was agreeing in general on the idea. Yeah. Yeah, I mean, maybe we can iterate this, continue to iterate this on the issue and continue the discussion. And I'm not sure if we'll have something in place before the event starts, but I don't, like even if we decide on like doing a separate award, even after the hackathon period is officially over, I think that's okay. Yeah. Yes, it has been. So I guess I have mixed feelings both ways. So I could see where doing weights could be valuable, but I guess if you don't do them real time, then it's hard for somebody to really compete, right? So that's what, at that point, it almost seems like giving out an MVP award might be better because if someone's trying to, you know, really watch how everyone's doing and compete, we've got to do the points real time. Yeah. I mean, even the points, like, I mean, I wasn't necessarily thinking like a real time, even with the scoring, like we could do it after, like, I mean, that 10-day period is over after everything's, like, you know, the deadline for the MRS to be merged. Like, you know, we can, on the Slack channel, we can just, you know, if we decide to use the score, we can, like, you know, award scores there and it doesn't necessarily have to be done real time, but... Right, I guess my point was, so there's currently a published scoring system, which there's a value in having easily available, so someone can see, am I online to get first place, second place, third place, or whatever, right? Right. So anyway, I guess I'm agreeing that perhaps keeping the current system and then having a separate MVP might be a good idea. Okay, yeah, let's definitely continue the discussion on the issue and, yeah, we'll try to... I mean, I like the idea, though, even if it's just a picking one that we want to highlight and as an example, and then, you know, we might just do a, you know, MVC for this time around and we'll try to improve it for Q4. Oh, right, well, thanks, Jacopo, for that suggestion, but that, yeah, that gave me a chance to think about that other post that I addressed on Reddit about three months ago. Yeah, I mean, good thing is we haven't, I haven't seen any evidence of gaming yet. I mean, just to win the $100 gift card, but doesn't mean that nobody's gonna try to do something, but I mean, if that happens, I'll probably try to like a deal with it like a separately, but... See, I think, Ray, more likely than gaming is probably just different people's MR habits. Like I tend to break out MRs as much as possible, but other people might not, so you might end up having someone with 20 typo fixes and someone who spent a ton of time on some really big MR. So I think it really comes down to, ideally, we're rewarding the person that contributes in the most valuable contribution. Yeah, exactly, that was my point indeed. Yeah. But I think it's a really good idea to do the MVP as a first approach because it's much easier and we don't need to set up wait for all the issues in advance and so on, so we could agree in starting with that and let's see how it goes. Cool. Right, thanks. Cool. So let's move on to the next topic. So the heroes program, not sure if people have seen either the landing page or announcement. Like a Twitter, like a campaign went out last week as well. So this is the main landing page. I don't know why they put my photo on the top of the page, but so you'll basically gives you a background in terms of like rewards, attributes and what we're looking for. And I mean, this is basically a way to provide more structure in terms of recognizing contributors. I mean, not just contributors like yourselves that are contributing a lot of the code or helping fix or improve our product, but basically, like things like organizing like meetups and events, speaking at industry conferences, but we wanted to basically provide better structure and recognizing people that are contributing to GitLab in a lot of different ways, like including like writing blog posts and doing write ups. So I mean, all of you folks that are on the call are I mean, more than qualified for this. I mean, we have different tiers for the heroes. And I want to encourage you to, I mean, take a look at this page if you haven't already. And I mean, feel free to fill in this application and send it in. And I think, I mean, at least one or two of you, I know submitted, which I appreciate. So I think John or Emily Chen will be getting back to you soon with the final decisions. But just wanted to make you aware of it. And at the bottom of the page, there's a link to it on the slide as well. I mean, John Coughlin did a webinar last week. It's about 30 minutes. If you wanna get more background on the heroes program, I encourage you to take a look at it at your leisure and let me or John know if you have any questions. I think a lot of the applications that have been coming in, I mean, there are several of us that have been sort of voting on whether we don't wanna accept the applicants or not. But I mean, I definitely wanna encourage all of you to, from the wider community, to apply and participate in the program. So I think if I'm not mistaken, I was talking to John, which there should be a place in the webpage. I think there'll be somewhere around here. There'll be basically photos of people that have been accepted as heroes. So you'll probably see them, see the pictures added here pretty soon. Any questions on the heroes? I mean, John would have been on the call, except that it's two in the morning, his time in New York. So I'm doing this discussion on his behalf. But I mean, if you have any questions, let me know, I'll be happy to do. I mean, or you can find John as well on the Slack channel. We have to be able to answer your questions and help you out. So that's it on the heroes. Any questions or? So I guess maybe Claire for you should. Go ahead then. Sorry. Yeah, I guess I was gonna say. So I guess originally I guess I just assumed that core team was considered automatic here, but it sounds like that's not the case. So we should go ahead. Yeah, I mean, go ahead and I mean, it should take you like two minutes to fill in the application. So yeah, I mean, that was, I think we talked about that like previously, like just grandfathering everybody in, but I think we decided to use it in the process. So just name email, get lab ID, that's basically all we need. And then Ben, I mean, or any other people that are applying, just ping me on Slack. I let me know, you send in the application that I could give John a heads up. So. Sure. So then I guess a second curiosity, do you know why they want work email? I mean, to an extent, but at the same time, I don't quite exactly see how this has to be tied to one's work. Okay. I mean, that's that I'm not sure. I just, I didn't even notice that, but let me take a note of that and ask John. Yeah, I can certainly ask, that's a good question. Was that it, Ben? Or I think Takuya also had a question. Takuya, did you have a question on the heroes program? Maybe he's on mute. Hopefully he'll see that and get back to us. All right. Okay. Can you hear me? Oh, sorry. Yeah. How many, how many heroes do you expect for the first, you know, heroes? I heard, that's, I think like somewhere around 50 is what I heard in the first quarter. So, I mean, it's a pretty large number. We're not just starting with like a five to 10 people. We're starting with a pretty large number. So, yeah. So, yeah, we're not like the limited artificially trying, I don't think we're trying to like artificially limit the number of people. So, I mean, we're trying to have a pretty big list of people to start off. So. Okay. Yeah, you bet. So. Okay. So, if there are no other questions, I'll move on to events and first two of these, I think I already gave people a heads up on either via email or on Slack channel. So, our first community conference called Get Lab Commit, we're starting with two of them in Q3. The first one's gonna be in Brooklyn, New York and September and the one following that is in October in London and via email, I think I sent you a registration code that you can use to register for free. So, you don't have to pay the registration fee. I mean, unfortunately, unlike the contributor or summit event, like we, unless you're speaking, the, we can't help you with the travel expenses, like the airfare and hotel, but at the very least, like we wanted to you to be able to attend the event without paying the registration fee. I know George, he's not on the call today, but I think he's speaking for the Brooklyn event. So, I saw him on the speaker list for the Brooklyn event. So, I guess I'll plan on seeing him there because I'll be meeting a panel session as well. And I think you're still thinking about whether you can come to the London event. But there's no deadline. So, I mean, you can register with that code, I mean, anytime prior to the event. So, let me know if you have any questions and let me know if you're planning on attending. I definitely would like to seek you out while you're there. And then I think we exchange email on this, like, I mean, both Brooklyn and London are not necessarily very close to California, but I think the plan is to have an event in the Bay Area in January timeframe. So, there'll be more details coming forth on that. So, that's sort of the plan for the Get Like Commit event that's happening in the next couple of quarters. And we're pretty excited. So, the speaker line up, if you go to the events page, I think I have a window here. I see more of these people or more of the profile photos populating. So, if you wanna like a look at schedule or who's speaking, go take a look at the events page. Cool. And, I mean, speaking of contribute or what used to be called the summit, the date has been announced. The location is still to be determined, but just wanted to ask everyone, all the 14 members to save the date. March 22nd to 27th. I believe this is like Monday through Friday. So, obviously, there aren't a lot of details available yet. I mean, there's a reading page that Kirsten started. So, we don't have the location. And then typically in the past, the first and last days of the events for like a travel days. So, I don't know if that's still the case for our upcoming event in March, but at least I wanted everybody to sort of book that week out. So, hopefully more of you can make it to the contributed event next year. So, that's that. And hopefully, I mean, I keep hearing the location will be announced soon, but I've been hearing that for a while, but hopefully we'll find out where it is soon enough. And the last one is more of an FYI. I've been talking to Yakopo about this. We've been working with the KDE community and we'll be participating at their annual Academy Conference in Milan in September. The link should take you to the events page. I had, I submitted a talk for more of a community related discussion that got accepted. And then I just, I'm trying to sign us up for a first of a feather session on GitLab to talk about our workflow and also about our community. And I mean, the KDE folks are evaluating GitLab right now as a new tool chain to use in their community. So that's why we're having, we have a presence there. And I mean, thankfully, like both for Yakopo and Alessio, who are relatively close by at the Milan. So they agreed to help with the birds of a feather session. And this is a free event. So anybody else is welcome to participate. So just want to give a heads up and thank you Yakopo for joining us there. It'll be actually good to actually see you in person for the first time. Yeah. So yeah, I added our session, the birds of a feather session for now on Monday. But I mean, Dave asks us, I mean, I told them like it's possible for us to like move that to Tuesday because I wanted to avoid conflict with some of the key birds of a feather session because I'm one of the presenter, Bushan from the community. I wanted him to come to our session as well. So I'm trying to coordinate with that with Bushan from KDE, but for now we're sort of slotted in for Monday and the September 9th. But I'll let you know Yakopo one is confirmed so you can figure out your travel plans. Okay. Thank you. Yeah. Well, thanks for coming. Cool. All right. So if there are no questions on events, I guess we can talk about the single code base. So Remy, like, tell us the latest. So yeah, the delivery team has been working quite intensively towards the single code base efforts. And finally they have a detailed plan with dates for when this will happen. So the goal, oh yeah, you can see in the issue that the process will be to rename both projects. So GitLab CE will become GitLab Force and GitLab EE will become just GitLab. And basically the development will only happen in the new GitLab, I mean, so the current GitLab EE projects, let's say, and there will be like an automatic sync from CE to the FOSS project that will remove all the proprietary stuff. And all the issues and merge requests will be in the EE project. And yeah, there will be communication. So this was communicated internally yesterday and in the issue they said that it will also communicate externally. So I was just, I just wanted to put that on everyone's radar and maybe we can discuss if we, maybe you can like communicate that in the GitHub channels too, like to broaden the scope of the communication here and also gather feedback maybe. So is, I'm just trying to make sure I'm reading this right. Thanks for bringing this up. Like the change in URL is actually happening in a couple of weeks, it looks like. Is that correct or oh wow. Yeah, and it could actually happen like the rick of the hackathon. Oh wow. So that's something to keep in mind. So the thing is that in GitLab, when you rename a project, the old URL redirects to the new one and even for the Git remotes. So that shouldn't be disruptive. And I think the only big disruptive change here will be that committee contributors are used to submit the major quest to GitLab CE. And they will need to actually submit it to GitLab EE which is, which will be called just GitLab. So that's quite a. Oh, okay. Yeah, that might need some like explanation for the hackathon. Yeah, so they just need to, okay, submit it to GitLab basically. Yeah. Okay, yeah, let me read through this and yeah, I'll definitely ping you or raise questions on this issue. Thanks for bringing that up. Wow, this is really fast. I was going to say, how finalized is this timeline? It's never final until it's done, I would say. But I think it's optimistic for sure. I think having this happen over the same week as the hackathon is setting us up for yet more problems than it's already going to cause. Yeah, exactly. Yeah, I just realized that just today that it was the same week. So yeah, maybe we should have a discussion with the delivery team to move it to the week after. Right. Because yeah, basically contributors will need to to clone the EE project and set up the GDK for that. Okay, yeah, then that's definitely a lot of hurdles. Yeah, I'll make a comment on here after we get off the phone, after we get off this call and bring that up. So yeah, thanks for bringing this to our attention. Yeah, this brings a lot of interesting things for me. Like, I mean, the developer dashboard we have, the way we script the data, it's all got to change. Like we got to do the redirects and all that. Yeah, there's a lot of projects that we need to be attentive. Yeah, cool. All right, yeah, wow, it is happening. It is coming quickly. I think the other thing that's going to cause a lot of pain is the moving of all the issues, which it looks like is in the plan up top, but certainly by room for things to go wrong. Yeah, and I mean, right. And then like the community members are like, I mean, they're going to continue to submit MRs through CE up until that point, like whenever it happens, right? But yeah, we need to give them a heads up that, yeah, that flow needs to change. Yeah, and the plan to actually like close on the merge requests, so in the week of August 19th. Okay. And before that, they will send a heads up, obviously, but yeah, that would be a bit disruptive. Cause everyone will have to recreate the merge request in CE. Okay, they're not just going to be migrated automatically, they have to recreate it. Yeah, I think, I don't know if they are thinking about automatically migrating the merge request from the... Oh, okay. Him, but doesn't look like it. Yeah, I misread it. I thought this said like CEMRs, but it says issues. So, yeah, I could definitely ask that question too. Like if there's an easy way to just migrate them, but... Yeah, it's up top on the plan. It says all CEMRs will be closed. Yeah, exactly. Okay. All right, cool. Thanks for bringing this up. Like I guess I'll have a few questions after the call. Yeah, I think that MRs are an area of concern. Like there's almost 1,000 open right now, but it's not necessarily easy to move them either since they're two different, technically two different projects today. All right, so any other questions or concerns? Okay, cool. Just wanted to make sure I'm caught up on those. Any other topics? Any other questions? Well, thanks for your time. We'll do this again in about a month. Have a good day. Thank you, have a good day. Bye. Cheers.