 So, we should be live now, and I'm going to just start sharing my screen, which means I can't do anything for seven minutes. But I'd rather do that than have something go walkie. Okay. Oh, wait. Jeremy goes first. Okay. So I should stop. Jeremy's not on yet. Here's. And check my phone to see what's going on. You folks don't see my screen, right? Yeah, we can see it. Okay. Yep. Okay. Great. Great. Great. It's really confusing because there's a camera button that I unmuted, but I, which I don't know what it actually does. It's really weird. It's, it's, it looks like if it's sensing somebody else talking, it takes out my screen. But anyways, so Jeremy, I think you're going first. So I will stop sharing my screen and and I'll let you share your screen, Jeremy. I will mute myself. So Jeremy, you can go ahead and start when in four minutes or whatever. Yeah. Victor, will you, I'm going to share my screen real quick. Will you just bear, can everyone, I'm curious to know what you, what everyone else sees. I have, yeah. It's really confusing, Jeremy. And there's also a delay. So I'm, I'm, I have my phone open. So I'm streaming YouTube on my phone. And I think you're going to mute or some, yeah. So, so I go ahead and go ahead and share a screen, Jeremy. And I can see on my phone what the rest of the world sees. Okay. So I'm sharing my screen right now. For me, I just get the Google loading icon at the moment. And you've been sharing since quite some time now. Oh, wow. That's not good. Refresh. I see you screen Jeremy, but whenever somebody else talks, that person jumps in briefly, which is really weird. Okay. I think if everybody is not talking and the person presenting is talking, it should be fine in theory. So with three minutes, I would recommend that's what we do. Okay. But just to verify, I'm going to try screen sharing again. And can you just verify that you actually see the content? So what do you see right now? That's your call. I don't know. Explore. Okay. Good. Okay. That's great. That's great. Yeah. But as soon as anybody else talks, it's switched to their video, so let's be mindful with the muting. Okay. Trying to do the same. All right. I have 9 a.m. Pacific time on my end. So let's go ahead and get things kicked off. I'm super excited to get things kicked off for the kickoff for GitLab 11.5. We have a lot of amazing content to get through. So without further ado, let's jump right in. I'm going to go ahead and share my screen, and you should be able to see the kickoff document in front of me. So I'm Jeremy, the PM for Manage, and I'm going to talk briefly through the issues that we have planned for 11.5. The first one I'm excited to talk about is exploring cycle time relationship with ComDev Index. So currently we have a ComDev Index, which kind of gives you a high level indication of how engaged your instances with GitLab's sorted features. What we want to be able to do is we want to be able to show a clear relationship that as you get further invested in GitLab, you actually ship software faster. And provide instances with suggestions and highlights and opportunities of how they can invest deeper in GitLab and actually ship software faster. Super excited about this one. We're going to largely likely ship the full version of this in 11.6, but we're excited to get started on this and explore how we can actually show this relationship and instance to statistics. The other two issues that we're excited to dig into that we've announced in previous release kickoffs is registering and logging in and using smart cards or common access cards to actually authenticate with GitLab using a physical token and also sharing groups through groups, which is another permissions kind of level feature that we're really excited about. The other two features that I wanted to kind of mention quickly are improvements to how we built for GitLab. The first one is adding the subscription table to GitLab.com billing. So we can make billing and showing your GitLab.com subscription really, really clear, understandable and easy and show and be able to see that right in your billing section of your .com. We're going to take this table and we're going to also apply it to self-hosted as well to make license and kind of revamp and give the license area of the GitLab, your GitLab instance, a new look. This is going to make licensing very much easier to understand. It's going to make the experience a lot better for our customers and hopefully make both of these aspects of GitLab a lot more, a lot, improve the user experience for all of our users. But that's just the first half of what we got it announced. Andreas, over to you. I know you've got some really exciting user improvements as well. Awesome. Thank you, Jeremy, for that. Let me share my screen as well. So continuing with manage, I want to highlight the UX improvements that we are working on for LM.5 in the current release cycle. So starting with our top navigation, we currently plan to add a lot of new items which is currently living in our user menu to really lower the barrier what it takes to contribute to GitLab. So one idea that we have is we want to introduce a new WhatsApp section that just links to the release post of your current version. And because we know that the user menu is going more and more, we figured out that we have to do something there to improve that. So we kickstarted the UX research knowing that navigation is a very sensitive topic, but we are now confident to move forward with adding a new help icon right next to the user menu. So that's what you can see here in that detail. And that menu will host a couple of items that are either already existing like our help and the contribute to GitLab link plus additional items that we're going to add in the next few releases. So as I mentioned, the WhatsApp, what's new section is one of them that we are going to add in this release as well. Moving to our project overview UI. So in 11.3 we already added a iteration that improved a lot of areas there as well. At the same time, in typical GitLab fashion, we knew that this is only the first iteration and while we were working on that, we already covered a lot of areas that we want to improve as well. So this is what we're going to happen and work on for 11.5. You can see all the screens in the link issue. So this is one example how the UI looked like on just a very full-spec project. So I hope we improve the information structure and logical coping here even further. Next up are our dashboards. So from my perspective, previously our dashboards didn't receive much UI love. So they've been very looking the same. It's not very clear what is the focus area of that. So that's something I want to tackle with 11.5 as well. And we're starting with the activity dashboard plus the poaching list. So the main focus and those are also again UX research backup. We did surveys to figure out what are the most relevant information and introducing more differentiation in the UI. We are confident that we want to improve and that we have achieved to improve the focus and better visualization of the most important items there. So that's the visual design that we have for the activity dashboard and at the same time, we're going to work on improving the project list as well. So that's on the one side the dashboard view we have but there will also be a more condensed view and I can show you a quick example here. So this is the redesigned profile page that we will ship with 11.4 and one part that is available here is the quick review of your personal projects and for that we needed a more condensed version of that. So there will be two new components here. With that, I'm happy to move to Victor. Thanks, Andreas. So I'm sharing my screen now and you should be able to see the items that we have planned in the planned stage of DevOps. So really quickly, we have promote issue to Epic with quick action. So we've been iterating like mad with epics and roadmaps in the past year overall and so we want to make it really easy to reduce the friction using epics and one way to do that is just to convert an issue to an epic and so this is our very first iteration and we're going to achieve it using a quick action. So copying many of the fields from an issue and turning it into a new epic email notification for closing an epic. We just released a closing epics in 11.4 and that's really exciting and we wanted to make a lot of that functionality in parity with the rest of good lab including email notifications automatically navigating to the last board that you visited. So with issue boards, there's a lot of in a given board UI whether it's group boards or project boards you might see a lot of different boards if you're working in gilab we use many many boards so it'll be really really helpful so that you don't have to always scroll that long list and go back to the board you were previously at chances are you just want to go back to the board you previously looked at and so this will allow you to do so with zero work you just go back to the last board by clicking through the navigation with design of issue list and related issues and epic issues this is our very first step and it's a really simple iteration in particular as you see here what we did is we just flatten the so apologize clicking around here if you if I open this one really quickly you'll see that what we did it doesn't look that much but what we did is we're saving it some extra space so now it's just one row instead of two rows and so that allows us in the future to add a lot more elements so we're doing that for related issues and also for the issues within an epic as you see there and then the redesign comments and system activities sorry I missed one email notification for changing milestone and issue and merge request so this is a really big one especially for folks working at gilab whenever our issues change milestones because we we change really quickly and we want to reflect that to all users everybody on the public internet is able to see our latest plans but that also means that it's hard for people to keep up on what's changing and what are the issues that that are changing milestones from day to day and so this will help with that by sending an email notification the last couple are things that we've worked on in the past and unfortunately we didn't have time to finish the redesign of comments and system activities is something that we wanted to do earlier we couldn't find time and now we finally found time in 11.5 so we're excited so you can see this design the comment thread is revamped and it's going to look amazing in my opinion filter tab by comments or activity and issues and merge request that's something we talked about last iteration for 11.4 unfortunately it didn't make it so we're really really close and it should be merged relatively soon early in the 11.5 release similarly for the issue board card redesign again you see on the screen right now this has been ongoing work and we're excited to finish it up early in the 11.5 cycle James you're up Thanks Victor I'll share my screen quickly Alright we have quite a few exciting improvements coming in 11.5 and the first I'd like to share is preview and comments for the new batch comments feature that's being introduced in 11.4 it's really great so when you add multiple comments to your review and you click finish review you'll now be able to preview your comments and this will really streamline the batch commenting process and make comprehensive code reviews even easier and better in GitLab I'm very excited about that improvement coming to GitLab Premium Also we're continuing to iterate on approvers based on code owners so in 11.3 we introduced our first support for code owners and then in 11.4 we've extended that to automatically suggest approvers when you're creating an editing and merge request and in this next iteration we're just going to take it a step further and automatically assign the correct approvers based on the code owners that you've specified in your code owners file so that'll be a really great improvement for anyone who's using code owners files and that's coming to Starter Edition The next feature is really exciting and is much requested and it's about keeping email addresses private in GitLab we've had a community contribution that helps control which email address is used for commits when committing through the web interface and we're going to be extending that with further support for no reply email addresses so you'll be able to use a GitLab no reply email for your web commits and also your local commits which will keep your email address completely private when using GitLab Another big improvement coming to Community Edition is the ability to comment on any line in a merge request so this is using the same merge request interface that we already have but when you expand the diff to see more context around it you'll now be able to comment on unchanged lines as well and this will this is really a first step in what are a set of improvements coming to merge requests that are allowing you to comment on absolutely anything in the project, any file, any line but the first iteration is just any line in a changed file and finally for people who take advantage of the mirroring feature push mirroring will soon support SSH based mirroring using public key authentication not just username and password so great features and Andreas what are you working on with Geo? Thanks James, so we are constantly improving our Geo feature I want to quickly highlight the objectives that we have for LM.5 so we continuously work on rolling out our hash storage support to achieve general availability and I hope to achieve that in the next few months ideally by end of this year. On top of that we identified and are working on optimizing relevant SQL queries so we had a look what are the queries in the Geo context that we can optimize, they are not the fastest and we're going to work on these to bring up things to performance and on top of that we will put quite some effort into improving the Geo documentation to simplify setting up an administration of the Geo scenarios and all the features that Geo supports so all this will come to get a premium in LM.5 Jason, you're next up Hey everybody, let me share my screen here alright, so on the verify side I want to share to quickly go through. First is that we're adding parallel keyword to split your CI tests automatically so what that will do is allow you to set a parallelization factor for certain jobs particularly ones oriented around tests that will parallelize those jobs and run them for you so that will be a big performance improvement to teams that are doing a lot of testing and then we're also making an improvement to the way that our GitHub integration works so GitHub status checks will depend on there being a consistently named reference so we're adding the ability to configure that consistently named reference so that the GitHub status checks work and that's it for the verify team this release so I'll turn it over to Josh. Alright, thank you go ahead and share my screen here talk about the package management features that will be shipping. We're going to focus on how we can work to plan out how we can achieve hopefully MPM integration. So last release we shipped our first iteration of our Maven solution which was great and we were able to ship a great MPC where people could deploy and push packages to Maven and share it within their company and we want to move on to also now trying to look at MPM as well as the next item in the stack here so we're doing some work there, trying to figure out if we should build this, how it should look, how it should work, if we can perhaps integrate some of our solutions to go more quickly so we're going to do that work now and hopefully we can ship something but if not we'll be well set to have a good base foundation to go forward here and build out that MPM integration that we're looking for within GitLab. So with that we'll move on to the major item for our packaging team and we'll move on to back to Jason for release. Hey there. So let me share my screen again and we'll just quickly chat about these couple items here on the release side. So first is showing better information about the running deployment in the Merge request so there's a lot actually that goes into what we're going to show about what's being deployed where, to which environments and so on but one really cool feature that we're really excited about is that it's going to give you a link to the review app for the environment that was the previous one right now that link is hidden whenever a deployment is running so you just have to wait for the next environment to come up but that other environment is still up and so we'll allow you to go there and still see what was there for the last deploy which is a very handy feature. And then the other thing that we're doing is making it so that on that same page, the review app if you're working on an HTML site or a site that uses templates or anything like that it will offer to link you directly to the pages that change so if you updated a sub page or a blog post somewhere on your site, when you click on that review app link it'll take you directly to the blog post that you changed. So another one that we're really excited about that's going to make the feature a lot nicer to use. So over to you Daniel. Thank you Jason. Let me go ahead and share my screen. Okay so for 11.5 the configure team is excited to begin work on group level Kubernetes clusters. This will give users the option to configure a single cluster which they can which then can be leveraged across all the projects associated with that particular group. So basically on the group screen we're aimed to show a dedicated section for your clusters and then at your project you will be able to see as you do now all the clusters that are associated with it and you will be able to tell if it's group cluster or project level cluster. Next we're going to work on the ability to configure auto-develops deployed applications with secrets that are not part of your repo. So for example your application running on the Kubernetes cluster may need a secret or a token to access a particular API or third-party service. So for security purposes we don't want to store the secret in the repo and in short this will allow you to configure those secrets to be used on your applications running on your Kubernetes cluster. And finally we are working on extending our Kubernetes RBAC implementation to create service accounts that are restricted only to a project's namespace. So as you know as part of 11.4 we're rolling out RBAC's report for Kubernetes and instead of having a limited service account to manage the cluster the service account will be implemented per project. So the service account will have access to that namespace only and thus will be more secure. And that does it for the configure team. Josh, on to you. Alright, thanks Daniel. Let me open ahead back and share things here. Alright, so monitoring team we have a couple of episodes that we want to achieve here this release. The first one is you want to shift the sort of first iteration of our trace integration and we're going to figure for our tracing solution. So we want to be able to offer users an easy way to view tracing within GitLab and be able to start to kind of have an integrated solution for that story as well. Again probably a small iteration going forward here and we'll let you try to embed some of the UI within the workflow of GitLab and that will be an easy way to sort of make it easier for folks to access that content without having to open a new tab or open a bookmark or things like that. So again hopefully here to try and make things a little easier for our users on the monitoring side. We're also going to try to finish up two items that we unfortunately weren't able to ship last release. That's the operations home page and the support for the new metrics from the new engine next to Ingress. So we'll go ahead and wrap those up this release and get them out to the door. We got quite close on both of these but unfortunately just couldn't quite get them done in the last release. And finally we'll also be addressing Firefox support for our metrics dashboard. Turns out there's an SVG rendering issue in Firefox and we'll be working around that to have this be able to be seen with folks who prefer to use that particular Firefox browser. Let's go to the main agenda items there with the kind of marquee item here being the Tracy and MeC and then also the marquee item being the operations home page which will be quite exciting to actually get out there and make it available for folks to try. With that I'll pass over to Fabio to talk about what's new in security. Thank you, Josh. Let's see what's new in security in the security in actually in 11.5. So let's see the kickoff dock and the first item I want to talk about is the group level security dashboard. This is something very important that the team is working. If you attended the previous meeting you may remember that it was announced in 11.4 but that was quite hard and we found some blockers during our development and so we are not able to ship it in 11.4 even if a lot of code has been merged already into the master branch. So in 11.5 we will continue this effort and we are going to finish the story and ship the very first iteration on the dashboard. Later releases will contain other improvements to the dashboard. Just remember for people that are not confident with this dashboard, the group level dashboard is the very first feature to allow security teams and director of security to jump into things that have to be considered for securing their project. So it's not intended mainly for developers like all the other features are, but we want to focus on this new persona. You can see the screenshot that is the mockup that we are using to implement the dashboard. There are counters at the top to have a very high level overview on security of the group and then we have the list of issues ordered by severity. So when you jump into the board and you are a security specialist, you want to know what is most important to work on first, you can pick up the first item in the list. From this list obviously you can create an issue, you can dismiss the item, you can see more information. The second item we want to talk about is a suggest fixer for dependency scanning for the gymnasium tool. This is very important because this is the very first step to implement auto-remediate. That is our way to provide an automatic fixer for security vulnerability in your code. This first step is about getting which is the best version to update your code if the version you are using actually is vulnerable to something. Let's assume that you are using version one and version one is part of that is vulnerable to something the system is able to know given the data that we have in our databases that version three is the good version that is still compatible with version one and also not vulnerable and so it will provide this information in the issue that you can create from the vulnerability giving you a very important suggestion about how to fix your code. In the future this information will be used to automatically create actually the fix so changing the code but this is for a later iteration. The security is also working on a lot of other backstage things to remove the requirements and unlock all the other features we want to work on. So you are more than welcome to go to the board you can find linked in the document the other items that you are working on. And now back to you Josh for distribution. Thank you Fabio. To wrap things up for today we can talk about what's coming with distribution. This team is responsible for what we deploy package into the customers and how you maintain install and take care of GitLab not just our customers but also our sales with GitLab.com and the same software and packages for that as well. So we have some exciting improvements here coming from the distribution team. The first one is that we will be working to add support for encrypting data in transit for Gitaly and so if you are leveraging the Gitaly service to go ahead and power your Git storage that chapter will now be secured as it can be communicated across different nodes in the GitLab cluster. So some exciting improvements there to improve security for our Gitaly solution. We have also made some changes in the previous release that improved some of the permissions and some of the configuration files that were set up as part of our omnibus distribution and so we made some improvements to further restrict the permissions of those but we ended up funding some customers who had some interesting configuration options around groups in particular and how they were handling the user account that was responsible for our assigned to this and then also what group it was in and so we ended up I think having some issues with those deployments and so we will go ahead and do in their past to better improve the handling for specific types of group memberships configurations as far as the power permissions go. We will also be working on changing the Postgres directory naming. What we want to do here is that when we change the Postgres version we can avoid a restart if we can essentially change the directory naming from major minor and I think the dot release to now just major minor for now. So for example it will be like 9.6 for example for Postgres and that way if we bump the minor version or the past version we can still do so without having a day based restart event. So this will help folks using omnibus to essentially be able to accept more queries from GitLab and we can roll the version of Postgres without requiring restarts of the database which would be nice for folks again running GitLab in a self managed way. We will also be working to refresh our GKE marketplace deployment so that's the deployment you can see on the Kubernetes marketplace of GCP and so that's very exciting for us. One note is that it does contain some confidential information in there so that is a GitLab only issue but do note that we look to be at the deployment option to have the latest version of GitLab and also to improve the lifecycle management features once you have it deployed so some great improvements on that mechanism of running GitLab. And finally for our GitLab Helm chart which is the way you deploy GitLab on Kubernetes you can also we are also working to improve documentation as well as ensure support for both EKS and OpenShift. It does work on EKS today but our documentation is a little rough and so we are looking to polish that up and then we are looking to create the first version of documentation for deploying our GitLab Helm chart on OpenShift and so that will be great for customers who are looking to leverage that platform. We will have a good tutorial on how to so they can save time and avoid potentially bumping into some things that weren't perhaps documented in the best way possible. So great improvements there to documentation for our GitLab Helm chart. And with that I have come to the end of what we are planning to do here for 11.5. Thank you so much for attending our live stream. As you can see we have a bunch of really amazing features here. I am super excited for this release and again we will see you next month for our kickoff for 11.6. Thank you so much and have a great rest of your day.