 All right, happy new year everyone. I'm not sure if I got a chance to talk to everybody after people came back from their breaks. Hope you had a good break and great start to a new year. Looks like, I think I may have added harness prematurely, but you've got Vitaly, Robert, George, Jacopo, Remy, and Ben. Yeah, I think we have a good number of people here, so we'll get started. And then let me, I think you guys can see my screen, but let me make that into a full screen presentation mode so you guys can all see this. Can you all hear me? Yeah, yeah. All right, cool, thanks. All right, so we've got a few things on the agenda. I mean, thanks for your flexibility. Getting back from the holidays, I just realized the originally scheduled time conflicted with the event last week, so I appreciate your flexibility. So I just wanted to get started on a few things to start off the year. And obviously we can add other topics towards the end under any other topics if you want to add anything. So have a link to working progress blog post. A couple of you folks already took a look at it, which I appreciate. So just wanted to do a couple of things on the blog post. I mean, one is, I mean, guys, I think I mentioned our participation in Pausam in a few weeks. But the other key thing that I wanted to do was to sort of celebrate what we've done from the wider community during 2019. So I added both of these charts on the slide. Is there a question or is it just a background noise? All right, I'll just keep going. So I added both of these charts, both of these charts on the slide to the blog post. I mean, the one on the left basically shows community contribution starting, I mean, going back to 11.l, you see a nice upward trending graph, which is always nice to see. And then another cool thing in 2019 was that we ended the year for the 12.6 release with the record number of MRs that were merged from the wider community. So that was a great way to end the year and start the holiday vacation. I mean, obviously, I want to thank everyone on the call and in the community for the contributions. And I was really excited to see this, I mean, continuous growth. I mean, obviously, we'll have ups and downs based on like seasonality and other things. But it's nice to see this nice upward trending graph in terms of MRs getting merged for each release. And one on the right, I just wanted to compare data for the past three years in terms of number of contributors and the merged MRs. I'm particularly happy with the contributors, especially if you compare the numbers between 2018 and 2019, we almost like doubled, and which is sort of reflective of the number of team members at Gillab. I think we more than doubled last year, but I mean, this is pretty close in terms of contributors that are participating in the community. So that was really, really cool to see. So hopefully we'll see this continuous growth in 2020. But yeah, I was pretty excited about this one. I tallied the numbers a couple of weeks ago. Not sure if people have any questions. Or commentary. But if not, I'll move to the next slide, which shows, I mean, top contributors, I mean, this is a final tally for 2019. And I mean, it's not a coincidence that top three people are from the court team in terms of the number of MRs merged. So I mean, all of you not just the MRs. I mean, MRs are great, obviously. It's always welcome. But you've always also had hand in helping other community members during hackathons or otherwise in terms of triaging MRs or encouraging community members to contribute. So I definitely appreciate that. And we have a different customer, like a custom merchandise that'll be going out shortly, hopefully soon. But just want to thank everybody on the call who helped out. So any comments or questions that I wasn't sure if there was, it looks like Takria joined, but I don't know if you have a question. I'm sorry, just I'm coming. What is your question? I wasn't sure. Like, I just noticed that there was a, I wasn't sure if it was a background noise. I was asking you if you had a question, if you had any question, because I heard something from your line. But if not, I'll move one second, please. Yeah. I mean, if you're, if you don't have any questions, I mean, that's, that's fine. We can move forward. But other people on the call, if you have any questions, feel free to speak up. Yeah, I, I, I would do, do the old, you know, much best as community contributions. Can you update statistics? Yeah, yeah, yeah, I saw the comment. Yeah, so I mean, obviously, see, if you look at this MR, Takria, you made a comment about, I should probably update some of the community statistics, statistics lies on, on the contribute page. We'll definitely, can definitely do that. And I need to update it dead in a couple of places. So. I don't mean, I mean, I mean, I mentioned about top contributors, not annual statistics of contributors or magicers. What do you think? For example, the source, it can, can you click the source? I'm sorry, Takria, can you repeat that, please? Can you click, can, can you have access to the sounds? Sorry, I forgot the name of the, the figures on the list and the source are different now. I'm sorry, I couldn't quite catch that, Takria. I'm sorry. Did you say like a source and, and these statistics are different or? On this page or? This page and figures on V, V takes, V take or the IO? Let me just see, let me go to the top contributors page. So are you referring to this link right here? Yes. It should be the same. I mean, I left some of the names off. So, I mean, basically I exported this chart for the submitters, but I removed people like myself because he's part of the GitLab team, team member now. But it should be pretty identical. I see. Yeah. This must be some much, much, so maybe the figure is increased. So some, some people are ranked up to the insurgist and also star. Yeah. I mean, I double checked the data as like a first week of January. And then if you look at the query, I mean, basically I set the timestamp for like a December 31st for like MRS to be merged. I mean, if you see a discrepancy, I mean, please let me know. I mean, if something's incorrect, be happy to correct them. But if you want, if you find something, if you can just follow up on the issue or for this month's call and just point me to where the error might be and happy to take a look at it. I see. Okay. Thank you. All right. Yep. Thank you. Okay. Any other questions from other folks? Okay. All right. I'll just move right along. So, not sure if you notice, we started this thing called the community office hours. And this is something that I started talking to the package team about a couple of months ago. And this came out of one of the iteration office hours that SID holds. And a lot of the product managers, including Tim, were talking about looking for ways to get feedback from the community members. And then that's when we started talking about holding office hours to invite wider community members. And separately, the same discussion was taking place in the runner's team. So we wanted to just set up a pretty informal call with the wider community members to talk about a variety of topics. It's not like a real formalized agenda. But we can talk about community contributions that people have submitted, that they wanted to talk about or get looked at, feedback on product directions or development priorities for each team. One of the things that the runner team, as you can see from the recordings is that they wanted to also show what's involved in doing MR reviews for community contributions. So we started off with the runner team this month. And we actually, if you go to the playlist, you'll see a couple of recordings. One was actually more of a planning discussion. It was a short, like a 30, 40-minute call on what the format should be and how we want to structure the conversations. And the following week, we had the first formal office hour. And we spent the entire hour just talking to the community members about one of his MRs. And then, you know, we, you know, I think Steve did a great job with trying to understand the motivation for the MR. And then trying to figure out, like, how do, you know, and then try, and also trying to explain, like, what are some of the steps that he goes through in reviewing the MR. And we spent the entire, like, an hour going through that one particular MR. I mean, Pierre Tardy, he's been pretty active in runner with his contributions over the past several months. So it was a good exercise. And it was a really nice way of getting, like, a real-time feedback between Steve and Pierre on that particular MR. So, you know, we're going to continue this with the runner team on a monthly cadence. So the next, the office hour will actually happen, I mean, during the hackathon, which I'll talk about in a minute. So, I mean, I mean, I think a number of you were, like, interested in looking at some of the backlog of runner project in the past. So, I mean, feel free to watch your recording and would love to get your feedback. And in the package theme that I mentioned with Tim Rizzi, like, we'll kick off the office hour also during the hackathon in a couple of weeks. We actually talked to one of the contributors who's, like, pretty interested in this, and he's been actually making contributions over the past year or so. And, yeah, he was, like, definitely interested in, you know, trying this out and participating in conversations. We would have started this earlier, but except that he was on vacation for, like, a couple of months, starting in December. So we wanted to hold off until he's back. So I believe he's back now, back home in Germany. But so we'll kick it off with the package theme next month. And I think this is a really interesting way of, you know, working community members real time, or I mean, people can obviously watch your recordings of, you know, discussing various topics that are of interest to the community members. So there's also a link to a handbook update that I made and working, waiting for feedback from the runner team. It's a pretty simple change on describing what the office hours are. But just wanted to give you all a heads up. I'm not sure people have any questions or comments, or I'm not sure people had a chance to take a look at the recording. I mean, we try to tweet these like office hour sessions over the past couple of weeks. And I mean, at least from the Twitter traffic, it looks like decent number of people like the idea of it. But any feedback that you folks may have, or if you want to participate in it going going forward, obviously we'll welcome your feedback and participation. Cool. I think that's a great idea. Yeah, yeah, I was I was really happy with the way the runner event went. I mean, I happened to be with Pierre at GitLab commit last week. So I knew he was going to definitely going to join like, but once he got back to France. So, yeah, we'll continue to iterate going forward. Cool. Cool. Okay. Moving right along. I mean, Hackathon is coming up shortly. It's on the 12th and 13th of February. I'm still trying to, I mean, I haven't updated the Hackathon pages yet, because I'm still trying to sort of nail down the tutorial topics and a couple of other things. But two office hours that I mentioned, I mean, it's pretty high likely, I mean, runners definitely going to happen, happen because we nailed on the schedule for it package. I'm awaiting confirmation from Tim. And a couple of others like a secure and defend David DeSanto is going to talk, is looking forward to meeting with the community. And I think I posted this on the core team channel or maybe it was the MR coaches channel about a week or so ago. We're working with, I'm working with Myra to do sort of a tips and tricks session on Git for contributors. So I was collecting topics like simple things like, you know, how do you do a rebase and, and I think a couple of people made some suggestions. So any like ideas or tips you have on that both Myra and I'll appreciate it. So looking forward to that. And so that will probably, hopefully I'll have an MR sort of announcing all of this thing in the next few days. And also if you have any suggestions on issues that we should highlight up highlight for the hackathon that are good for contributors. One of the things I did notice over the past couple of months is that a lot of people have been taking advantage of the good for first time contributors label of seeing more that getting, getting added to issues. So the interesting sort of run a query on how many issues there are, but I'll probably highlight those. And I've seen a lot of that in documentations and a lot of other projects. So which is, which is, which is a good thing. But if you have any others that that grabs your attention that might be worth highlighting please let me know. A final thing on the hackathon. So I typically do a kickoff session around this time on Tuesdays. And it happens to coincide with the hackathon. I think this has happened this happened like a couple of times in the past, where the kickoff session coincides with the court team call. And one of the things I was going to suggest or ask all of you is what do you think of the idea of like combining the kickoff call with what the court team meeting? I mean, obviously this call is open to anybody to join. So I mean, from, from that standpoint, I don't think there are any issues of, of, of, you know, wider community members joining in on, on the court team discussions. And also, like a tutorial kickoff usually goes about like a 20 minutes. And I mean, this doesn't, and this court team meeting call doesn't necessarily go to full like a schedule 45 minutes. So wanting to see, you know, I definitely see a value in like combining the call to raise visibility to both, but wanting to get your take on it and see if you have any concerns. I think that's a good idea. Yeah, sounds good to me. Yeah. All right, cool. Yeah, I mean, appreciate that. I mean, let me know if you have any concerns. I mean, I'll, you know, definitely try to keep the agenda so that it's not overwhelming for, for the court team discussions, but I think it's a worth an experiment. If it doesn't go well, we won't, we won't do it again, but we'll see how it goes. So let me write that down on the notes. All right. All right, well, thanks for, thanks for that. I mean, those are all the topics I had. I mean, let me pause here. I don't know if people have any questions or comments on the hackathon. So yeah, yeah, go ahead. Yeah. Is there an issue for this hackathon, like where we can suggest ideas like for the tips and tricks? Yeah, let me find the issue. Give me a second. I forgot to add it to the slides. That's a good point. There it is. Let me just paste it on to the slides. There we go. Awesome. Yep. All right. Any, I think, George, did you, were you going to say something like I don't know if it was you or somebody else that had a comment? Nothing comes in mind. All right, cool. Combining the, the core team meeting with the hackathon will be nice and experiment with this. Yep. Cool. Okay. Cool. Any other topics that people want to discuss? Ray, are there any, is there any progress with the community advisory council? Oh, that's a good question. I know, like Todd had made comments on it right before the holidays and David's not on the call. So let me follow up with them and get to the note so I can follow up with David. You know, completely forgot about that. Thanks for the reminder, George. Anything else? Any other topics? All right. Well, I appreciate, especially for people in Europe, dialing in early and we'll do this again at the hackathon or, oh, I forget, like, is anyone else coming to FOSAM besides, besides me on the call or, I guess, you know, I guess it's just, it'll just be me and David. You probably saw in the blog post we got some interesting things planned for the one in a couple of weeks. So definitely looking forward to that, but we'll provide a recap of it during the, during the next month's call. All right. Well, thanks for, thanks for joining and have a good rest of your day. Thanks for having us, David. Thank you.