 Test. This is on. Yeah. This is on. Hello. Good afternoon. My name is Nick. We're going to talk about the road to a thousand contributors a month and beyond. This might not mean much to you, but to me, this was what they told me. This is your job. All right. This is the goal for GitLab itself, so we'll explain it a little bit more in detail. But the bottom line, what I wanted to share here, and it's totally a conversation, I think, also with the audience, is what GitLab has learned from Drupal and what Drupal maybe can learn from GitLab. I'm not going to make any statements. I'm not going to say you have to do it differently. As in you, it's also myself. I've been a member of the Drupal community for over 15 years. Hi. So this is by no means any statement of saying, let's do everything differently. This is more knowledge sharing. So that's a bit to set expectations in a sense. So as I explained, my name is Nick. At GitLab, since April, I am the director of contributor success. And I don't know how to explain that to the hairdresser. For example, like I don't know how to explain what I do in a sense. But maybe to step back a little bit, I've been involved in open source ecosystems like Drupal for more than 15 years. Started with Drupal Conseget a long, long time ago in that sense. And I'm advocating open source in a sense that at GitLab, I'm working with the engineering team, working with the tooling at GitLab to see how can we improve GitLab, the product to cater to our contributors for GitLab, the product. Obviously, there are certain things that are in common with other open source ecosystems like the credit system of Drupal, or maybe attribution and get commit messages, or maybe just some other kind of automations of labeling and et cetera. Maybe you've heard Neil say as well, there's some things in GitLab that maybe needs to change for Drupal or for the migration. There is also certain communications that I'm doing with association to see how can we improve that communication. Next to that, I'm also a member of the board of the Drupal association, so I have some connections still with both worlds in that sense. So high level situation, open source is eating the world, and now we all cheer, yay! That's actually a good thing indeed. A step back in the past is that software is eating the world. You've maybe heard that phrase in the past, that software is eating the world, that any kind of industry is actually becoming a software industry. Maybe the best example that in today's world might be Tesla. In the past, car factories had some software division. Now it's a software division that has some car, software company that has a car division in a way. So I wanted to talk a bit about this and see how that impacts maybe our job, how that impacts these open source ecosystems and what kind of expectations we maybe can have for the future. So this is also the situation. If all these companies are using software, and then the next step is all these companies are using open source software, and I don't have to ask you are you using open source? We're at the Drupal con. But there's a lot of companies that are now starting to use a lot of open source tools to build their companies on. If you don't maintain, it's stating the obvious, if you don't maintain these open source packages or whatever, basically you put your company at a risk because if the open source package breaks and nobody cares, then your business process is broken. So organizations need open source to compete and those that leverage open source the best will win because they actually remove the risk for their business because they know those open source packages and they're actually able to maintain that or help maintain that. And maybe it sounds obvious to you. It's in my job at GoodLab to talk to these customers and to say like, yes, you're using GoodLab, great. But maybe if you contribute, you will actually gain a competitive advantage. If you contribute full-time, it's actually in your best interests and in GoodLab's best interests to do this together. Not a very easy conversation sometimes. This relates a bit to a story that you might all know. Who knows like Nokia and BlackBerry? You all know, I would assume. They're not really in today's world anymore. Now it's Apple, Samsung and others. Who knows? Cable, like you know these digging machines that they create to make like holes in the ground that have cables. Have you ever seen such a digging machine? What do digging machines have today? They have pneumatics. In the past, all of the digging machines had cables and there was only one company that started with pneumatic digging machines, but they were like way more expensive. But somehow all these cable digging machines said, you're crazy. This is too expensive. Nobody's gonna buy it. We're sticking to the cable digging machines. Ultimately, today's world, we don't see the cable digging machines because if the cable snapped, actually a human could die and it's safer to use the pneumatic ones. But this is an example from the book The Innovator's Dilemma. Today's example with software and open source is actually the same. Are we still actually going to see software that's closed in 10 years or is it open source? It's a dilemma and for companies to invest in open source, it's still a little bit of a gamble in a way like, okay, let's go full in knowing that the future might be different. You don't know what the future is gonna look like. If you'd like to read books, This Innovator's Dilemma is a great book to see how these big changes happen and who's on the forefront. And maybe another really good example on that and then I'll move on is, do you know where Agile came from? Toyota. In the end of the 90s, there were three massive car factories, but they were not Toyota and at 2009 or 2008 Toyota was the biggest one. They had one massive competitive difference and that's the way of working because for the rest they were just car factories. So who knows what the future will bring. This is interesting. This is something for the future today is bringing. I don't know where it's going to head. I created this with AI. This is the GitLab logo, the Tanuki with a Drupal Poti. So differences and parallels. Let's see. I'll do this a little quick. So GitLab itself started in 2014, had two co-founders, a Ukrainian person and a Dutch person. And as of the end of August, it has approximately 1950 team members. It's called team members because GitLab itself also includes themselves in the community and then people that contribute to GitLab are called the wider community. So we're being said, don't say employees, it's team members and we're all part of this here. As 30 million users and then the first commit was 2011 and I think it has 3,600 contributors as of the 30th of August. Drupal you all know, otherwise you wouldn't be here unless if anyone doesn't. It's a little weird if you don't. But more companies that are contributing to, okay, it has a broad adoption, a million sites and starting in 2001. So in a way to have a lot of parallels but there's also like a lot of differences in that sense. And before I go into the contribution journey and what is maybe different in that sense, I'd like to give you some info about GitLab as a company. GitLab is fully remote. So these close to 2,000 people don't have any HQ to go to. Everyone is at home or in a co-working space and it's a mission that everyone can contribute. So what does that mean? We are de-incentivized to send private messages and everything that we open up in GitLab.org is actually public by default. So that's to make sure that you can actually also help us or that we can help you, depends on how you look at it. And this is the hardest thing that I had to get used to in the beginning when I started at GitLab is that there's no email. Like this massive amount of people and we don't email each other. I'm not sure if they monitor it but you should not email it and actually I don't get a lot of emails from people. There's one other team member here from GitLab but I'm pretty sure he also doesn't get personal emails from team members. This is a very different way of working from what I was used to but everything happens in GitLab issues and in Slack. And then this is also what I mentioned in the bottom. Even on Slack we are de-incentivized to send private messages. There's like a KPI on how many private messages are being sent and that should reduce because otherwise people cannot help each other. So we need to be able to know what's everybody doing. Not to control but to be able to help them. How does an open source ecosystem work? Is there anyone here that ever tried to start a new open source project and to try to like get contributors and get that bootstrapped and get that running? Or is doing that? I think Root is doing that. Anyone else try that maybe in small scale or large scale? But it's good you try it and so you also know like it's not so easy and there's like a lot of different factors coming into like how does that work? I like to compare this a lot to to Root work in a way. Have you ever been in a scout or scouts or any of those volunteer-based systems when you were younger? I was in the scouting or something along the scouts from I was 11 till 22. I started as just playing around which is consuming in a way to then starting to create games for the kids. I was like actually adding something to the system and at certain point I was responsible for all the teenagers. I had no clue what I was doing and it was all volunteer but somehow I learned a lot of skills doing so. Those skills in the end benefited me when I was doing a job application and saying I have some skills. Okay I cannot compare open source to Root work in a way but there are some some parallels. It's all about people, people connections and trying to see how can we grow because even a scouting is to grow otherwise it's dying in that sense. So let's take a look at what it means to be in an open source ecosystem as an individual. How many of you are organization owners or company owners or maybe founders or any of those? One, two, so a couple of you. Hang on I have some slides for you as well in that sense but it's a mix between individuals and organizations obviously. The important thing as an individual and maybe it's a question to you as well like why are you in an open source ecosystem? Because everything is constantly changing and it's a constant flow of actually new knowledge. That's one thing you come for the software somehow it changes and you keep getting all that new information but it's constant and it's a great thing in that sense. You can also see the very elements that made open source so powerful, transparency, rapid iteration, collaborative innovation which is key for the individuals are actually also something that is a kind of a protest against how companies were working in the past. Maybe today as well as well that I don't know. Next to that there's also incentive and rewards. The credit system of Drupal is a very good example on how far you can go towards incentivizing and rewarding and creating a system around that. On GitHub you could for example say these badges that you can get on first PR or any of those things. There's a lot of those incentives and rewards. There's companies that also maybe give away swag when you create a merge request or have a merge request merged. We'll get back to that. Goodlap does some of that. And then I think the very important parts of a community once you get started with software is the people. So as an organization it's a very different explanation. Why would you as an organization one adopt open source is quite easy because it's there, it's good quality and it actually brings you to market more quickly. But then the big question is why would you contribute? Why would you give back to these open source packages as an organization? I didn't invent these words here so it helps and retain and attract top talent. There is some research that happened that if indeed like you contribute back to software or you contribute to a certain ecosystem employees are actually also proud of the organization that they're working for. Maybe it makes sense like when I'm explaining it but this is not so easy to ultimately get and then present to an organization owner or to a company owner and say like this is actually an advantage for you if you let your employees contribute to open source. The next one is actually also a very interesting one. This was a research that was done by Harvard by a professor called Frank Nagel. Feel free to Google it. I think I also have references on the slides later on. That researched if a company uses an open source package and you compare that to another company that uses that same open source package. So for example agency A and agency B using Drupal. Would there be a competitive advantage for the agency that actually contributes back to Drupal? So this professor researched this and the answer is yes. And it's actually a fairly simple explanation why. It's because if you learn by doing it you will learn a lot more than if you learn by just using or consuming. It sounds simple but indeed like if you just start doing it and go to the nitty gritty details of it and contribute back you will learn a lot more about the system that you're using on a daily basis. I think with Drupal it's the same. Agencies that contribute back to Drupal they're probably this is still a quote unquote I don't have the research at hand for the Drupal specific ecosystem but it will probably be more knowledgeable in actually using Drupal and getting a faster time to market for the same problem. So I found out a really interesting research in that sense. People that are interested in research please research Frank Nagel. He's like all in that kind of stuff. Lower total cost of ownership is kind of obvious. If you push things upstream you don't have to maintain it yourself completely. Glue code or any other code that you have and you can share the maintenance cost it's a lower total cost of ownership. I wanted to remind people here of a blog post that Dries wrote a couple of years ago about the privilege of free time. Drupal went through a pretty big change from having contributors over the weekend to contributors over the week. I think someone told me that it was also explained in the session before and it's maybe obvious but it's a lot better for an open source ecosystem if people that are contributing are being paid for because then at home they can actually sit in their sofa or take care of the kids or do whatever they need to do in the rest of their private life. Not everybody has free time. If we want to be inclusive for people that are limited in that free time we need to be able to create opportunities to make sure that they can contribute on paid time. So that also means that we need to convince agency owners company owners that contribution is key for that company to survive. So hopefully you can help me in these conversations maybe to your business owner to other people but it's good to understand. So how does an open source ecosystem win? This is again an AI image of a robot going to the finish line. This is completely side stuff. I wrote down the prompt of what I wrote in the stable diffusion API or like it's a stable diffusion model. You will not get the same image but you will have something similar because the model just creates that image for you. I found it mind-blowing. So how does it win? It actually goes from consumers to contributors. So how can we make sure that Drupal suddenly like doubles the amount of contributors. Would that be possible and in the same sense that's the goal I get lab has. Today there's 120-130 contributors a month and the goal is to go to a thousand. And that's a good question. How do we get there? How can we convert a lot of these consumers of GitLab into contributors? I think the same question could be valid for Drupal but it's also valid for Linux and other large ecosystems. Drupal was very early to I'm not sure if the word is right like invent but the whole credit system as an incentive to make sure that people are being recognized for but it's also incentive to maybe try to get more of those. But before we go there and we need to understand like who and what we're talking about. I thought when I started at GitLab easy importing I'm gonna help Neil importing the credit system of Drupal into GitLab. I was wrong. I was very wrong. I'm sorry everybody. This is not so easy. There's a lot of factors that we need to look at to understand like what is a credit. What do we understand as a credit and what kind of contributions are there. That same Frank Nagel from Harvard also did a research on what doesn't like what's an open source contribution. And he came up with these two words called content and editorial contributions. Content contributions means that if you come up with something out of thin air something new which could be new codes or a new documentation page or something that you had to think about and write down that's a content contribution reviewing codes or making typo fixes or anything that I wouldn't say it's less it's at the same level but where you don't create something out of thin air that's an editorial contribution. So developing reviewing merging reporting commenting reacting the the first one is a content contribution and the latter ones are editorial contributions. I'm not saying that one is more important than the other one so don't quote me on that they you need all of them to succeed but they have a difference and there needs to be a balance if everybody is reviewing merging reporting commenting reacting there's no innovation and then you get still so you need all of them to survive and then you have people that have many hats I've been an event organizer I've been a speaker been a developer like other stuff everyone has different kind of hats so how do you convert that into an ecosystem or into the product of GitLab that's not so easy. What does one get in return and then we'll get to the nitty-gritty stuff of Drupal and GitLab and maybe some other ecosystems. At GitLab there's a couple of rewards you get if you contribute. There's a hackathon every three months and if you get a merger quest merged during the period of the hackathon you get a t-shirt or a mug someone's here in the room with a mug I don't have a mug I'm very jealous yeah she fixed the type where she got a mug so that's kind of an incentive or reward to do contributions. If you do event organization like organization if you do a merger quest here and there and you start to do a lot of quote-unquote promotion for a good lab you could be applying for a good lab hero and that means that you then can go to a summit or an event for all the heroes this is not the same as a core contributor this is more your community evangelists if you will avoid some contributions and then every month because GitLab has a monthly release cadence there is a nomination for the most valuable person of the month which means in the release that's coming up there's a contribution coming from someone and we as a community deem that contribution really valuable so that's one part if we take a look at the rewards at Drupal which I think it's interesting because it's wildly different top contributors get mentioned by project lead or I think also in the keynotes from earlier today there were lists of names so you get recognition for actually contributing to these large-scale initiatives but sometimes and maybe tomorrow I don't know his keynote there is a list of people that helped creating Drupal 10 or like there's a list of people that he mentions organizations get higher in a marketplace ranking based on the amount of contributions that you do if you want to know more about that I think maybe Neil or the association can explain you a bit more but there's a specific ranking and it changes compared to the amount of contributions you do to Drupal and I'm both the individual the organization and the clients in Drupal can get attributed and recognized publicly you think obvious right in goodlap it's only today it's only the author of the code change of the merger quest that gets recognized so there's no such thing as saying I'm doing this for a customer and I'm coming from company X that that's not the case today if I try to do that analysis I need to guess based on maybe the profile information that you filled in or maybe the email address that you did it from but it's not so explicit you didn't give explicit permission to actually show that to the world maybe less measurable we talked a little bit about that is you can jump the career ladder faster and learn skills otherwise difficult in your daily routine I think I wanted to show you a really nice picture of myself why she it was my wife that took this picture I went to Malaysia on a holiday private holiday but I couldn't resist the urge to meet the Drupal community in Malaysia like somehow I needed to do that I wanted to do that and I was explaining about search API and then stuff so you get some fulfilling as well as a contributor in open source I needed to mask the faces because legal told me so so how are other open source projects attributing contributions I think that's an interesting one have you ever looked at how WordPress attributes contributions or type of tree Linux foundation that's interesting right there for me that was a new one like I knew the Drupal system but if I wanted to get something in good lab it needed to cater for more ecosystems other than Drupal so let's take a look has anyone ever contributed to WordPress so you have a prop and you have a prop right the word in the WordPress community is called prop and if people are working together and you get something in or there's something resolved the people that are collaborating get a prop a prop is something that is added to get commit message and then they get commit message you can see it here in the bottom might be a little unclear it has a username and the username links to the same username of profiles at WordPress org and in your profile of WordPress there is a link to an organization and that's how they create these statistics that you can see on the right so then you can see that there's 134 companies contributing to WordPress 6 and etc so I found it interesting that they do that on a get commit level obviously they recognize event organizations and all of that but that's not within the get commit sphere there are proposals at WordPress to change the prop system to more get commit message default standards and that's actually similar to what Linux does what Linux does and maybe you need to take a look here at the bottom is that in the get commits I get commit message themselves they add yeah suggested by suggested by signed off by altered by reviewed by acknowledged by and then has like a bunch of email addresses so that allows you to create a distinction between content contributions and editorial contributions because you know who created it and who helped there's no difference in importance but at least like there's some information on the balance of what's going on while attributing and recognizing the people that collaborated so I found this really interesting and how do they link it to organizations they look at the email address if and then you could question like hmm but I'm a volunteer at home and during the day I'm working for a company why it's quite easy you switch email addresses in the the get commit that you do because based on that email address it actually links to the organization I found that really interesting if we take a look at Drupal and I think you all know this there's a whole like credit system and then in a secondary basis there's some get commit that does a summary of those but there is no such thing as like altered by or reviewed by or that so that could also be interesting that said Drupal obviously goes in a higher level and recognizes contributions other than get commits themselves as well so then I got in like a little bit of a conflict with myself like okay how should we go forward do we go with to get flow and going just to commit messages or do we have an overarching system I'm still not sure I'm happy to get some more feedback I think from the audience there but today this is my dashboard so today we are recognizing the author of a Merch requests and we're looking at how many authors of Merch requests do we have every month and you can see there in August it's the green bar was like 126 and we look at how many Merch requests are created how many are merged so there's like a big start and ending point and there's like a lot of opinions in between so what draws contributors to to GitLab and then maybe we can go in Q&A a little bit later to see if there's like thoughts and suggestions and I have like a little roadmap as well of like where we're working on at GitLab so what draws contributors to GitLab there's events so these hackathons there's meetups also virtual meetups there's community office hours GitLab commits and here's summits what you don't see here and what I think is a concept that you all know is sprints like I was a bit surprised that there were no such thing as sprints in the GitLab community physical or remote like I'm not sure if I've ever done a virtual or remote sprint but probably is possible so I'm curious if we could maybe start that or have any of that starting but this is what is happening today to get contributors now in terms of metrics and learning and this might also be interesting as so the hackathon which is a very different word than a sprint as a sprint is working on maybe long term things hackathon is like get as many people as possible for a small anatomic changes as possible and if you have something merchant hackathon you get the price you can see at the right in August there's like a massive spike that was the hackathon you can actually also see that here in May there was also a hackathon and then in February there was also a hackathon so every time there's a hackathon it's a peak and then it actually decreases because people are waiting for the next hackathon because they don't get prices in the two months that's our following that's a problem like you actually want to keep them like please continue and like don't wait for the price window to open up so we're gonna see if we can maybe change the expectations there in that sense what we also saw and we did some analysis on the data is that as soon as people have 10 contributions they're more likely to stay that sounds obvious but I was actually expecting like four or five like if they if you do four or five merchant quests maybe you will stay but it's actually you need 10 and then you're more likely to stay it's really easy under 10 to actually drop and ever come back I'm curious if we could figure out that data for Drupal as well but that's that's rather difficult I think future initiatives and this is also I think interesting for for Drupal although it's not so easy to accomplish if we have people or organizations that have 20 merchant quests or more in the last three months merchant quest merged they get entitled to a specific batch they're called a leading organization or a leading contributor in a way and if they have that status we promise or we have an objective and because it's not an agreement it's an objective and SLO that we get back to them within four working days if they say I'm ready please review this the review could be you didn't add description so anything that just says okay what's the next step that's what we are trying to do within those four working days I know and in the Drupal world by my own experience sometimes issues can linger around for a long time for years it's a good and a bad thing like everyone is equal that's very good but it would be nice that if we somehow have people that says okay let's try to shorten that time to maybe increase the innovation or increase the change pace this is an experiment that we're doing it could be that in two months I do the same presentation and this no longer exists so you can find this back in the handbook on like how you qualify and that an organization like even if you have an organization I have five people do a merchant quest they could still qualify if those five people do for merchant quest each so it's an organization that qualifies as a whole I foster communication there's like a lot of communication channels at GitLab for contributors I would love to get to that same centralization that Drupal has but again like that's also not super easy to do and maybe as the last thing the contribution credits in system in GitLab so this is a bit of the timeline I think Neil can confirm that's more or less the timeline and you can maybe also understand now that looking at these other ecosystems just porting the Drupal credit system into GitLab was not so easy or it couldn't be just like plug-and-play and create like a mini form and just see okay let's let's go for that there was not enough consensus to cater to these other open source ecosystems as well so I became responsible for the issue in the end of June which is good so then it actually says you are the directly responsible individual that doesn't mean you have to execute it but you can make decisions but you have to listen to everybody and then maybe make another decision later on but at least there is someone responsible we are now working on the developer certificate of origin which means that you get that mini message in the git commit message that says signed off by so it's a very small step to just a git commit message thing itself I would love to get reviewed by I would love to get collaborated with or something like like that line just within the git space maybe later in other iteration we could go more holistic and look at the issues but again like I don't know how fast we can get there there's a couple of of links here but these are user stories that are open in the issue queue of what needs to happen to get this reviewed by and get this signed off by with multiple email addresses like to get in production it's like a very small scope just having reviewed by assigned by all of those things with multiple email addresses and this is like that work that needs to happen so you can see like to port the credit system of Drupal into GitLab we're still like still a little bit behind or it's like a long way to go in so to get in touch with GitLab maybe you can help me if you make a merge request and it gets merged you get gifts I have socks as well if someone wants to port the system right now we have community resources it's how to contribute there's a handbook page and you can join the community at Gitter and then there's also an unofficial discord space where you can yeah talk and hang out there's a community relations team and then there is my team called contributor success so in charge of that engineering process and to see like how can we cultivate and grow to that thousands and then there's also similar to Drupal a core team as a core contributors that are not necessarily working at GitLab and there's some that are working at GitLab and coaches this is I think also really interesting for Drupal there's 35 merge request coaches and their job is to help you find the right person you make a merge request and their job is to see who do you need to get in touch with to make this move forward are the labels correct I think this is similar to mentors in the Drupal space although it might be different I don't know enough about the mentor so I'd love to understand a bit more but yeah this is what they have and with that I'd love to thank you for your attention hopefully you found it interesting and maybe there's some questions I don't have the app so if someone can read the questions if someone puts questions in the app I'd be happy or I'll be happy to take live questions as well seems to work do you know that Drupal is changing how the credit system works because it's mirage into GitLab partially and there are some things that are being lost like for example the some parts of the credit system and I would like to know if you have an opinion on this on this change which change I'm sorry I mean the Drupal Drupal org is using GitLab as the backend and they are moving a lot of things to GitLab part of the change involves changing the current credit system and for example the commits have been removed from the profile in Drupal org and they are based on they are going to base that information on GitLab so I would like to know if you know the changes and what's your opinion on that I'm not super involved Neil is more involved I'm happy to give him a microphone but in his keynote initiative he actually says like they're porting the system to another system in Drupal from what I understand but there is no functional or like scope change but there's also not being embedded in GitLab but do you like to like add on to that more or is that accurate what I said right yeah yeah so for the next iteration of Drupal org even with the GitLab migration is the functionality is gonna stay okay right yeah I'm kind of curious on the on the metrics that a that of your open source contributors so for me what made me start in open source is scratch my own each I wanted to build a website so I installed Drupal Drupal had multiple problems so I started fixing them and then I gave them back etc etc now as a GitLab user I don't have that first of all it's a pretty good product already I do have some itches that I need to scratch here and there but getting to 10 I mean that's that's that's like what are those people doing with Drupal with the GitLab I simply can't imagine the product is finished like just get out of here it's fine I get your question I get it asked like a couple of times but if you would ask the CEO he says we're only 15% there for example like there's a whole Kubernetes agent now and there is like a lot of these other toolings the clusters and whatnot that are constantly changing and updating features making management more easy so all of that also needs to happen like the whole maintenance part also still needs to happen and then there's a bunch of new functionality that is open for discussion like even this credit system that needs to be added in for example yep thanks one person said I like it these issues and I have merge requests and now a GitLab also added a support ticketing system bare bones but it's there but I don't know which customer it is and I also don't know what the rate is for that customer if I answer the support ticket so this is a core contributor it says well let's add a CRM system bare bones but let's add who is a customer and what organization is this person working for and that's a contribution that he did in multiple iterations but I'm very grateful of that because now in the database there is actually the thing called organization and that might be useful for the credit system at some point maybe not we still need to investigate but that's one one alley but there's many people scratching itches on the GitLab I think two thousand five hundred merge requests open right now and like fifty thousand issues or something I don't know I've question about the why are they only the authors of the code credited but first of all there can be several authors of the code obviously but I've I've seen looking at the statistics for the GitLab credits that model maintainer who merges lots of patches from other contributors in doesn't get any credits for that so it's like making that part really invisible even so we know that reviewing merge requests or patches or other issues take a hell of a long time what do you mean with module maintainers within the scope of GitLab when you look on the when you used to look on the project page on a Drupal.org for example the activity included accepting merge requests or accepting patches I mean you could look on GitLab I understand that the action of merging something is not credited what did I get that wrong I think there's maybe a confusion like what I'm explaining is for GitLab the project on GitLab.com so I'm not talking about any of the credit system of the the GitLab implementation of Drupal the GitLab implementation of Drupal normally should take whatever existed in terms of credits and be feature parity in that sense if there's any lacking thing there I would suggest that you talk to maybe Neil or other people to see like what's going on there maybe to understand like why does GitLab the project on GitLab.com only credits authors is because that was the easiest thing to start with I'd love to get more complex but one of the values of GitLab is iteration and that's how we started and then it's a good question like what's next what's the smallest next possible change we can make does that answer your question thanks I think time's up I see like a moon rising there in the end thank you so much for attending I'd love to like answer more questions later on if you'd like maybe one other thing there is a Belgian night tonight at 9 p.m. and it's on the Drupalcon website at social events and yes and swag there's t-shirts there those that actually made some questions please come to the front and you can take a t-shirt or if you're really quick socks