 All right, we'll just get started. I think David will get here in a few minutes. Let's just get started and hopefully you can see the screen I'm sharing. Here, let me paste it on the chat window too so I can all help you with the note taking here. Hi, everyone. Hey, Vitaly, how are you? Great, how are you? Good, good. OK, so just go ahead and get started. So we have a relatively short agenda for the last call of the year. It's amazing how quickly time sort of flew for 2019. So three topics. I mean, first is regarding the membership changes in the core team. I don't think Vinny's here on the call as of yet, but he announces departure from GitLab a couple of weeks ago on the Slack channel. Hey, David, how are you? Good, thanks. So we'll talk about that really quickly. And then a quick follow up on we had some good discussion on the Community Advisory Council. I think there are some updates that were made on the MR. David will give us a quick recap of what's happened since the call and what the next steps are. And I'll also talk about some of the community events in Q1 2020 leading up to Contribute. So those are the main topics. If there is anything else, please let me know. If you could add a topic towards the end. But so we can do that at the end. So let me quickly jump to the next slide. Yeah, unfortunately, Vinny, he's been on the core team since 2016. And I believe he joined GitLab as a team member in 2017. He's been here for a long time. And he's pursuing a different opportunity in a few weeks. And I had a quick discussion with him last week if he would have an opportunity to continue contributing to GitLab. And unfortunately, at least initially, that's not going to be the case. So he will not be able to, at least for the first few months, he's not going to be able to contribute to GitLab. So he will be standing down from the core team. So yeah, I don't think he's on yet. But I just wanted to, I'm sure, everybody has the same sentiments based on what I've seen on Slack messages. He's been an awesome contributor and a core team member. Definitely he'll definitely be missed. But hopefully he'll start re-engaging with the community in several months. And we'll hope to see him again soon. So what that means is that, I mean, so what we started to do almost two years ago now is to have, or about a year ago, is to have up to two GitLab team members in the core team. So we'll have one space that will be vacated. So we'll look into adding a new team member to the core team in the future. I mean, there's not necessarily any urgency in doing this. But this is something we'll look into doing in the next couple of months. So if you have any suggestions or ideas from the GitLab team members, I mean, you feel free to let me know. I mean, one of the things that I'd like to consider is to add somebody from underrepresented groups into the core team. I mean, one of the comments that I've heard in the past is that all the core team members, I mean, happen to be male. I mean, that wasn't designed that way, but that's how it turned out. So that's, I mean, in terms of gender and other areas that we want to have a well-represented, sort of well-rounded core team. So that's something that I definitely want to consider. If you have any, like, suggestions on people or thoughts on this, I mean, feel free to, I mean, bring them up in a Slack channel or reach out to me. But that's something that we'll look to do in the next couple of months. But let me just pause there and see if people have any comments or feedback that you want to discuss during the call. So unfortunately, neither Vinny or Remy were able to make the call today. But yeah, I think, yeah, David, you and I talked about this quickly like last week, but I'm not sure if you have anything else to add here. Yeah. I mean, I'd say if everyone has seen any contributor doing good work, that might be a good candidate. It'd be good to send a suggestion. I think we're still using service tests. So that might be a good way. Another thing might be as well to announce it somewhere like the company call within GitLab as well. And yeah, I'm explaining this proposal essentially to make sure that the new candidate, one of the, so one of the deciding factors as well of contributions would be to make sure that we create a more inclusive and diverse community as well. Right. Yeah, that's a good idea. I mean, there's certainly a lot of people within the GitLab team. I mean, people, both that have been around for a while and even somewhat recent that have been really good about working with community members. So I think we should have a lot of good candidates. But yeah, I mean, could probably open this up even within the company on the side channel might be a good idea. So any other thoughts? Oh, go ahead. Sorry. Maybe I'm right. Sorry. Maybe one place to look for is a mad request coaches and if they have any suggestions. Yeah. Since they collaborate more often with the community. Right. Yeah. OK. Any other suggestions or thoughts? We'll just move on to the next topic and the next slide and I'll turn things over to you, David. I made some slight tweaks from the slides from three weeks ago, but hopefully that reflects what's what's happened in the past few weeks. But I'll let you lead a discussion. That's right. Yeah, thanks for the updates. Essentially, it's a continuation of the discussion on the last call. There have been some changes, but I haven't been able to spend as much time as I wanted it on it. I think the bulk of the proposal is essentially done. We had discussion on the size and we tightened the definition of how often the team would meet. I think the only thing that's missing in there, unless there are other comments from the participants, is creating the process for nominating issues and MRs from the wider community. And this is something that I was thinking to keep simple, to perhaps create a group in the same way that we have the core team group and then add some documentation around the process and let people be the community advisory council to nominate something that's for discussion in public. So I think what I'll do is I'll add that process and I'll remove the working progress on the MRs request and then look for comments and further approval. And then in parallel, I'll start reaching out for initial members and start asking folks who might be interested in joining the initial incarnation of the council. But yeah, I was going to say, if you've got any comments, then feel free to add them to the MR or feel free to reach out to me directly as usual. Any thoughts, comments? We'll move to the next topic. So I wanted to talk about some of the community-related events that we're planning for, particularly in Q1. So one is not a big conference per se, but this is an initiative that we wanted to try out as one of my OKRs. It's what we call hackathon in a box. Obviously, the virtual hackathon that we've been having every quarter has been pretty successful. And wanted to replicate that so that people are able to create an event where it's create a fun environment for people to start contributing, especially for new contributors, when there are face-to-face events or need-ups. And I mean, Takria is on the call. Like he's been very good about this, and he's already done this in the past in Japan. But I've been talking to some of the heroes and a couple of meet-up organizers where they have a regular cadence for meet-ups and then creates an environment where people can get together and help each other and get new contributors involved in contributing to GitLab. So there's a link to a relevant epic there. So you'll see some of the things. There are mainly two things that I started working on in Q4. Like one is creating some introductory content. So you'll see links in the epic. One is just an overview presentation on here's how you contribute to various areas of GitLab, like including documentation, UX design, translation, and in addition to code. So it's a short deck. It's a variation of a slide deck that I use as a tutorial a couple of hackathons ago. So that's been refreshed. And then the other thing that I started working on with the GDK team is to create a series of videos for GDK. We had a GDK introduction video that was done by David Anton, like probably at the first hackathon, that was one of the most widely viewed videos on the hackathon channel. They had over 1,000 views when I checked about a month ago, which was good. But the GDK has evolved pretty significantly over the past few quarters. So there should be two videos there. If you go to that epic, let me just go there right now so you can see it. So there's a GDK playlist under the unfiltered channel. So we just recorded this several hours ago with Tiger Watson. He's one of the back end engineers, but also maintainer for GDK. So quick, if I made a video on how you set up a GDK, and Tong had a somewhat more advanced topic on using GDK for auto dev ops, that's probably more relevant for GitLab team members. But I think community members might find this interesting. But we want to build this library of videos. So there are probably a couple of other topics that I'm going to tap a few GitLab engineers on. Just do a quick video, like a five to 10 minute video session, so it's easy to consume. So those are sort of the two things content-wise that we started working on. And the other thing that we also want to offer, and Takuya can chime in here, because he's got a meetup scheduled on the 16th, like one day next week. So he's going to hopefully pilot some of this content. And then I also sent him some GitLab merchandise that he can give out. Like, for example, if someone submits an MR, like you sort of get a prize on the spot. So fun prizes that you can use at like a face-to-face meetups where people contribute and they get rewarded immediately. So I want to try that out at a couple of different venues over the next few months and put together sort of a hackathon in a box material that various event organizers can use. So I mean, Takuya's got an event next week, and then he's got another one in January. But if there are other like a meetups that you're typically involved in, like locally and in your countries, I mean, please let me know, I definitely would like to see if we can put something together for your event. We also try to do this for, right, the docs in Australia, but it was like a too short of a notice. Like a lot of the sponsorship and all that sort of came together so we couldn't like organize something like on-site in Sydney almost about a month ago. But if there are other events that we should probably like experiment this at, I mean, please let me know. So let me just leave it at that. And I mean, David, I don't know if you have anything to add here or anything I may have missed. Well, I mean, one thing is good, I wanted to say, good work with the last video, which is a case setup. I think it's great to have something like that that's under 10 minutes. As I say, I think that's much easier than for people to consume the longer ones. But still, we have the longer ones if people want to delve more into detail. I have a question on the playlist itself. Is there any reason why the initial GDK tutorial from TUN was not added in there? Is it because it's still there? Yeah, we can certainly add it in here. I mean, there's no reason why it can't be in there. I mean, I can certainly like add it. I assume there's no issue of doing this because this GDK channel existed in the unfiltered account, whereas the other recording was under the regular GitLab account. But I assume that's not an issue. I haven't tried it yet. But that's a good point. Let me see if I can at least add a link there and see if it works. One thing we can do is try to download a video and move it to the unfiltered channel where it comes to worse. OK, cool. Any other thoughts or suggestions? Do you expect the kind of contribution in Hakka in the books? I'm sorry, Takuya, can you repeat that, please? Do you expect some kind of contributors in this Hakka zone? You mean like contributors to attend these events? Or like? Yeah, and we can see many kinds of contributions, like having a talk or organizing meetups. But I think Hakka zone in the books can help us to have a code contribution. Right. Yeah. Yeah, I mean, so I think having talked to a few of the event, like a meetup organizer, because it'll depend on sort of the type of the meetup that you're running. So this sort of the hackathon activity that's targeted more towards code contributors should be, I mean, it'll be like one of the agenda topics in a longer meetup, right? I mean, some of the meetups from what I heard from some of the organizers, they sometimes run like a three to four hours. And it's possible that during the three to four hours, you'll carve out some time, like an hour, to just have a workshop working with the contributors. And then you can have other talks and discussions. For example, on DevOps or other aspects of GitLab. Or I mean, it's possible that somebody might want to just run an event that's just focused just on code contributors. So I think both of those options work. I mean, whatever works for you locally, I mean, at your event in Japan, if you want to just have a single topic focused on working with recruiting or training you contributors, I mean, I think that's fine. But I think it's also OK if you have a decent amount of time allocated for the meetup to have this as just one of the topics that you'll have at the meetup. But I think it's up to the organizers. But is that answer your question, Takuya, or like? OK, I think. OK, cool, thanks. Ray, perhaps another comment. We haven't discussed this, but I'm seeing this on the same page. It might be worth perhaps thinking whether there's something that we might want to do at some of these events, either for thermo or scale or both. Having we've talked about having contributor workshops, so I think start to contribute, but perhaps with also a triad running a hackathon there with some prizes like that we could do live. I mean, FOSM might be a little difficult because it's a little bit more chaotic. And then we're not going to have a dedicated GitLab session. But I mean, for scale, I think that's definitely more under our control. Like if we will talk about this in a minute, if we're going to have a track that we're going to organize on our own, it's completely appropriate to have a carve out some time to run a workshop for contributors. Yeah, it's definitely an option for something like scale or for some of the other events like a GitLab might be sponsoring down the road. I mean, I didn't list it here because the events, I believe in Q2 in May, I believe GitLab is going to have a bigger presence of a right to docs in the US. So I mean, I've been talking to the technical writing team about running a workshop on focus on docs contributors. So opportunistically, I think we can definitely do something not just at meetups, but events like scale and write the docs. Right, so we'll move on to the other events that are on the slide. So FOSAM that's coming up, that's usually the first weekend of February. So I believe this time is like a February 1 and 2. And there's a relevant issue that you can take a look at where a number of discussions have already been happening around FOSAM. And then if you wanna join a Slack channel, like in Slack, there's a pound FOSAM channel, if you wanna join discussions there, it'll probably get more active like after the holidays as we get closer to the event. So we'll again have a stand during the entire conference. When I actually submitted this CFP, I actually requested Saturday only, but the feedback I got from the organizers that GitLab is a big open source project, so we should be there for the entire conference. So we'll have a stand for both Saturday and Sunday. And there are also a lot of dev rooms that happened at FOSAM and a number of GitLab team members and myself included have submitted talks for various dev rooms. I mean, John Coughlin and I submitted proposals for the community dev room, but I know there have been a CFP submitted for like a Golang dev room. And I believe Ben Kochi is also one of the organizers for one of the dev rooms. I believe it's like monitoring. I forget the exact term for it. So you probably see a lot of GitLab team members there in general. So if you are planning to like to come to the event in February, just, I mean, please let me know. We'll probably have a decent presence there anyways. And I believe that that room schedules will start to get announced like starting like this week or next week. So you'll see which talks have been accepted. So that's just a quick info on FOSAM. And yeah, and for, I think most people here probably know FOSAM always happens at the same like a university campus in Brussels. So that won't change there. The other event that might be new to a lot of the people, it's called Scale. Southern California Linux Expo, I think that's what Scale stands for. And David has more experience with this event than I do. I mean, this year was the first time I attended at least part of the Scale event. And it's very similar in type of people that attend like FOSAM. A lot of like open source enthusiasts, people that are passionate about open source like in general attend that event as well. And the Scale is already, I mean, as you can imagine from the name, it's always held in like the Los Angeles area in the March timeframe. So there's also a relevant issue there and as you can see in the second bullet, David and I have been talking to the organizers about sponsoring a half day track focus on GitLab, both on the community and our product side of things. And I think this is where we can sort of have a session focus on like attracting new contributors sort of run a workshop. I don't believe Ben's on the call yet, but we do have like a few community members that are in the Los Angeles area. If they can sort of participate and help out in sort of running that workshop, I think it'll be pretty effective. So, and also the Scale event this year, it's sort of in the same week the Git Merge event also happens in the Los Angeles area. So it's sort of dovetails like nice, like a Git Merge event dovetails nicely into the scale. And we, I mean, last year what happened with Git Merge is that it happened right before FOSM. So it's interesting like this year, they decided to do it in LA right before Scale. So one event sort of leads to another. So that's sort of, I mean, the two events that I just wanted to give you a heads up on. I mean, if you're like, if you're planning or interested in participating and or attending any of these events, I mean, please let me know. And I feel like I may have forgotten something either about on FOSM or Scale. Like, I mean, David, did I miss anything on either one of these or? No, I'm just trying to think of anything else. But yeah, I mean, let's say if anyone has good feedback on either of them things that we could do or things that we could do differently, then feel free to comment on those issues. Right. Yeah, and then I think David, you and I are both planning on attending both FOSM and Scale. So just an FYI. Cool. I think that's the end of the slides. Just want to see if people have any other topics that people want to discuss or anything I may have missed. Everybody's really quiet today. Ray? Yeah. Regarding the community events, I think it's worth bringing this up a few months earlier to the court meeting so that we can plan any calls, proposals we can submit or something because the CFPs are closed for all of these events at the moment. Yeah, that's a good point. Yeah, yeah, I mean, I think for, especially for both FOSM and Scale, I probably should have given people the heads up about, like especially for the CFP a few months ago. That's a good point. I mean, on Scale, since we can sort of schedule our own track, I mean, if there's something, George, that you're interested in maybe talking about, I mean, let me know. Then we can definitely see what we can do there because that's sort of, we have the time in the room and we can, I mean, within reason, we can sort of schedule it the way we want it that half day to go. So let me know. But yeah, next time, it's probably worth talking about both of these events, like right after people come back from the summer holidays because I think that's when typically FOSM starts communicating about the debt rooms and proposals. That's a good point. Yeah, and I think I talked to David about this on, especially on Scale, if this half day track goes well, I mean, who knows, like we might decide to expand this to a full day next year. We weren't quite sure if it will have a full day worth of content, like just on, because since this is sort of the first time we're trying this, I mean, there are other communities like OpenSUSE and Ubuntu, I mean, they've been, had presence at Scale for a long time, so they typically have like a full day event. But we'll see how the first one goes this time around and then if it's successful, there's no reason why we can't expand it the next year and extend it to a full day next year. Any other topics or questions? All right, I guess that's a wrap. I mean, this is, like I said, it's the last call of the year, so I assume a lot of folks will be taking some time off for the holidays, so do enjoy the holidays and look forward to seeing you and talking to you all in the new year. Cool. All right, have a good day. I'll see you guys later. Cheers.