 Welcome to my lightning talk about experiments. We run with services. And a very quick, very short story of what we can do with services beyond contributing to open source projects. So I want to share a story about creating services in a world of software as a service. And what does it mean for open source tooling? Today, I'm going to be talking about Paribolos on Operate First, which is something we are trying to shape and build as something called open service. So what exactly does that mean to have an open service? When you think of a current ecosystem in open source, people contribute to tools, to software code bases, and all these bits and pieces that make up successful application. But when you want to contribute beyond that and see how applications are actually run and executed and the lifecycle is taken care of, there's not much ways to contribute to that. So we're trying to change that through experiments like this one. This is a story of Paribolos. Exactly three years ago on KubeCon 2019, there was this talk called Paribolos, how Kubernetes uses GitOps to manage GitHub communities at scale. This is a, then it was a brand new tool called Paribolos. Now it's part of the Kubernetes community tooling through Pro and through other CI means. And it allows you to manage GitHub organizations as a code. We thought this is a very neat idea. So how does that work? You get a config file that you can do changes to. It's a declarative way to describe your GitHub organization, right? So you can add members. You can add create repositories. You can create teams. And what's more important, people can do that. You are basically crowdsourcing the GitHub organization management. So you don't need to hunt down your GitHub organization admin just to add a member to it. They can create a pull request. You can review it. And once merged, it gets applied to GitHub. So we thought that this is a neat idea and that we want to use that in our organization. So how would you do that? Traditionally, normally, you would start with taking the tool, taking either a binary version of it or a container as the version of it, pull it into your CI, and let the CI run on your repository where you have version controlled this configuration file. This is a normal workflow that probably most of us would use. Well, that at some point becomes a problem when you're managing multiple organizations. You need to set this thing up for every organization. You need to maintain and upgrade these parables applications across all these organizations, maybe in the same configuration, and so on and so on. And then it becomes a challenge. And then it becomes a challenge that you need to take care of lifecycle of all those CI pipelines and manage it all similarly, hopefully the same. But every organization is a bit different. And usually, these code bases diverge. So how to solve that? Well, nowadays, a trendy thing to do, let's make it a service, right? That's what everybody does with everything currently in the SaaS ecosystem. Let's create a service that is managing all of these organizations together. We thought, OK, let's do that. So we created this GitHub application that you can sign up for, install into an organization, and let it manage your organization through your configuration file inside your organization, which is a normal thing that modern application would use, create a service out of your tools, out of things that you use in a decentralized fashion, and unify it into a service. But we thought, can we make more out of it? How can we get more value out of a service? So we decided to make it open, make it a collaborative way. Let's challenge. We decided to challenge ourselves and collaboratively manage this service as a community. So we found a community where we can do so for various services, not just for our little, tiny, marginal application that takes care of a single use case. So we joined this Operate First community, which is a community supported by Red Hat. And its focus is exactly this. Find a common ground, find a place, a meeting spot where we can talk about how ops should be done, how SRE work should be done, how to handle services collaboratively, and how to transparently contribute to something which is running as a managed offering. So we joined this community. And we used it to share best practices, define best practices for managed services. And to also host our workload because Operate First community has a community cloud offering that is publicly available for anybody to join and use. And it's basically free hardware that you can jump in and use and deploy your workloads onto. So we decided that this is the best place where we can run our service. And by that, I'm going to conclude this short story. You can join us in Operate First. You can join us in the Privilege application. We would welcome any contributions to either of those things, collaborative cloud management, Privilege is an application. Install it, use it. Thank you very much.