 So, welcome to the live stream everyone, thanks for joining. Bloomberg broke the news that GitHub is acquired by Microsoft and both people inside the company and external to GitHub Inc had questions so we go on a live stream and try to answer them. If you have questions, please ask them in the YouTube chat, apparently that is going about pizza and me baking pizza, I have to disappoint everyone, it will probably not be pizza tonight. I'm not sure what's up. I was having my anniversary weekend, wedding anniversary weekend in Tahoe came back a bit early for all of this happening but I burned my foot because I was standing on the pedal board too long. Anyway, that is about as relevant as the pizza and I'm not seeing any good questions in the YouTube chat right now so I'm opening it up to anybody here who has a question about what's happening. Hey, you said one question I saw in the chat was about how many repos have been transferred from GitHub so far, maybe you could talk about what we know about that. Yeah, there's some monitoring. I think our public monitoring broke because it's number one on hack and news right now. I think we also broke hack and news because that was down for a minute but maybe someone here can look that up. There's a difference between number of users, number of projects, number of repositories. If someone has an idea that would be great. The only number I know is that moving to GitLab, the Twitter account has over 1,000 tweets. Sneaky crowd. Sorry, I just got those numbers. Looks like there's been about, I'm just doing the math adding up the data points in my head, about 3,000 every six hours for the past 24. Cool, thanks for that. Sneaky crowd asks, is GitLab having any scalability concerns right now other than our public monitoring being down? I don't think so yet. We did have to scale up a number of repository servers earlier. We did that and it should be good now, but we're standing by and we're just waiting for the storm. We especially think that tomorrow when probably there's going to be a lot more news and a lot more people online who are not asleep or watching the Warriors game, it's going to be a lot more busy. For now, GitLab.com is online and of course there's also lots of people downloading GitLab and running it themselves. QualHorse asks, can you talk about the backend server architecture we're using? Cloud? Yes. We're hosted on Azure of all places, so we're going to be moving from Azure to Google Cloud Platform soon and maybe someone, a moderator, can link to our architecture documentation, what you get if you type GitLab architecture. Oscar Montiel asks, what does Microsoft buying GitHub mean to the way GitHub operates and what does that change where you see it coming from? Obviously, we're not GitHub, so we can't comment on that. The only thing that we can speculate is that Microsoft shown recently that they care a lot about Azure. They now have an Azure department, no longer a Windows department and they were working closely with GitHub already to work on that, so we think it's related to that, but that speculation we'll have to hear from GitHub when they send out the press release. Brett Jones asks, what kind of effort are you putting into speeding up the overall performance of GitLab? A lot, a lot, so there's maybe two separate things. First of all, we're trying to keep GitLab.com online right now with the onslaught, we're scaling up all the servers, but we've also done a lot of performance improvements. Those are detailed every month on the release posts and things that I'm looking forward to that are still working, that we're still working on is the merge request view. That should get completely into view and that should get a lot faster then. And GitLi 1.0, with GitLi 1.0 will be able to deprecate the NFS servers and have a lot more reliability in the Git repository hosting. Josh says, great job. Thanks Josh, appreciate it man. How can Microsoft eventually destroy GitHub, but we're not going to answer that. There's a question about, is the GitHub acquisition 100% confirmed yet or not? Yeah. The way it was worded in the Bloomberg article was that it was a done deal, so we're going off of that. Someone stopped watching Silicon Valley. Yeah, you'll be able to catch up anytime. I think they stopped after like five episodes or something. The last one was 51% or something. It was genius, like usual. Alexander asks, if more and more people start coming to GitLab from GitHub, do you think GitLab can become a complete replacement? Alexander, that's a great question. I think there's a couple of stages to it. I think what we tried first is to become the most popular for self-hosted. And it's in our strategy. Maybe someone can link the sequence paragraph in our strategy in the YouTube chat. First one, get most popular self-hosted. Second part, get to most revenue. That's where we're focused on now. The third one is get the most popular SaaS for private repositories. And I think that's what you're seeing now is that we're at least growing a bit faster than we used to there. I think the last thing to move will be the open source projects. We're already seeing open source projects moving. GNOME recently, to a self-hosted server. But for example, FDroid is hosted on GitLab.com. There's a huge network effect there where you want to be hosted on the service that has the most developers. And although you can log in to GitLab.com, with your GitHub account, it makes sense that those will be the last projects to move. So I don't have the illusion that tomorrow all the open source projects will move. That will happen later. And that's fine. I'm seeing URLs being pasted in our Zoom chat, but I'm not seeing them on the YouTube chat. And I think most people can't see them there. But you have to be a moderator to post them in the YouTube chat. So if someone can do that, that would be great. Thanks. Brennan linked, will there be an easy way to migrate GitHub pages? We already have GitLab pages, but automatic TLS is a feature we still have to do, I think, for the automatic TLS, for the custom domains that is. People like our Tanuki better than the Octocat, although they call it a fox. It's a Tanuki people. And it's a Tanuki because our old logo kind of looked like a raccoon. So this is kind of like a raccoon dog. And it's a fox because foxes are super smart. They collaborate, they're super social, and they work together. Just like more than 2,000 people contribute a code to GitLab. Anybody in the Zoom call with a question? If not, we'll go on with the YouTube. What's your favorite operating system? I'm torn here, but I still Ubuntu, but we had to use Webex to call with customers, and Webex didn't run on Linux. So I switched, and I'm doing this for my MacBook. So another question that came in was about our free tier and free features. One said, are there going to be more free features? And another one said, do we have to charge a fee in the future because we'll have too many free users? If you could talk about our view on our free tier and open source users? Yeah, thanks for that, Brendan. I don't foresee any changes to the free tiers. Might be because of heating up competition with GitHub that we will be forced to do something, but we don't have any plans. We can handle the influx of free users to GitLab.com without a problem. Steve in the YouTube chat asked, do you reckon GitHub's acquisition will change your remote working paradigm? No, we don't expect that to change. We're 270 people from 270 locations, and even today, we're all remote, or maybe especially today because it's a Sunday. Someone asked whether I'm the CEO. Yeah, sorry for not introducing myself. I'm Sid, I'm the CEO of GitLab and a co-founder. There was another question about Tanuki Swag. I know it's not exactly... We have a hard question. It's shop.gitlab.com. And I hope there's stuff in there. If you can still get them, I recommend the sunglasses, although the hoodies are pretty sweet too, Brendan. The hoodie is in stock. I'm looking at it right now. They're sweet. Yay, the public monitoring is back up. Yay, we had to reboot the server. That takes a while. Jorge asked, does GitLab handle roles like admins and contributors that only get right access to some repositories? Yeah, for sure. There's five different tiers of users and you can mix and match them. So very elaborate permission system. Juan Carlos asked, is GitLab ready for many migrations from GitLab? I think you mean from GitHub. We're as ready as we can be, but we've never done this before, so we'll see how it goes. Another question that came in, Sid, is there an easy way to migrate GitHub pages, specifically GitHub's custom pages and automatic TLS? Yeah, so we don't have the TLS for automatic pages and it's annoying because I know because I did it for sites.com, my legal first name, and I did it last week, and even our instructions are outdated. You have to download let's encrypt and then you have to put a special file inside the repository, have let's encrypt, check that, and then you get the keys and then you can paste them into the GitLab interface, but it's not where we want it to be and we're working on making it happen. Maybe someone can paste the issue and we really appreciate help there. So we have a question about hosting FBX STL files, so I think those are binary files. So I think the question is about hosting binary files and having an artifact. Yeah, so thanks, Mattia. I see it's from snail.mil.games. There's a couple of things. I'm not sure exactly how big the files are. These people are talking about, you can just add them to a Git repo, but you also can do if they're really big, you can add them as Git LFS, large files. That way, they're not part of the Git repo, but they still get communicated and GitLab has support for that. So those are basically your two options. And recommend if they're big and they tend to be big, you use Git LFS. So I have a couple of other questions. There's questions about being acquired or going for an IPO. There was a question specifically about that by Alexander Snornikov. Do you guys plan to IPO or be acquired? We're planning to IPO and we detailed so on our strategy page maybe someone can link it. However, we have external investors, so it's not totally up to us what happens. What we're trying to do is grow as fast as possible and make sure we're always more positive about the future than other people. But what we're seeing in the market right now is that maybe companies like us don't get bought for the revenue, but get bought for the developers, which is something I didn't know. Something I didn't anticipate. Sad at our 256 asks, what are you guys going to do if you run out of storage? Add more servers. So we got sharding. I think we're up to 170 terabytes for the Git repo, so I think it's going to be fine. I don't go asking, give a quick diff between the free tier and the paid tiers. The easiest thing to go to our pricing page, I think the thing to know is even our free version, like the whole scope of GitLab, all the way from creating issues and managing them all the way to monitoring your apps, that's all part of it. But as you start working with more and more people and getting more and more advanced in your DevOps, it pays to buy the extra features. It's actually up to 194 terabytes said, so. Thanks, almost said 200. I posted the monitoring link since that's back. Awesome, yeah, and very proud that that is public. What's the biggest thing that worries us about the GitHub acquisition? In the short term, we're worried about GitLab.com failing. In the long term, Microsoft is a formidable competitor. They got lots of talented people. They really embraced open source and you only have to look at VS Code to see how good they are in making developer tools. And they got a big budget because Azure is going to bring in a lot of money for them and anything they can do to drive adoption, there's budget for that. So we're not underestimating what we're up against here. Another question came in said about what solutions do we have for file preview and web visual diff? Can you talk about that? Yeah, so I think what's really cool in GitLab right now is that it has a web IDE. So you can look at multiple files, add up multiple files and do that. There's also, of course, all the regular diffing there. I think it's interesting that GitLab was the first one where you could solve a merge conflict in the user interface. As we get bigger, we'll support kind of diffing for more files. Right now we support mostly images. The problem is that we want to make sure GitLab is good for self-hosted too. So we've got to be a bit careful with adding dependencies. Another question that came up said that I think I'd be interested to hear you talk about is why do you think women in tech should migrate to GitLab and can you explain how it works for student licensing? Student licensing. So for student licenses, students are free. So if you're a university and you want to get a pay tier of GitLab, you don't pay for the students. And I think women should migrate to GitLab just as good as the men. I'm really what I'm really looking forward to. I've been involved with Rails Girls. My wife is actually organizing Rails Girls Amsterdam soon. Again, she's flying in because she lives with me in San Francisco. So she's going to fly down to Europe for that. And with GitLab, you have everything in a single application. So that should make it easier to get started because I've had so many, I was a coach a lot of times and you sit next to someone and you have to explain, oh, now you download Git and now you download Xcode and now you download this and that. And it's like, what's all that stuff? You're installing Ruby on my computer and it's taking so long. We have every Rails Girls event has an installation party, the Friday before an installation party. That means we have to spend four hours installing stuff so you have to come a day early so we can actually work on that and not have it be a distraction during the Saturday where we do actual work. It's super sad and it's always a lot of fun but I'd rather have just a party without the installation part. So with GitLab and the Web IDE and Auto DevOps, we're really trying to make that easier. So if you're new to programming, you can start and you don't have to install all that stuff on your PC. And if you come on, like I had people come up to me and say, I'm sorry, it's a Windows computer because someone else told them they shouldn't come in with a Windows computer. Like that's ridiculous. We should fix that and not have, whether you have a Chromebook or a Windows computer or a laptop, everything should work. You shouldn't have to own an Apple laptop just to get started with programming. You shouldn't have to spend four hours installing it. Sid, there was a question about the reasons why we're moving to GCP from Azure. Yeah, we're moving because we really like Kubernetes and we want to run GitLab.com on top of Kubernetes. And right now GCP has the best Kubernetes service. If you have projects on GitLab, you can also add a Kubernetes cluster to it. So GitLab automatically deploys and runs tests and security tests and everything on that. But we want to eat our own dark food and make sure that we run GitLab on top of it as well. Peter Chung asks, what are you excited about seeing coming down the pipeline for auto DevOps? Oh, there's so much coming down. Thanks for asking, Peter. It's already like we're going to, GA make it generally available on 11.0. That's the 22nd of this month. It's less than 20 days away. I'm super excited about that. You just push your code and we make sure your unit tests are run, your integration tests are run. We run performance tests with like site speed. In the future, we're going to run low tests, but already run like security tests. If you have GitLab Ultimate, run four different kinds of security tests. SAST, DAST, container scanning, dependency scanning is really amazing how much stuff we're kind of doing by default. And it's getting better where your logs, we're going to have logs by default. We already have metrics where you can see all the, all the metrics in Prometheus. We're going to add tracing. So having that all work from the start, I'm super excited about that. And Ender has asked how to follow incoming features. I think a great page to look at is our direction page and our product vision page, which is linked below that. So maybe someone can add those links. And I said, I'd like to add, they can always opt into the newsletter by choice. Good one. How do they find the, just Google GitLab newsletter, or how do you opt into that? Yeah, we'll tweet about it and we'll put a direct link. Someone asked whether we can migrate the stars on the repositories as well. I'm sorry, no, but you'll have to start from scratch there. I do hope you like the GitLab stars. So there's a question about how much of GitLab's infrastructure is inside the Google Cloud. So I'm guessing that's in terms of how many servers do we have, or which parts of GitLab are currently in GCP. Yeah, I think it's, we have a few hundred servers right now. Let me share my screen. So this is a problem. I'll go to the non-public monitoring. I'm sorry, there's a bit more information here and it's due to, we have some stuff sell in influx instead of Prometheus. And I think what's, where we have most servers is with autoscaling. So these are like the number of servers. It's very low, but normally this is more than a thousand servers on a busy day. But we scale it up and down according to how much demand there is. Yeah, so now it's only a few hundred to a few hundred machines. Yes, speaking of that said, there's a question about how we're planning to afford the expenses that will arise from the vast majority of programmers switching to GitLab. Yeah, so expenses go up, but also income goes up. So the nice thing about the nice thing about software is that you make it once and you can sell it multiple times. So although there's costs associated with hosting, I think we'll also have more and more companies switching and more opportunity to convince those companies to start paying for the extra features of GitLab. Giovanni van Gel asks, which features are you lacking versus GitHub? A few, I think they're pretty detailed, but I hope someone can paste a link to the missing section of our feature page where we detail those. I link to the comparison page, but I will add that in as well, Sid. Cool, I'm very proud that on our feature page we have a missing section. And Sid, there's an interesting question about are private repos going to remain free? Yes, snail metal games are, since you're planning on using Kubernetes, will you support recently announced Kubernetes GPU containers? Yes, we don't have any plans right now, but I do think like multiple times of multiple kinds of compute is the future. So where you now have basically kind of CPU network and disk, you're going to see more GPUs. You're going to see the TPUs for TensorFlow for the machine learning. You see now hashing machines, machines dedicated to hashing, for example, Bitcoin. And we're going to see more and more of that. Do you have Intel now releasing processes with FGPAs on it? You're going to see more and more. And it might also go to the boundary where you now have a typical cloud has like tens of locations. Maybe because of latency, those will move closer to the edge, closer to, for example, the mobile networks. We're going to see, but I think that Kubernetes is going to be a great force in this and we'll try to support whatever Kubernetes supports. Could we add the ability to watch a few stargazers? So people that start your repo, I think that'd be great. But I think that would probably be a feature proposal, as we call it, something that we'd love for someone to contribute to good land. Said there's a question on transparency. David says, I'm a big fan of transparency. Can we continue to rely on you guys letting us know anything we need to know with regards to uptime, for example, the intern who tripped the circuit breaker, etc. So will we continue to be transparent as we are today? Yes, transparency is one of our six values and we'll keep doing that. And thanks for appreciating it. And if someone can paste a link to our value space, that'd be great. They said there's a question about, for those not looking at an immediate transition, is there a way to keep GitHub and GitLab in sync? Would that need to couple together Bash or other scripts to manage them both from the CLI? Yeah, thanks, David. And who asked that question? Is Dave asked a solution architect with GitLab? Yep, yeah. And I know who you are. I thought it was coming from the YouTube Brad chat. So I want to make sure we attribute the people that ask questions. I apologize. I said that was from Michael Stelkin, I believe. Okay, cool. Yeah, Michael, thanks for asking. There is support for mirroring. So GitLab can do both, but we only support one type of mirroring on the free plan. And I think that is having your repo in GitLab and then pushing it out to GitHub. If you have GitLab as the primary location, you can make sure you keep a mirror on GitHub, for example, to make sure people can easily find it if they're searching there. And as usual, there's a link to the docs. So maybe Dave Astor, or sometimes he's called disaster in the company. It's not because he is one, but because he's a force of nature. It's a compliment to you. Can we do more streams like this in the future? This is seriously better than HBO. It comes from coding blocks. Well, thank you very much. I think it's exciting. I like to do it, but I think we'll do it on special occasions because there's nothing sadder than sitting in a live stream all by yourself. So we need a kind of a minimal amount of people. But if you enjoy those on our YouTube channel, we have lots of content like this. So we got, for example, an AMA with Vili Iltef, one of our investors that we recently uploaded. And there's like GitLab 101 sessions and lots of functional group updates. And we'll start live streaming the functional group updates more in the future. So I'm excited about those. We have a really interesting question from Josh Manners in the YouTube chat. So if GitLab had a chance to be completely rewritten from the ground up, would you still use Ruby or remove to a more performance language, such as GoLine? Yeah, I think every year you started kind of determines what you were written in. So GitHub, GitLab, Shopify, all written in Ruby on Rails. I think it's amazing. I think there's no more productive platform than Ruby on Rails. And if you look at the amount of gems, I think we have over 1,000 non-unique gems in GitLab. That's all stuff that we didn't have to write and we can rely on. However, I can see if you're starting out today, you probably write something in Node based on Express and go a bit heavier on the GraphQL and the Vue. That being said, we have our first GraphQL endpoint coming soon. So I'm excited about adding those. It said another question that came in that I know there's an issue for somewhere that while I'm talking somebody can look up is does GitLab have a plan to integrate Gitcoin or Patreon for open source developer support? Yeah, we're not against it, but we don't have a plan. We tried ourselves with book bounties and we found that was hard. I do think Patreon makes a lot more sense and giving visibility to your Patreon sponsors on like a source coding repository that makes a lot of sense to me. So we're open to a feature like that. There's also, we've also seen examples of people customizing GitLab and making kind of gamifying it a bit. I think that's also interesting. For example, you could get like, right now you can get upvotes for every comment and every merge request and then maybe adding a total score of how many upvotes you got. Now I propose we don't do upvotes for issues because issues are easy. I think good comments and merge requests are a bigger contribution. So I love to see something like that as well but it makes sense to me to list kind of automatically list your Patreon sponsors or something like that. Although you can probably also do that with a link to Patreon. So it's a bit like, should it be in the GitLab interface or not? Don't have an opinion there. Yeah, and I found that link for that issue, Sid, and you actually talked about Gitcoin in that issue, so I linked that in the chat. All right, great. I'm always on the record and it's good too because I frequently forget everything I talked about. Sid, Alfred Myers from YouTube is asking, how is GCP's Kubernetes different from Azure's AKS and when did we decide to go to GCP route? Yeah, I think so Google Container Engine is a bit more mature. They were earlier. I think they spend a bit more time. It's working in a bit more scenarios. I have no doubt that Microsoft will catch up. I think they hire Brendan who created Kubernetes. So they're going full speed as well. Decision to move to GCP was taken before this acquisition was announced so way before that months ago. The question we answered, Sid, in the chat, but maybe you could talk about it. They were just kind of asking about what stack we're on. PHP or MySQL or Node, maybe you could just talk about our technology stack. I know we talked about Rails a little bit, but maybe you could talk about the rest of it. Awesome. Yeah. So a lot of code in GitLab is Ruby on Rails. Then for all the code that needs to be more performant, it's written in Go. So we've got several Go applications inside GitLab. It's not a kind of a pure micro service architecture, but every time we find something that we kind of have to make more performance and we can isolate, we spin it out. An example of that is GitLab Workhorse. An example is Gitaly. Database-wise, GitLab runs on both MySQL and Postgres. We're big fans of Postgres. We're thinking that it has a lot of awesome changes every month, so we recommend people to use Postgres if they can. Other than that, I think there's some HAProxy in there for our stack and there's a lot of Prometheus in there for all the metrics. Big fans of Prometheus as well. Is there anything you would like to tell a GitHub user that has never used GitLab before but who is nervous about switching as a question that comes from Ravelin1? Yeah, thanks for asking. It depends a bit why you're nervous about switching, but I'd say what you can try is give it a try with just one or two repos. And I think a great reason to switch is that with GitHub, you get the code hosting. With GitLab, you get the whole experience all the way from issue creation to monitoring what you've made in production. So things like auto DevOps. To create that on GitHub, you'll be stringing together a couple of applications. And on GitLab, it's all part of the same interface. And I think that's really neat and you should give it a try. Oh, and I forgot to mention in our stack that we're using Voo a lot. And we've been on the record about that. We were one of the earlier big projects that we're moving to Voo. And it's been an awesome, awesome experience. Our front-end team has been very productive. And I think a couple of years ago, our interface, our navigation wasn't up to snuff. It wasn't fast enough. It was not great. And I think the front-end that you were esteem has done an amazing job. And although GitLab has a lot of functionality in it, we frequently hear that people like the way it's organized and they can navigate it. So Sid, Snail Mail Games asks, what Git client would you recommend for using GitLab? Additionally, what Git client do you use? Yeah, thanks. If you get started, there's different options. I think Git Tower is a great Git client. I do recommend at some point that people try to go to the comment line. The problem is that all the clients with a GUI have a limited set of functionality. And then when you need that extra functionality, if you then have to also make the switch to the comment line, it's a lot to take in at the same time. So you rather kind of already do your day-to-day with the comment line. Then when you hit that really hard problem, you have more of a feel for it. I use VS Code and the terminal window inside that. And VS Code, both because it's great, Microsoft did a great job, but also because the Web IDE inside GitLab is based on the monocle editor of VS Code that Microsoft open sourced. And yeah, when I'm not using something local, I'm using the GitLab Web IDE. Sid, Josh Manders asks, how are you enjoying Vue? I'm a React developer primarily, but I've never been unhappy in a Vue project. Yeah, I don't have any experience in it. I can't even program JavaScript. I used to be a Ruby on Rails developer for doing this, but I'm hearing that our people like it. I looked at the code examples, and it seems like Vue is just so the... It's simple and beautiful, and I love how those code samples look. I think Evan did a great job of kind of simplifying and putting all the best practices together in one thing. And there was this cadence where there was a new JavaScript framework coming out like every three months, and I think Vue put a stop to that. So great to see that. Raven asked, are you worried that feature people ever make GitLab 2 unwieldy, rolling out new features every month? Lots of features. Yes, we're really worried about that. It hasn't happened yet. I think there's a couple of things that we can do to prevent like GitLab collapsing under its own weight. One of the things is boring solutions. So we always try to make sure that any technical innovation we do is not something that's hard to understand because our mission is everyone can contribute. So we keep it simple. That already started when I first started Codebase. GitLab was a year in. 300 people contributed to it. I opened the project up and it was just pure vanilla idiomatic rails. And we kept that spirit. Don't make it harder than it should be. Think about it carefully. Have your models and your abstractions as simple as they can be, but without trying to overdo it. And I think that served us well. We got lots of automated tests. I think there's over 100,000 tests now being run. If we check or commit, it could be tens of thousands. But all those tests make sure it doesn't break and we're still able to add great new features. So right now we're not worried. I'm super proud that we're able to expose it all in an interface that also makes sense. Peter Chung asks, can GitLab CI completely replace Jenkins? Yes. Have you achieved feature parity yet? I think so. Maybe someone can add a link of what Forrest has said about the comparison between GitLab CI and Jenkins and Spoiler Alert. GitLab CI is much better. Another question that came in. Well, not a question, a comment. I just thought you might look here. It says Josh Manders said, the speed issues were what discouraged me last time I reviewed GitLab. But I have no qualms now. So great job there. Awesome. Josh, thanks so much. Glad to hear it's better. We're not happy yet. So we're still hiring. You know, any great system reliability engineers send them, site reliability engineers send them our way. But I'm glad to hear it's improved and it for sure has improved greatly. Still have a way to go, but we're getting there. He said, I see a question asking you to just share some of your thoughts about improving GitLab's UI and social aspect. There's been some comments about that throughout the day that people are hoping that GitLab becomes more social. Yeah, thanks. I think with GitLab, we really focused on what the users of GitLab want. And the users of GitLab tended to be larger organizations that were self-managing their own installation. So there's lots of very advanced features if you want to work with lots of teams. For example, we GitLab supports subgroups and many things like that. Only now are we seeing open source projects coming in like GNOME and Debian. And we hope that those open source projects will also kind of help us develop new features aimed at open source. Both help us by asking for it and commenting on the relevant issues. But also kind of hope that some of the features will be contributed. I see I got one here from Jorge Durango. Is Bitbucket even a competitor? Yeah, David, thanks for that. And thanks, Michael Skelton and Jurja, for speaking up. We don't tolerate in the YouTube chat someone is commenting in accordance with our diversity values. So just simply cut it out. That's not how we operate. We won't tolerate that. And if needed, we'll stop the entire live stream. Diversity is really important to us. And we won't stand for that. And thanks, people, for speaking up. That's what we require. David, your question was about whether Bitbucket is a competitor. For sure, they are a competitor. And they're a solid one. And this is a market with GitHub, GitLab, and Bitbucket. And they have some great things that we could learn from. Daniel asked, does GitLab have a documentation service, kind of like GitBook or read the docs? I'm not sure. I know the people, I've talked to the people from GitBook a couple of years ago. I'm not sure whether they support GitLab. What we do ourselves with docs.gitlab.com is that we run it as a static site. So we kind of take our slash docs directory and we put it online as a static site with GitLab pages. So that might be the best way to do it. Sid, Josh Banders says that he was an original signer of the Dear GitHub movement. How much has that letter influenced any of our decisions at GitLab? Thanks. Yeah, I think we placed a blog post then that said Dear open source contributors. And a lot of the things that people wanted at that point were already inside GitLab. So I think it was validation for us that we were listening paid off. We're just listening to what people wanted. And some of the things that we didn't have yet we are after that prioritized. Sid, there's a question by Edwin Cascio asking how will GitLab be in the next three years? I guess what is your vision over the next three years? Yeah. So I think we get a great product vision for this year. If someone can link to our product vision that'd be great. The basic plan is to go from just Dev to also doing all of ops. So really doing complete DevOps. I think that's really exciting. I think what we want to do as a company we want to help other organizations have a 200% faster DevOps cycle. So where you now collaborate and you hand off between the different tools you kind of have your planning tool and then you hand off to the coders and they hand off to the QA people. They hand off to the security people and they hand off to the production people. And it's all using different tools and you have to string all those tools together. We think that's inefficient. Not only on the time wasted on integrating all the tools but also because if you're in one tool the other people can't work at that point. So you can't work in parallel. If you can't work in parallel because you're using a single tool like GitLab now you can get changes out a lot quicker. And the quicker you can get out changes the more feedback you get the more of a sense of progress you have. And I think that's really important in any job. And that's why we're going to help people and we're going to add more and more features to GitLab to get there. So that's the path we're on. As a business we're doubling our incremental ACV every year. So a lot of extra recurring revenue every year and we want to IPO by 2020. So in three years that should be the case. Sid, do you want to explain ACV to those who might not understand that? Yeah thanks for that. Incremental ACV is incremental annual contract value. It's we have a subscription business. If you buy GitLab whether you run it yourself or on GitLab.com you get a subscription. And if you're in a subscription business you kind of look at you don't look at you have the money you already have from the existing subscriptions. You look at what's coming on top of that. And then for the existing people are they going to spend more or less with you. So the incremental ACV is like what's getting on top. Suppose you were doing 1 million in revenue last year. If you're doing 3 million at the end of the year you had 2 million in incremental ACV. Set error ask what's your favorite IDE and text editor. So set error look what's the sublime person for a long time. Now using VS Code locally but I'm really liking where the GitLab Web IDE is going. And sometimes I regress and use sublime still for note taking not coding. And I try to use Vim a couple of times. And I think I know how to delete a row with double D or something. But it's it's I'm glad I don't have to earn my money that way because I I be very poor. But you got it you were able to exit it though. That's yes I'm able to exit yes. A question came in from snail mail games said does GitLab have any built-in unit testing or as a plug-in for the platform? I was going to maybe queue you up for AutoDevOps. Sorry if you didn't. Yeah yeah you want to give it a try Benden the AutoDevOps one. Sure sure. So we've got a feature that we did we GA it in 10.8 did we know I know it's either GA in 10.8 or an 11.0 which is coming out on the 11.0. So we release a couple of quick things about GitLab. We release on the 22nd of every month we've done that for almost 80 months. And so we'll be releasing on the 22nd of June GitLab 11.0 which will make AutoDevOps generally available that's something that's been around for most of the 10 series of GitLab. What that does is let you upload your code and without having to build anything for your pipeline it automatically build your code automatically runs in a unit test that you have in place. Automatically does a bunch of things like security scanning, scanning your container, doing static code analysis, a number of other things and then it also can deploy automatically into production or into a review app and into production if you connect your GitLab instance to a Kubernetes cluster. So there's a lot of great open source magic and some GitLab magic under that. We use Herokuish build packs to detect the language. And automatically dockerize the application and then we use Helm and Tiller to get that into Kubernetes automatically. So definitely check out AutoDevOps. We'll put a link in the chat. It's one of my favorite features of GitLab. And I think this Wednesday we're having actually a webinar specifically on CICD. So we'll also find that link so you can learn about that. Someone asked, we're going to get a shirt with the logo of GitLab. Well, thanks for asking there. Shop.GitLab.com should have that swag. Hey, I'm wondering about something. And I'd love to input from the people currently watching the livestream on YouTube and commenting. We're thinking about doing a discount code for people moving to GitLab. So not for the people already on GitLab but for the people moving kind of to help them and also to kind of amplify the trend. Now, we want to make sure that anything we do is sustainable. So we're thinking about doing the discount off our highest tier so that would be ultimate or gold and it would be 75% off for a year. And to qualify, you have to Twitter anything with the hashtag moving to GitLab and you have to email us. What do people think? Well, that question answers come in, Sid. There's a question here that talks about Edwin Castillo. He's asking, are there people from Latin America like Columbia, Mexico, etc. working at GitLab? Do you want to comment on how our global workforce is set up? Yeah, for sure. And we're working on making our team page better because I think it currently doesn't most people are not listed on. Everyone is listed on the team page, but most people aren't listed on the map because you have to sign up to teleport for that. But these are people in South America. So we have Mario who's in, I forgot the country, but it's not going very well in that country right now. Nicaragua. Nicaragua. Thanks, guys. And then we might have more, but I think there's way less people on here than are here. So you can have a look to all the people working in GitLab. And I hope that the situation in Nicaragua improves for everyone there. So Sid, Sun Kim asked, this might turn GitLab into a social network site, but will GitLab provide a feature to contact chat with open source developers? Do you mind to share a bit about GitR? Yeah, thanks, Lukas. We acquired a company called GitR a while ago, and what GitR allows you to do is in any project you have, whether it's on GitLab or on GitHub, you can add a button. You kind of have an instant chat channel, kind of like Slack channel or an IC channel, but one that's really easy to access for everyone. And we think that's a great thing to do. So recommend using GitR for that. Sid, some responses came in for the discounts. Question you had? Yeah. I can do more. So Josh Mander says, I have no opinion. I've been a member for two years. Saturday 256 says, sounds good. Do it. Movable Singularity says, yeah, discounts. We have snail mail games saying, do it, do it. And then a couple of other comments with some interfaces. Cool. Thanks. Well, we haven't decided yet, but thanks for the input. I'm glad that it's sounding reasonable. We still have to decide on amount, terms, timing, and everything, but thanks for the feedback. Hey, Sid, we have a question from Douglas Augusto. He says, has GitLab used machine learning algorithms in any part of the product? Thanks, Luka. We have not. I do think there's a lot of scope for that. And on our direction page, we detailed some of the things we think we can do with that. So I'll screen share that. So signal versus noise, especially with all the security testing we do, recommending labels, auto scaling applications, lots of things we can do with ML and AI. But for now, we're super focused on doing complete DevOps. So we're prioritizing that. So Veide asks, what's the nature of the split between the open and closed-source parts of GitLab? Is it pretentious for closed parts to be opened up? Or are contributions at risk of being made closed-source? Thanks for asking. That's a great question. So a few things. When something is open, we never close it up. Whether it's our code or community code, that never happens. If you contribute it, you can select which repo you contribute it to and if you contribute it to GitLab. CE repo, it will always be open-source. Sometimes we do open up code that was closed-source before. A good example is GitLab pages. And that's because when we think we've made a mistake and something should have been open-source anyway, and we find that out. If we make a mistake the other way around and we think, oh, that should have been closed-source, our bad, we'll never go back. Another thing in that category said it would be the Web ID. We thought we were going to make that closed-source. Yep. Thanks for that, Brandon. Good example. Snail Mail Games keeps the great questions coming. Thanks, Snail Mail. And does GitLab pages support preview of 3D models, such as Sketchfab? I don't think so. So I'd love to see that added if it comes without too many dependencies. There's a helpful suggestion from Nemesis Contreras, something that could help GitLab, too, is providing a super simple explanation of why GitLab is a good alternative to GitHub due to the massive migration from Microsoft buying GitHub. Yeah. Thanks for that. We're working on a blog post that should have a few of those things. And people have been tweeting reasons why to move to GitLab. And we're working on putting all of that in a blog post. So here's some tweets that we're thinking about. And also for the people at GitLab watching this, only four. I think we can do a better job here. So I would love to have some extra tweets here. I think it's hard for the people on YouTube to contribute because YouTube doesn't let you post any links. But people know way around that. Maybe after you start, you can start with the slash and then we'll find the tweet. Michael Skeleton says, the importing engine seems to be down. Any ETA on the fix? I've been in a live stream for the last hour. So I'm not aware what the status is. Can someone check GitLab status Twitter and see what's up? Ah, thanks for mentioning. He says, I used GitLab before. The UI wasn't very good. However, on the news, he now checked back and it's much better. 10 out of 10. So that's really great. Do you offer discounts for non-profit companies slash charities? Unfortunately, right now we do not. Firstly, 111 asks where GitLab company is registered. So we're based in San Francisco, GitLab Inc. We already also have a couple of companies around the world because we hire people in over in 40 countries now. And in some of those countries, we have our own organization there on our own payroll. Real talk, if possible, as an aspect crawl, are all of the GitHub features that one would want, apart from the missing ones available in GitLab without having to pay? Oh, that's a good question. I think there's some features that GitHub charges for that we also charge for. But I couldn't tell you which ones because I don't know. So anyone at GitLab that knows, feel free to speak up. I'm not sure about that, Sid, but I was just jumping in our production Slack channel here. So the importer is working. There is quite a backlog. And some will 502, as I usually mentioned on YouTube. You should be able to try again. You'll probably be okay. We're currently spitting up a large number of psychic nodes, which is our backend job processing piece of the stack. And so we're pulling that error rate down, but there have been a few. Cool. Thanks, Brandon. Mohammed asked, what about education discounts or student death packs? We know that a lot of universities are running GitLab. And if they want to get one of our pay tiers, they don't have to pay for students. So that's what we currently do. But maybe we should do more there. So anybody have the real talk about which GitHub features you have to pay for? I think possibly the best to look at our pricing page and see what features we ask money for. Because there's so many. On the pricing page, there's a CEO features, and that's the most extensive one. I'll screen share to make sure people are clicking the right way. So here's our pricing page. This is like the top line features. But if you click this, you can see all features. Matt asks, is there a way to separate an account into a standalone account? I signed into it with GitHub. I think so. I think there's the ability to set a password later on. But I'm not 100% sure. Sid, there's a really, I think, important question here from Blackstone. Are there any plans to encourage community contributors to contribute to GitLab? I think this is a really key question to answer and highlight the difference between GitHub and us. Yeah. Unlike GitHub, you can actually contribute to GitLab. And lots of people do that. Every month, we have about 1,000 new changes in GitLab that were contributed by the community. And I think I recognize Blackstone. So if it's the same Blackstone, he contributed a few. But he's asking for a badge or an icon. And I think that's a good request. Like, wouldn't it be cool if your GitLab avatar showed that you contributed to GitLab itself? So I like that idea. Kind of when you view a project, a way to distinguish which people contributed to that project and which ones did not. That makes sense to me. So if you're free to open a feature proposal for that. And Sid, didn't we recently have an announcement or a blog post about our 2,000 community contributor to GitLab recently? Yep, for sure. Kevin asked, oh, but one of my repos successfully migrated from GitHub. It's also the only one that had issue tracking set up in GitHub. So I'm wondering if that's causing issues. I'm going to change. Go ahead. I would say there's two things, sorry, Sid. There's two things there. One, it could be related. So there is also an API rate limit that you'll hit eventually for your personal rate limit against GitHub. And so there's a lot of API calls made to transition the issues over. So you may want to, again, try that again in like an hour or two once you've been on rate limited. Thanks, Brandon. Firstly asked, is there plans to integrate Gmail login to GitLab? I think we have login with Google for GitLab.com, but I'm not 100% sure. But I'm like 90% sure. Eide asked, does GitLab provide repository license metadata? Not yet. What we are working on is license management. And what that is, is if you're an organization and you ship code and it has lots of open source dependencies you bring in, it will tell you what the licenses are of those dependencies. I think there's also a standard for exposing kind of license information in a standardized format. I don't think that's part of GitLab yet. That would be cool though. So feel free to contribute that. And Drew is helping out the person that wanted to make sure he had a standalone account. So thanks for that, Drew. So what I'm seeing in the live stream and there's lots of questions about features in GitLab, which is kind of awesome. But I think we solved a lot, or we answered a lot of the majority questions about the industry developments. So maybe we should start wrapping this up. Frank asked, my bosses are worried about moving over due to the issue ahead with uptime. Is there a page where you track system issues? Yes, Frank, at GitLab status on Twitter, we tweet about anything that's wrong any time. Do you have any RTF plans for plugins like AppVayer? I don't think so. Remind me what AppVayer does. I think they do CI for Windows. And with GitLab, with GitLab Runner, you can do CI on Windows just as a part of GitLab. So one other question is, I know it's a feature question, but Michael Skelter again asks, are there any plans to add a feature like pinning or similar to it that will allow you to highlight specific projects? Yeah, I think we have starring right now. I'm not against pinning. I think starring and pinning should be probably separate things. But the starring, we want to prevent having multiple features that all kind of have done. So I'm not sure. It's probably a longer conversation so that should probably happen on our issue tracker. So a doctor clarified that AppVayer is indeed kind of CI focused on Windows. Yeah, you can just install GitLab Runner on Windows and then run the test that way. You do have to kind of bring your own machine. Michael is clarifying by saying he meant to, I mean to highlight your largest or larger projects in the large mix. Oh yeah. Like 100 plus repos with two or three that are larger. Okay, I don't have an opinion about that. Yep. Hey, it's been a little over an hour as you noted a while back. So do you want to check for one last question and then wrap up or keep going or up to you, but thought everyone should remember the time. Yep. Thanks. Let's the last one. David, Swarj, you have the last one. How has your infrastructure handled the mass Exodus so far? I'm curious because the past day has probably been quite taxing. I think so far so good. We're still up. We're still importing, but we're bracing for tomorrow. We think we're going to be a lot more tomorrow. So we'll see. But they've done a great job. They scaled up multiple parts of our fleet. So we'll see how it goes. Cool. I want to thank everyone for attending the live stream, asking questions, answering it, and especially Emily for organizing. Have a great day. And I'm sure tomorrow will be very interesting. So looking forward to it.