 Hello, everybody. Can you hear me and still see my screen? I see someone nodding, so that's the answer. All right, my name is Joep. This is the product update. I'm briefly going over what we just shipped in 9.5, but we're shipping in 10 and what we're going to do beyond. But there will be plenty of time to ask questions and ask away, please. So get love 9.5. To me, it seemed like forever ago that we shipped 9.5 because we've been working on 10 for a while, but it was actually just a week ago that we shipped 9.5. And what happens is that it's vacation and people go away on vacation and with very little capacity. So what happened actually is that we shipped another amazing release. The biggest deal, the biggest thing we shipped this release was a GPG commit verification, which started out actually as a contribution by someone from the community. So I'm extremely proud of the fact that such a major feature, such a highly requested feature, comes from someone in the community. So they started the contribution. Of course, we helped them, but this is a really nice feature which basically allows you to make sure that you are the author of a particular commit and no one else. Very important, many people wanted to have this. So this is a really big step in GitLab's history. We also included the whole bunch of new navigation improvements. So you know that we have a new navigation. It's still opt-in. Please mute yourself, even if you're on mobile because I'm hearing someone. And in this release, we shipped a few improvements, specifically allowing to quickly navigate to some parts of a project. AC, I'm publicly shaming you, you're not muted. We also shipped project templates. So GitLab, of course, allows you to not only have your code there, but it also allows you to quickly set up CI. And with project templates, we made it much easier to be using Rails or Node or Spring. You can now just click on the project template and you have a good starting point for a new project. This is a really powerful idea because what we want is that getting started with the project, you know, building something, it should require you to do all this extra work such as I have to type in the commands to boost up my project, then push the GitLab and then I can get started. If we take away all those steps, it saves you maybe a few minutes, but those few minutes, well, you can use them for something else. This is a really good step and it helps people getting started with things like CI much faster. So we can build on this for forever. And every time we add a new feature, we can add it to these templates. It's really nice that we have this right now. Quite a big deal. We also allow you to automatically retry your failed CI jobs, which because sometimes they're not completely deterministic, as it seems. And even cooler, if you are auto-deploying an app. So we have auto-deploy, which allows you to do nothing and have your project basically deployed to your Kubernetes cluster. And with automatic monitoring, we are actually monitoring your app if you've used auto-deploy to deploy it. So that means you don't have to set up monitoring and report them somewhere, share credentials. No, you're just going for press monitoring. There you have the most important statistics. Very cool. You can also shift the beta of Postgres HA where you have automatic fail-overs that if one of your day basis falls over, GitLab will start using the other one. Go back to this. It's a big deal for the future. Now, as I said, we've been working on GitLab 10 for a while already. And all the number itself sets it up. It's a very, very big release. I have only a few highlights here and I ran out of space on my slide. But it's a very big deal. Actually, we're right at the end of finishing work on GitLab 10. We should be finishing next week with the first step in development. And I will go test it to then release it on September 22nd. Some of the things that we're shipping. For one, group-level issue boards. This is one of the highest requested features ever in GitLab. GBG commit verification was another one. So we shipped that group-level issue boards allowing you to manage your issues across a group. I know that a lot of people are waiting for this. We're planning to do it for 9.5, but it's a complex feature. But it's really landing in GitLab 10 and I'm super excited about it. It seems simple, but a lot of people want this and it finally allows you to manage issues across projects rather than in one project itself. We're also working on GitLab server HA basically making it easy to set up an HA instance of GitLab. So right now you can have HA parts. So you can have reddits easily in HA. And now we should post-press but we want the server component also as easily set up as HA. So to make it easy, we're working on a few different things. We're thinking about leveraging console for this. Hopefully this will make it 10. What we're also doing is many of our customers and our users, they're still using Jira. And of course we prefer them to use GitLab issues. But until they finally see the light and switch, we want to be able to use Jira successfully together with GitLab. And to do that, we're going to support the Jira development panel. Basically allowing you to quickly see inside of Jira what is happening with your commits in GitLab. So it's actually quite a big deal. This Jira integration, we even have on our website a specific page just for Jira. If you go to about.skill.com slash feature slash Jira, you can see what we do right now and what we're planning to do in the future. And this is one of the most important steps in it. If we have this, we are on par with the competition and after this we are going to do more. We're also finishing the first iteration of auto-dev-op. So you are familiar with auto-deploy and auto-dev-op goes one step further. So it gives you all the tools. And of course the auto-monitoring is part of that. It basically allows you, I have a project and everything for me is set up. I don't have to think about it anymore. I don't have to think about setting up a CIM or for instance, everything just happens under the hood at GitLab and your project is ready to go deployed with monitoring and everything out of the box. It's a very powerful idea. It's also one of those things that will be extending forever and shipping this first iteration is a very, very big deal. We'll also allow you to lock an issue. Now, you might wonder, well, why is this a big deal? Well, as GitLab is growing, GitLab.com in particular with other instances as well are becoming more social platforms. And unfortunately in social platforms, sometimes you need tools to moderate what is happening. You need tools to stop the discussion and then the ability to lock an issue basically allows you to say only if you're a project member you can continue commenting on a particular issue. So disallowing from a particular issue or take the project, the group, people from the outside to comment even though they might have access. This is an important feature and we wanna make sure that everyone that uses GitLab is confident and feel safe about using GitLab. And these kind of tools help us manage and build communities on top of GitLab and GitLab.com in particular, it being a very big instance. And lastly, and I think this is the biggest change for everyone that is using GitLab today and is running one of the versions and then upgrades to 10 is that the new navigation will no longer be opt-in. No, everyone will just get it. So if you install GitLab 10, you'll be welcome within a new application. This is one of the first features where we said, you know, we're not gonna release immediately but we're gonna make it opt-in and then iterate over the releases until we're in a place where we're happy and confident that this is an actual improvement. And I think for those of you that have been using a new navigation, I think most people agree that this is a big, big improvement. One of the smallest things in it, which I think is already such a big improvement is the ability to directly navigate to some navigation subpages. For instance, if you wanna go to issue boards in old navigation, you had to click on issues, page would load, then you had to click on boards. And with the new navigation, you can just hover over issues and then click on boards. So the page only has to load once, you go directly where you need to go. And it's really important because for once less clicks, two, you don't have to load two pages so it's much faster. And three, we want people to actually visit all these pages. And if you have to click twice and if you have to load two pages, we're raising a threshold for you to actually click on that. And in our research testing, we found that only one in six people could find issue boards, would ever even encounter it. And we hope that these kind of changes will make it more likely that people visit these pages. There's much more to do in terms of making sure people visit these kind of features and that we teach people how to use it, the whole onboarding experience. But this goes a long way in doing these kind of things. And as I said, Github 10 is a huge release. It will be very, very, very full of features. A number of features came from 9.5, we brought them to 10, many of them are in 10. So it's a very exciting release and this is just a small, small highlight of what we're going to do. All right, up next, beyond. By the way, if you like my Rocket GIFs, they were all totally indicative of what is happening. So here we're still shipping the parts and we're still thinking about what to do exactly. Another interesting story, this is the space shuttle on top of a plane. When NASA was building the space shuttle on one side of the country and then they had to fly or they had to bring the space shuttle to Florida, they didn't have a good plan. And it was actually an engineer that had like a miniature plane that they were playing with. And he said, well, why don't we just stick the space shuttle on top of the plane? So they took a model of the space shuttle and I put it on the model plane and they flew it around and it worked perfectly. And then they said, well, let's buy some planes. So that's how that story went. All right, by the way, the space shuttle's no longer flying, it's a big loss to the world but that's not the story. So what are we doing next? Well, a whole lot of things. And I'm going to give you the very general executive overview of some of the things that we are thinking about because it's all big topics that will take many, many releases. And I think it's interesting to know what we are thinking about. So first, we are thinking about extending our range of products. So you have today, Github Community Edition, Enterprise Edition Starter, Enterprise Edition Premium. And then what do we want to introduce Enterprise Edition Ultimate? A tier of features of the product that is interesting for very large enterprises think 5,000 users or more. These kind of enterprises have very unique challenges. There, you have to think about the kind of stuff we need to manage. Github has more than a million users. These are the kind of features that only are applicable to these extremely large enterprises. Of course, they also have very unique authentication, authorization needs and even just managing hundreds of projects. It's a very complex thing to be able to give enterprises an insight about how things are going. Those are kind of challenges that we want to solve with Enterprise Edition Ultimate. And within that, one of the things that we can, we think we have some space to win is to go in the direction of portfolio management, which I think is a terrible name for what it actually does. But it's basically giving you the ability to manage teams and projects from a higher level. Basically allowing to say, well, I have this much capacity in terms of people and ours. And I have all these projects. How do I distribute all the capacity over the projects so that I get a good return on value? And it's all very business-like, but it comes down in good luck and practice that we're thinking about things like giving you the ability to have epics. So nowadays we sometimes make meta issues. Well, let's make that a first class citizen called epics, maybe something in cross projects. And then once you have that, you can start thinking about things like gas charge, which is those charge where you have the horizontal blocks that represent an abstraction of multiple issues. And then having the ability to plan those over time and seeing, oh, if I add more people here, then maybe I can do these things. Or if I take this person from this project and put it in that one, I see that the timelines of these projects change. And that is basically what portfolio management gives you. It's a huge subject. There's enormous companies that do nothing, but ship this kind of software. So for us to say, we're gonna ship portfolio management in GitLab. It's like saying, you know, we're gonna build a car. We already have the bolts for the wheels. It's gonna be a long path and there's gonna be a lot of features that fit within this. But I think it's an interesting direction and it will help us level up the issue tracker because all of these features that portfolio management needs, we're gonna build iteratively over many releases. So slowly, but surely the issue tracker will get better and it will be driven by this need of going towards this point. Like, how can we achieve a good portfolio management product? As always, and I say this almost every update and I'm going to keep saying it because these are the things that are really important. We're still working on HA, we're still working on GL and we're still working on disaster recovery. When you have all your codes and all your issues and all your CI and everything that outputs and GitLab manage your server, you know, it's incredibly important that GitLab is stable. So any person that we put onto this is never a loss and we're gonna keep on expanding the products and the amount of time that we spend on things like HA, GL and the disaster recovery. And as I said before, Autodeflops is another one of those things where you can put the infinite time and it will only get better and so we will continue doing that. Another thing that we're thinking about is conversational development and I'm sure you've heard this before. Right now, if you're an admin for an instance, you can go to conversational development and you will see an overview of how your GitLab instance and its features are used and how you compare to the competition. Now, this isn't a really interesting idea and I'm happy that we built it but today it's still not very useful and what I want to do is I want to make this useful. In other words, I want to show to anyone using GitLab how they are performing and you know that because we say, for instance, you use this many features. We also have statistics such as cycle analytics that tells you how fast you are going and how well you're doing in terms of text and whether the time to value, the time that you should actually ship something goes down or it goes up and where it gets better or where it gets worse and giving you the ability to compare yourself with other teams within your organization or the instance or even across many instances will help you see, okay, I should improve this particular part. Oh, it takes us a long time to deploy something to production. What is going wrong? And that all is what conversational development is about and I hope to make some strides. One of the first thing I want to do is improve cycle analytics to make it actually very useful so that anyone in the team goes there and that teams are proud of this course they achieve and they say to it, oh, our time to value is only two weeks versus the three weeks of another team and that way we increase collaboration between teams and it's just a useful tool to see how well you're performing. All right, two more and then we're done. Authentication for enterprise. One of the things we see if we look at how support is doing and if you just simply go to Zendesk and anyone that works at KidLab can do this, you can go to Zendesk, we have a general account and you can just search for keywords and if you search for tickets that have a high priority and then search for a number of keywords like LDAP, authentication, but also a bunch of other ones with issues and such, you see that things like that relate to authentication, authorization and specifically things like LDAP, there's just an enormous amount of questions and as a product organization, it's first thought this seems a little bit boring but there's a lot of value that is here and making it easier to make sure that everyone can access their KidLab instance and can do so properly. For one, it's very important because you want anyone to be able to enjoy it and two, these things are so hard. I don't know, if you've never tried to set up LDAP, I don't recommend it but you should just start reading a little bit into it. It's just a huge thing. So anything we can do to make it easier for organizations to start using KidLab specifically if they're using LDAP is a huge win for us. So what we're thinking about is making features for KidLab Enterprise Edition Premium that make it easier to work with LDAP and that is gonna be the beginning of this and this is also one of those things where we can invest infinite time but I'm very excited about this initiative. And lastly, and I think this is particularly the fourth quarter of this year, we'll be spending a lot of time on requirements for partners and customers. So as you know, there's many things going on at KidLab. We have very big partners, very interesting partners that have all sorts of questions or requirements and what we will do is we'll take those and we try to make them interesting for everybody. So if a particular partner asks something from us and they say we really want this kind of authorization, we try to build those requirements in such a way that everyone, every customer, every user of KidLab benefits from them. There might not always be the case. Not unless we'll be spending a lot of time on this in this quarter and if you work within KidLab, you will see a lot of this. And that's it for the future. It's gonna be a very, very busy time becoming, I don't know, 10 years but I'm very excited about it. I think these three are all very cool. Let me know if you have any questions. I'll check the chat. I don't see any questions here. Victor H says that he likes the Neo-Navigation a lot. It's great. Also very, very happy with it. Jose says he likes the Gantt charts. Vision is looking good, says Ederon. It's great. No questions about anything in the whole product. The one thing that we saw, you have no questions. It must have been really, Jacob asked me, what am I most excited about? Ah, I see you asking that question with every functional group of day, Jacob. I'm not sure. I say this almost every time. Just making it easy to do things that were previously exclusive to people that spend a lot of time on it. And I think CI and CD and deploying to container schedulers and to containers in general is such a powerful idea. Like it still is, and I will say this, every functional group of day, it still is really hard to just deploy it up. And with autodefops, it's one of the things that finally it's easy. So any work we can put in this, any investment that we can make in this to make it easier for anyone independent of your scale or what kind of project you're working on to just deploy your idea and have it live, I think that is the most exciting thing we can do. And all the features in GitLab should be focused around that idea of helping people get to value quicker. How do you get to value quicker? It's simply by getting stuff deployed, right? That's the end goal of all of this. So yeah, that's what I'm most excited about. Can Cushall, can have code names for releases starting with 10? Cushall, I think that's a really great idea and also a really bad idea. It's great because it's a lot of fun to have code names for releases. It's a really bad idea because no one knows anymore what release you're talking about. I have never any idea which boot to release I'm looking at because one occasion they call it the snarky snark wall and the other they call it 17.6. It's horrible. So no, I don't think that's a good idea. You can call it something but not publicly because it's just confusing to people. AJS, do you think portfolio management elongates an already long enterprise sale cycle? I don't think, I don't necessarily believe it will elongate the sale cycle portfolio management feature. I do think that enterprise edition ultimate might have that effect. But I do think that there's grace we can help to speed that up. Jacob says, how do you do that? I think he refers to making it easy to deploy auto-dev forms. I really believe that's the answer. It's also an easy way to say, just make it automatic. But I think that's a very good stuff. Jacob says, can we name them after celebrity based on a letter in alphabet 10.1? You need one that starts with A, so Angelina Jolie, 10.2 Britney Spears. Yeah, that's a very horrible idea. Sorry, he says, what area of the product do you think you used most of your improvement? That's a great question. I think onboarding is the weakest part of kid lab right now. So we fixed the navigation. I think that's a good start. I think onboarding in general is something that we basically don't do. And I think there's a lot of work to be there. I think there's a few other ones. Sarah found that there's a need for dashboards. I think the entry experience in the kid lab is not very good. We just give you a feed of decks. We can do much more there. People like visual stimuli in that sense. And we're also working already on this. But setting stages, they are hard to navigate. And it's hard to parse. There's a lot of work to be there. While on one end, search is also not very good in terms of UX. So there's a bunch of you for there. I think the biggest bank for bug is providing a good onboarding experience. Joe asks, how is product engaging with enterprises that would be candidates for ultimate? How can we help? Well, what we're doing is we're trying to talk with enterprises that are already using things like portfolio management and other features that we are considering for ultimate. How can you help? Is it whenever you have one of these enterprises that you know of, okay, they might be using one of these projects, say Rally, for instance. Bring them to me or bring them to Victor specifically who's working for a lot of time on this. Bring, say to Victor, hey, Victor, this is an enterprise. They're using this product right now. They're clearly not gonna switch to GitLab because we're lacking these features and go talk to them because we need to know as much as possible so that we can focus on the things that are important and we can ignore the things that are not important because we only wanna build the things that make our customers switch to GitLab and forget about the things that those kind of software do we don't actually need. So it's very important that we talk to these customers, bringing us closer to them is a great idea. Victor says that John M is already putting me in contact with folks. Give me more, all right. And John Wood says, plus one important GitHub repos on Mars. You can already do this in GitLab, but we can always improve these kind of importers. All right, three more crickets before I'm gonna call it off. Three crickets, two crickets. All right, thanks everybody. See you in the team call.