 Hello and welcome to Cloud Native Glossary, trusted, simple community-driven. I'm Catherine Paganini, head of marketing and community at Boyan, the creator of Linkerd. And I'm also one of the maintainers of the glossary as well as the co-chair of the tag contributed strategy. So why do we need a community-driven glossary? Aren't there enough definitions out there? There certainly are, but there are some issues with the status quo, let's see why. First, when you Google a Cloud Native term, you're most likely going to get a vendor-provided definition. And while vendors did a great job at helping us understand these complex concepts, it's less from ideal because, well, first, it might be biased towards the product or their opinionated view. It's often also just a marketing tactic such as SEO optimization. And I should know I work in marketing and have applied these tactics myself. Then it's not necessarily kept up to date. A definition might have been a priority at some point, but then priority shift, once a definition is out of sight, it's out of mind, it's never updated, and that is a problem because we all know technology changes really fast. And then we see that the audience changed. Increasingly more people are involved in Cloud Native decisions. For instance, whether a company should migrate to a microservices architecture is not a decision that is done isolated in the engineering department. These projects cost millions of dollars and need buy-in from the leadership team and boardroom. But if we look out there, most Cloud Native content is written for a technical audience. That makes it really hard to understand for people with no technical background. So how can the C-suite make these critical decisions without content they can easily understand? And then a lot of Cloud Native content is in English, but not everyone in our community is a native speaker. Understanding these concepts is hard enough, let alone enough foreign language. That's why we need good Cloud Native content in multiple languages. So that's the why. Let's now talk about the glossary and how it addresses these challenges. So the glossary provides definitions from a trusted source that is vendor-neutral and community-driven. And that is key for the definitions to be objective and up-to-date. And then we try to use easy language, free from buzzwords with daily examples whenever possible because we want to make it accessible for a technical and non-technical audience alike. And even technical people will really appreciate the easy accessible language. After all, this is really complex stuff. And then we have more non-native English speakers than English speakers in our community. And to make the glossary even more accessible, we're trying to localize it into as many languages as possible. Currently, we have eight languages live, two more in the making and hopefully many more in the future. And it's really exciting to see how teams all around the world are working on this effort. And then we launched last year at KubeCon.net, so happy first birthday glossary. So let's talk a little bit about our approach. We try to focus on the minimal viable definition, at least from a technical point of view. We don't want to save on examples of words, the things that make a definition easier to understand. But if a technical detail is not needed, we'll skip it. We don't want to overcomplicate things. We want to provide a high-level overview to give the readout foundation so they can read on and dig deeper if they need to. So the glossary is fairly new, but our goal is to be the most trusted, objective and up-to-date cloud native definitions. We want to be a go-to resource for newbies and pros alike, ideally in their native languages. But to achieve that, we need your help. First thing you can do is use it. Use it to learn about cloud native terms. Use it to link back to definitions whenever you write about it, and use it to educate your customers and colleagues. And as you use it, and if you see something that's outdated, needs improvement or is missing, please submit a PR and raise an issue. That is how the glossary will improve over time. So that's the glossary, just a quick announcement. We are looking for technical reviewers. So if you're really passionate about cloud native and really good at explaining these terms, please join us. You can find more information in our Contributor Letter or just swing by the link in your point booth and talk to myself at the conference. And that's it, thank you so much. Please use the glossary and tell others about it. Thank you so much.