 Hello, and welcome, everyone. It's so great to be in Berlin again. I met a former colleague, a lot of friends. I was leading here technologies prior to joining Red Hat, the developer team, and so many good friends. And I've spoken in this event last in 2019, if memory serves right. So it's great to be back in Berlin and see all of you. So thanks for joining. My name is Mithu Indar, and I lead the developer business unit at Red Hat. I got the funnest job in Red Hat. I love it. There are two components to this job. One of them is running the program, and Ignacio is my right-hand man, whom I depend on. This whole event was coordinated by Ignacio, at least the Red Hat presence in this event, and then building products, building products like Portman Desktop, like Red Hat Developer Hub, like Red Hat Sandbox, and making the developer experience better for each one of those. That's what this team at Red Hat does. We are over 400 people within the business unit, and that includes engineering, product management, everyone. And all of us are working with one goal, make developer lives better when they use Red Hat products. And why does developer experience matter so much? How many of you, by raise of hands or even putting your fedoras on that you have, tell us how many of you here are developers? Wow, OK. So that's pretty much all of you here are developers. And you know, when you use those products, when you use tools, how important it is to minimize the friction, how to easily get started, how you can be more productive when you use a platform, when you use a tool. These days, you're inundated with so many different things. I started coding 25, 26 years ago, and I started actually writing programs for GWBasic. And from there, you know, started using Fortran, Pascal, Kobal. And I still remember the first time after using all those languages, when I wrote my first Windows application using a Windows SDK, it was revolutionary. The whole concept of an SDK was fascinating. And ever since, you know, everybody now knows how SDKs change our lives. But, you know, we have a word quite a bit, right? But measuring that developer productivity from one tool to the next, from one release to the next, you know, it's basically trying to make it easier, make it faster, make it simpler for developers. How many of you have coded before IntelliSense? Before even IntelliSense was there. I think Visual Studio 2000, I think DotNet. Visual Studio DotNet was the first one, first version which had IntelliSense, you know. And now, you know, co-pilot is easily integrated and easily available and, you know, it's changing, right? It's becoming more and more efficient for us to use the tools easier. And at the same time, you know, it is inherently becoming very complex, you know. Today as developers, we need to make sure that all the applications are secure, right? Our code is compliant with one of the many compliances that we need to follow. And, you know, so measuring that whole developer productivity is much more complex. And just to, you know, tell you why it is important that we need to measure developer productivity is because study after study after study has shown that companies which have developer-centric cultures, companies where developers are happy and thriving have a bottom line, lead to a better bottom line for the company. In this case, four times more, you know, than what their competitors who don't care about developer experience or developer happiness is. And again, this report here, the McKinsey report is fascinating. If you get a chance, you know, definitely download and read it at leisure. It's a great, it's a great report and insightful report. Not only are happier employees more productive, but they also like to stay in a company which cares about their developers. So, you know, essentially developer experience, developer centricity leads to developer happiness, which leads to more productivity, which leads to more revenue. It's as simple as that, you know, you've got to make a few leaves, that's it. And in making sure that, you know, we are building the products for developers in the right way. We are making it effective for developers. We at Red Hat, you know, follow three key aspects. And then we were really surprised when, you know, the research report from Microsoft researchers and University of Victoria published, you know, and they said, hey, they categorized over 25 different factors that go into making developer experience and release this framework, which is very sort of easy to use, more practical to apply within a company. And it boils down to three things. The first thing is reducing cognitive load. And I'll click on each of these in detail. The second one is optimizing for the flow state and the last one is establishing a strong feedback loop. What it essentially means is, hey, help get developers started, you know, easily without any friction. Once they start, help them, you know, to be in the flow, help them to write their applications, develop their applications seamlessly, you know. And lastly, help them to deploy those applications, make it easier and, you know, get into, help them publish the application and get it to their customers, increase the value stream. That's what those three things is. And to explain each one of these concepts, I thought what better an analogy to use than our daily lives, right? Like many of you here, my favorite pastime or my second most favorite pastime is binge watching a good show on TV. And like all of you, you know, I've had many, many remote controls over the years, but one remote control stood out for me for a long time. I had, you know, I had the same remote control for over three or four years and that is the Logitech Harmony 650 remote control. Anybody has that here? Anybody used it? Maybe it's a U.S. thing, I don't know. But it was a fantastic remote, you know. It had, it pretty much had a lot of, you know, features and functionality. It came with a 22-page user manual, by the way, if you're interested, and it had six programmable buttons and every function on the TV could be hard, had a hard function or a hard button on the remote itself. You know, I loved it for about three or four years, but there were only five functions that I used in it. I never went to, you know, discover all the other capabilities of that remote. You know, because whenever I saw that 22-page user manual, it was a little inundating to me. And then about six months ago, my wife plugged in Apple TV because she wanted to get the pictures onto the TV from the phone in an easy way. So that when we had guests or friends or, you know, whoever comes to the house, we could share the pictures and put them in a loop and, you know, make that integration more seamless. And when she did that, I noticed that, you know, that remote controller, new remote control had made it into our family. I saw that and I'm like, huh, this is such a small remote. It's a, you know, I don't know if I could use it, you know, it definitely didn't look like my Logitech there, right? It looked very puny to say the least. But 10, maybe 12 minutes after having this remote, I was in love with it. The way it felt in my hand, the weight of the remote, the easy functionality, how intuitive it was, you know, it was fantastic. And it did every function that the Logitech remote did in a more seamless way. You know, it also had the natural user interface with the speak to, you know, change HDMI channels, whatnot, other functions on the TV. It was just fantastic. And that is what reducing cognitive load is, right? Like look at that remote. I mean, the simplicity of that remote is just fascinating. They don't even go to, you know, write what each of those buttons are because we all know what each of those buttons are. And if you don't know, you'll figure it out in the first two minutes of using that remote, right? So our developer tools, our developer products that we use are somewhere stuck in the Logitech remote world, right? We inundate our developers with, you know, complexity. So when, especially when you think about, you know, the entire developer workflow loop from, you know, from onboarding onto a new project or getting started writing your applications to publishing your applications to monitoring your applications, everything becomes so complex, you know? What we at Red Hat are doing is trying to minimize that cognitive load across each one of those phases. And particularly, I'll talk about each one of those phases and tell you how we are helping developers here. From an onboarding perspective, you know, think about the first time you started your project or you joined a new company, you joined a new team and how complex it was, what all you had to set up, you know, download the different pieces, set your machine, set your environment, get access to the Git repo, like it is inundated with complexity, right? And to reduce all of that complexity, make it more streamlined, make it more efficient for developers to be onboarded, we launched a product called as Red Hat Developer Hub. And this Red Hat Developer Hub is based on the successful upstream CNCF project called as Backstage. And we are using Backstage and we built the Developer Hub, which is essentially an internal developer portal and a platform that has opinionated paths, but is also flexible. It allows you to make it your own. It has a rich ecosystem of tools and products and plugins that you can replace or use the opinionated paths from within the tool itself or the platform itself. It offers us a single pane of glass for everyone in the company. And it allows engineers to be more productive and use golden paths and guard rails to get started on application development and then start publishing and deploying to the endpoints that they're looking at. But let me actually show you this in action instead of talking more. Natale, who leads developer advocacy at Red Hat, is going to show you this. And those of you standing in the back, there are some seats here. Please come join us and you can sit here if you wish to. All right, Natale. Thank you, Mithun. Please come along because here today we have only live demos. I'm really happy to be here in the city in Berlin, super cool city. And I love confidence like this with people passionate about technology like you. Me and my team are here to deliver some session with all live demos. So with all the consequence, of course. So let's start this. And Mithun, I love your analogy about the remote. I didn't know there was so much expertise in remote, but this is very cool to understand how it's important to remove friction and how it's important user experience and developer experience. And I'm gonna show you a demo of Developer Hub simulating a developer doing an onboarding on a real project where we created this sample organization on GitHub called the Winterbin Inc. This company produces software games. It's a software company producing games and those games are toward generating green electricity. We'll play this game today or today in the stage as a live demo for this keynote. But let me show you how as a developer I can get started on project at ease without not losing too much time on setting up environment, finding documentation. Sometimes documentation are people, but people also live and then we need to figure out how we can do that. So I'm using this sample organization. I'm in those developers here and listed here with some of the team as well. And I want to get started. My first point of start is this one is Red Hat Developer Hub. As Mithun mentioned, this is Red Hat products levered on top of Backstage. Backstage is an open source and CNCF project for implementing tenant developer platform. It's really cool because it's a standard way to define how to get onboarded into project. So the first thing you have when you have your developer hub is of course is an on-page with the February tool. You can do a lot to get started, cluster connection or tooling. But I want to show you that as a first onboarding, let's imagine it's the first day of work. And the first thing you want to do is understanding what you can do in the company. So there's some learning path. You can configure on learning some of the technology. Today we're deploying a game developed on Java which is using Kafka for messaging in Finishpan for as a distributed caching. So first you want to learn some of the topic and then you want to create, you want to start developing this game. So how can you do with your GitHub account? I'm logged in in this system and I can pick one of the available template. This is an important concept. The golden part template has a way to get started into project. You can set up a skeleton of your project with your, you can create some repositories. You can create some CI CD automation. My colleague and Peter after this session will show you in detail how to use it. But here I want to show you that I created this sample template which is the Java template to deploy the game. And let me show you real quickly what is a template under the hood. This is the definition of how backstage define a template. Essentially it's a YAML file where you can say, hey, this is a template generating some Java project. And those are the parameter you can inject into the template. This will auto generate a form. So you can remove the friction to your developer, to the developers, right? To get started in the project, connect to some cluster. You can really develop this part and this will convert into a sequence of form. For instance, we are part of the organization. Let's go into putting other setting. We are targeting some Kubernetes cluster. In this case is an OpenShift cluster. We want to work in some namespace. Kubernetes namespace, let me create this namespace. The owner is my GitHub user and I'm fulfilling other settings. Some can be pre-felt. So I'm using a one-distance plate generating a container image. And I want to store this container image inside the cluster. You can also connect to other registry like Kuei.io or Docker app, whatever. So easy way to get started. When you hit the create button, what developer hub is doing is creating some repository in the organization you connect and creating a skeleton of the project. And I want to show you in detail because this is really important to understand how this tool is removing friction. So I have an overview of the whole project. Like this is connected to GitHub in this case but can be another Git server. So you have an overview on the GitHub pull request, any issue open. Of course the project just started so we don't have any. And of course you have the evidence of the source code you generate. So if you open the WinTruppin organization again we go to the repository. As you can see there are two new repo. One is the app repo. So as a developer I want to start contributing to this game that we will play together to generate some green energy. And so here's the documentation, right? But I have scaffolded some projects and the code is there. So I can really get started in developing something. And also there's a convenient GitOps repository. This template is also set up to automate everything. This means that can automate the container image creation thanks to a series of plugins that also read that support. And I want to show you what are those plugins. The CI plugin is a plugin that use Tecton which is an open source software. Kubernetes native to create pipeline in the cluster. So this is now creating a Tecton pipeline creating the container image and pushing this content image into the registry. There's another plugin for deploying application which is the ArgosyD plugin. ArgosyD is a popular open source software for implementing GitOps. So this is the GitOps plugins also supported in developer app. And it's part of the ecosystem. So as you can see, I've scaffolded some repository that I can start coding. I scaffolded some project that is evolving and creating something in the system. And also I'm connected to the Kubernetes cluster, my target Kubernetes cluster. I have an evidence of what is going on. I have some pods running. This is also cool to remove friction to the developer. You don't have to be a Kubernetes hacker, right? To get started. This template system really help you get started into project with some automatic automation but also you have this nice dependency graph with the relations. And what is happening under the hood is that you are connected to the target cluster. All those links I'm showing you here are auto generated. So once you install developer hub and you set up the templates, this mechanism automatically connect you to the cluster. So I'm using how my Kubernetes cluster, in this case, this is an OpenShift cluster. What you see here is the OpenShift web console which is a web console showing you all the settings. And there's also a topology here where I can show you that the template not only is deploying my Java application but also is deploying the dependencies. This Java app needs Kafka for the messaging. When you're gonna play the game and we will do it later, you're gonna send Kafka messages to the backend from your mobile phone. And also use that distributed cache for doing that. Where you can define this, you can define in the scaffolder module. So the template is using some kind of a source code where you can define all those settings in the GitOps repository. So this was how to get started and scaffolding everything. And last but not least, if you are familiar with Argo CD, this is generating also some Argo CD deployment. So you can see an evidence that is deploying your application, is deploying on the component. This is fully automated and I didn't have to set up anything. It was already done. And if you don't want to add to enter in the cluster, there's also this nice topology view, which is another plugin that is providing you a view of what is going deployed into the cluster. So this is going on. Once this is ready, the app has been deployed and we can get started. But before we close this demo, this first demo, I want to show you that you have the code, you can also start coding. What about you code directly from here? If you don't want to spend time in setting up your environment, you can use OpenShift Dev Spaces, which is a product built on top on Eclipse Jet, an open source software for implementing in browser IDE. Eclipse Jet and Dev Spaces, they mount your favorite IDE that you can use IntelliJ or Visual Studio Code. In this case, I'm using Visual Studio Code. And when you click, this is open a web interview of Visual Studio Code with the search code and you can open a terminal and run your command. You can run some run configuration. You can open a terminal and run your settings here. This is a Java app. I want to package my app, so I'm running my own package. This is all configured automatically. And this part is part of the automation. So that's really cool. And maybe that doesn't give me the time to have the deployment up and running. Yes, so my app is deployed to the cluster and this is the game. I want to show you this is the front end of the game. So you're going to play this game from your mobile app. But this is the first part of our series of demo. And as you can see, we were able to scaffold that project from scratch and being able to start contributing from the first minute. Back to you. Thank you, Natale. So what you saw here is how easy it was for a brand new employee to be onboarded, have guardrails, and get access to the right systems and get them contributing to the right project and get published to the server or the Kubernetes cluster that we were looking at. In our case, it was OpenShift. And this is available for you to try today. It's in a private preview, but just send us an email and then we will make sure that you're getting it. This is called Red Hat Developer Hub. And as we move forward, we just showed you how we have removed friction on the onboarding side. The second one is improving flow state. And what is flow state? Flow state is essentially helping developers be in the moment, be in the zone. You've all heard developers say, oh, I'm in the zone. I'm in the moment. I'm being more productive. What they essentially mean is they finally have a chance to concentrate and code without any distractions, without any interruptions. Later today in the second session or in the third session of the day, you will see my colleague talk about how developers have less than 55 minutes of productive coding time a day. And it is less than four hours every week is how productive time is available for developers. The rest of the time they spend in setting up the environment, getting caught in the processes, so on and so forth. And again, to explain flow state, I wanna go back to the analogy of entertainment. You know, we all take binge watching for granted the way Netflix changed user behavior or viewer behavior, I should say, for granted. But what Netflix did is amazing. They said, hey, we are gonna start producing shows and these shows will be catered towards the user, not towards the advertiser, not towards TV networks, but towards the viewer. You know, and how can we give these viewers an optimal viewing experience, right? So they said when we produce a season, we are gonna release all the shows because let the viewer decide whether they want to watch all the seasons in one day, one night, or one week, or they want to spread it out and watch it over three months, right? And that in and itself was a massive change in viewer loyalty and viewer behavior change that Netflix did, but they didn't stop there. They said, where else are users or viewers getting frustrated? You know, why should we see the credits when the show is done? Maybe you don't wanna watch the credits. So they said, if you're interested, there is a button, but by default, when the episode ends, in five seconds, it takes you to the next episode, but they went one step further again, right? In removing that user friction because they were deliberately thinking about good design and viewership experience. They said, oh, you don't wanna watch even the intro when the next episode starts, skip intro. You know, they gave you that option. You can skip the intro and go where you left off in the previous episode. I think that's fascinating in how Netflix, you know, achieved that momentous sort of behavior leap from traditional cable network shows. And in a very similar way, you know, for Innerloop, we want to get developers into that flow state. And your Innerloop is where developers are actually building applications, coding their applications, testing their applications, using their favorite IDE. How can we keep them completely in the loop, in the flow, you know, and for that, we, I'm gonna use the example of another product. In this case, it's a complete upstream product called as Podman desktop to help container development and application lifecycle management be more integrated and more completely in-tune and help developers be in the loop. How many of you have used Podman or are using Podman here? Okay, a few hands. So hopefully this next demo that Natale will do will convince you to give it a spin and give it a shot. Again, it's free of cost and you can get started. Natale, on to you. Pleasure to keep doing our live demos and now we're getting into the, another moment of our developer lifecycle where, you know, we scaffolded all our project. This is cool. We have all ready. What about we need to do some change and we don't want to use that, you know, in browser IDE we just, you know, what we do, we just go to our repository and we just clone our already created repository locally. So we just copy here and we already did it for saving time. And essentially what we do, we open our favorite IDE. I'm using Visual Studio Code, it can be whatever. We do our actual, you know, I think we need to change the code and do some setting like packaging the application. This project is using an open source Java framework called Quarkus, which is optimized for container development and Kubernetes deployment. And it's really optimized also for resource consumption and also for speeding up application startup. And the game, as you can see, is Java code and it's used also some connection to Kafka and some cache with InfiniSpan. But let's say now the local development is fine. Let's think I need to containerize this app because I need to ship the container somewhere. I need to give the container to a colleague, whatever. So first thing I do, you know, I write a Docker file or somebody else write a Docker file for me. This is a really simple Docker file. Start from a base image. This is using universal base image nine and open JDK 17. Then I copy my artifact that I just created and I create my container image. So how do I get that at ease to application container development? Well, Podman desktop is the right tool for doing that. And Podman desktop is an open source software which is based on the Podman engine which is an open source container engine which is focusing on security for running rootless container. Demolus is demo less approach. So it's really focusing on security and speed. When you download Podman desktop for Mac Windows Linux I'm using it in my Fedora workstation. You can also connect it to a rich set of extension or plugins you can either deploy to your local Kubernetes cluster with OpenShift local or kind or to a remote cluster. I'm using OpenShift developer sandbox I'll show you in a moment. So, and the other cool thing of Podman desktop it can nicely connect to your favorite registry. I already connected to Red Hat Wave which is a public container registry but you can connect to Docker Hub or GitHub or any of your favorite registry. So let's start containerize our app. You have a list of available container image but you can also build your own. And it's really easy from your clone repository you just started the Docker file that we've seen before and simple as that you define how is the container image. I'm gonna tag it with the name I'm gonna use to push to my registry. So this is gonna be Kinoa, WinTurpin, latest tag. And simple as that I'm gonna just build the container. This takes some while it depends on how much the container is made but once you build it straight really easy you can go to the list of images that you create and you can start this container. You can either inject some settings like environment variable, networking and security. By default this is a secure tool, open source tool but you can also toggle some of those security settings. Those are settings that you can inject as you want. Let's say you wanna use default port to default environment variable. It's really easy to start the container. It's gonna be available in the list of the container and where you can see of course logs. It looks like it's super small. You're becoming blind but don't worry. Just to go into the flow and you can access the terminal and finally you can access the container local. So I'm using the container locally is the same game we deployed with the developer have on some cluster. Now it's running locally and I think it's ready to be deployed somewhere. If you need any development environment that there's this convenient environment that called developer sandbox. My colleague Marcus is gonna show you it in the while after in the session how it works but essentially is a free environment where you get an access to this OpenShift cluster and this is again the OpenShift web console that you can have start and you can have to start deploying your application. How you deploy application with a frictionless approach. Well, if you don't want to spend time on learning too much Kubernetes so you want an easy way to do that. From Podman desktop you can just deploy your app by clicking in this little rocket icon. This is gonna auto generate some YAML file describing your application and then it's gonna deploy into the target cluster. So as you can see here this is just deploying the container image that we were building. And if your container image is pushed to a remote registry I have already did it before to save time but you can either do from Podman back. So if it's already pushed to a remote registry then your container image that your pod is deployed into this remote Kubernetes cluster. So another way to deploy the same app but from the inner loop as a developer at Geeks. Back to you Mithu. Thank you Natale. And you guys will be able to play this game in just a bit. But what do you saw here is essentially Podman desktop is that really optimized tool to help developers be in the flow state, right? Where it helps developers maximize and maximize the container development application lifecycle management in a more seamless way. And that brings me to the last part of today's talk which is establishing a strong feedback loop. Going to the same parlance of entertainment and television shows, feedback loop essentially means production, right? Like how is Netflix able to produce so many hit shows that are popular around the world? Well, most cable networks in their lifetimes have produced two maybe three if they're lucky, good shows. That's because Netflix is able to sort of test how the show is resonating across the world. They're able to get data, they're able to figure it out and then try to replicate it. The Casa La Casa de Papel. Yeah, La Casa de Papel. That's the one that's really famous in Europe. And now they're trying to do that in the US and other parts of the world, Squid Game. It was super popular in Korea but they replicated that for the rest of the world. But they're able to get that viewer data, that viewer analytics, how many eyeballs are seeing, where are they stopping? Where are they xing out? So on and so forth. Bring the data into the application and then take it from there. Now, how can we bring that sort of feedback, feedback loop into the software development lifecycle? Essentially, this is where your outer loop comes into picture, right? Once your application is developed and it's getting ready to be published, how do you, can you secure it? Can you make sure it's compliant and you're building, making it compliant, making it secure, and now you're ready to publish it? That entire software delivery time, how can you shorten that as much as possible and increase the deployment time so that people, enterprises can, you're supporting enterprises to have that iterative development. That is where we are helping companies with the feedback loop. And for this, we have a product called as Red Hat Trusted Software Supply Chain that we just announced in our user summit earlier this year in May. And again, this is in private preview, but this allows you to help build applications, deploy applications more securely in a more seamless way. Natale, quick demo or we go into the game itself? Well, we're getting into the end. So I just want to show you that for we're finally playing this game together. So thank you for staying with us until the end. I just want to show me to that, again, security should be put in place from the beginning. So we want to deploy this app in a secure way and this product you just mentioned helped us to doing that. So we already done to save time so we can start the game. But essentially when you use Red Hat Trusted Application Pipeline, you can start from the summer repository like the one we just created. And this will create a secure pipeline similarly to what we've seen before, but this is more focused on security. And it has many gates, like not only it build the containers, but also inspect the image. It performs some scan with a clay. So it's able to scan your container image and then run and give you some score, some vulnerability list. Then it's the performance scan with an anti-virus. Analyze the software bill of materials. So it's a complete set and checks before you deploy the app. It can connect to your existing cluster. I connected to the cluster and now Mitun is it's time to play the game deployed in secure way with this system. I want to show you that the tap deploy the app here. Here I put also all the dependencies, but now it's time to play the app. So I kindly ask you to use your phone to finally consume the app. We scaffolded at the beginning with developer app that we built with Podman desktop that we deployed securely with a trusted application pipeline. You should see now a rotating car. This means that you are waiting for the game to start. The system assign you automatically in two teams. So who is team one? Who is team two? Great, so let's see what is happening. You have seen the front end of the game. I'm gonna open the back end of the game. So this is our game we just deployed and essentially we can open also from the cluster itself. So you see that one and I'm gonna access the dashboard to start the game. I see some of you in team one and team two it looks like we have a 37, team one, 37, team two. So equally distributed. When I'm hitting the play button, what happens? You're gonna see a windmill in your phone and you have to generate green energy by tapping your phone to move the car. I want to say that if you don't play you are affecting the score of the whole team. And for those of you that wins we have some cool gadget to give away. So please don't miss this opportunity to run this great game. Three, two, one, you should see a windmill and please start tapping, tap, tap, tap as fast as you can. Come on team one, we can do better. We can do definitely better. Don't destroy your phone by the way, because it's always... That's a close race. Come on, come on, come on. Team one, team one is getting some gate. Oh! Congratulations to team one, congratulations. So again, that was great. We have a leader board and we have also the team one that won. We're gonna... I have the 45, only 45, but who is in the first tree of this rank? Who is bad in it? Wait, you win some cool swag. Come to that booth and with your phone and we'll give you the swag. Who is Barbero? Barbero, congratulations. Come to the booth and we'll give you the swag. Who is Vietzke? Oh, I mean, no, you know. Who is Hicklin? Hicklin, congratulations. You won the swag. Come to the booth and we'll give you this one. So thank you all for playing this cool game with us. It was just an example to show how the developer experience can also bring joy to the users in the complete feedback. So in recap, I wanna say that an ideal developer experience is one which reduces developer toil, whether it is in the onboarding process, whether it is in the inner loop or in the outer loop and increases developer joy. You know, it comes down to those two things at the end of the day. And again, we think about developer experience at Red Hat beyond just product. We also have a lot of... We also have a great program with a lot of content and a lot of events that we go and definitely, you know, this is one of those events but we do over 140 events across the world and a lot of content, a lot of eBooks, et cetera, that we have which will help developers be up to date. So if you're not already part of the developer program, sign up. There's also the QR codes behind the chairs. You can scan those and sign up and you'll be in the loop and informed about all the latest and greatest things that we are doing as a company and as a team. And additionally, we also have a lot of good eBooks that we give out. And tomorrow we have the authors here to sign those books, so be there. All the products that we showed today are available for you to try, whether it is the Developer Hub or the Portman Desktop or Red Hat Trusted Software Supply Chain. For those products which are in private preview, send us a mail and we'll definitely get you in. But that's it. Thank you, stick around for the rest of the day for more in-depth sessions on the products that we showed. Thanks again. Thank you. Stay. Okay. Okay. We are going to make the change in the microphone. In the meantime, there are a couple of questions coming from the audience. By the way, you can submit your questions if you want. There is the app and you can submit your questions in real time. So. The first question is, maybe, yeah. The first question is, does the platform support GitLab? So if you mean Developer Hub, yes. It supports GitLab and you can use GitLab but likewise, we did more GitHub in this case. So our plan is to support major Git systems like GitLab, Bitbucket, and GitHub. And everyone else. Yeah, and everyone else. The other question is, does it support creating services inside a Monorepo? A Monorepo, which service? What do you mean? Who made the question? Whoever had that question, can you create more services and run the services from within Developer Hub? Yes, in short, you can. But let's meet on the side and then we can go in-depth and clarify your question and then we can answer that. Thank you. Right now, Hans Peter here will talk more in-depth about Developer Hub. So thanks everyone. Thank you so much.