 So that was all the time. So if anyone wants, just go ahead. So, yeah, the next topic is about inclusive name initiatives. So it's not Remkins, it's serious. So, you know, in Jenkins, we invested a lot of time in cleaning up technology and thanks a lot that don't work for doing the presentation today for the details. We have this community Jenkins for discussion, it's new landing page where we integrate all the inclusive naming cleanup. So it replaced our G-ray issues and ethics. We aggregated everything here on basically discourse because it's easy to edit, it's easy to collaborate and discuss, and we will be putting all the links here. So basically it's an official project in advocacy and outreach, so I made a patch which basically made it explicit, so we agreed on that more than one year ago, but yeah, just edited. And here are some links, and you can see that there is a link referring to inclusive naming initiative. So this is what I was about talking about. We have a lot of contributors including me, Angelic, Thierry Vasylenko, Karin Target, and Kara Dela Mark. We joined this inclusive naming initiative channels, we contributed to some meetings. So what is it? It's global initiative which is focused on helping organizations, not only open source but also private source to adopt inclusive terminology. And you can see that there are actually multiple organizations participating, including the Linux Foundation, Cloud Native Computing Foundation, these are founding members. So Priyanka Sharma and Steven Augustus are one of the founders of these initiatives, they're from CNCF. Also there are quite big companies, and there are also related projects, including for example, by Kubernetes by Linux Foundation Network Inc. And what I proposed to, we as Jenkins and maybe as the continuous delivery foundation also joined this initiative. So we joined this related project, so basically our name here. I prefer maybe this advocacy and outreach link so that we highlight the PS Jenkins project that we are committed to cleaning up terminology because this is what we announced. And for us, there is no reason to not participate, so yeah, it would be great to participate here. And we agreed that we would be helping inclusive naming created with marketing. So Alex Earl, who posted on terminology updates on CNF recently, he would be also interviewing with inclusive naming initiative and we are helping by sharing our expertise. So, for example, here they shared a tool for discovering mis-usages on screenshots embedded in the documentation. So he created a tool for that, fully-decorized and somewhere open source. So we can do it already, and I think that for us it would be reasonable to not only join this related project, but actually try to participate in organizations. It could be Jenkins or it could be the continuous delivery foundation or both. And for us it would be free because we are non-profits open source and we can join for free. For companies, they're currently discussing what would be the cost for participating. So for example, I also brought it up in my company that, hey, since we contribute a lot to terminology cleanup in Jenkins, we also join as a company and you can also offer it in your company, see if you contribute. But for open source projects it's free. And this is basically my proposal. Let's join. I still want to put it on the developer, my name is the official voting at one of the governance meetings. But I think it's quite set forward for us. And it's definitely win-win situation for all participants. So, well, why not? And yeah, they have a Slack channel. So yeah, there is inclusive naming somewhere. Just a second. It's here. And on this channel you can see that actually there are multiple work streams including community, including marketing, language, setting standards, company outreach, which is rather most communicating with OSPA, etc. But we participated there already. There are regular meetings where we participated. And we could again participate more highlighted the Jenkins project and basically work together on setting, for example, standards, marketing and aligning, use other organizations. Questions? Comments? I think it looks very promising. So the kinds of initiatives that are happening here, would they assist us with phrasing things? What sorts of things do you see us involved with? Yeah, they're organizing quite big initiative in terms of cash. So there is an ongoing proposal to ask premier members, for example, for $15,000 per year for membership, etc. They want to funnel the most of this money to marketing. They are non-profit and what it means that they will be facilitating. For example, they plan a series of blogs about how open source projects and organizations create basically an environment and how they contribute to naming and clicking up. Definitely something where we could contribute. And since they have their marketing team, they need content, we can provide content and they can provide marketing for us by using our content. And vice versa, they could create generic guidelines, etc., using their resources, their outreach programs and we could consume these guidelines, we could implement standards, or we could just, for example, adopt guidelines as Jeff's current angelic is working on a job for localizations and for NTS updates, but in the future we could get these standards out of these working groups. So for me, it's clear win-win and it's totally non-commitment. So why not just by saying that we join this initiative, it will be also quite a marketing splash. Why not? Yeah, I think so. We're going to do the work we are. So why not, why not announce it? Why not say so? Yeah, I was going to say we're already doing this in alignment with what we're already doing and yeah. Okay. And thanks all. So I will bring up this topic in the developer's list, maybe this recording to save time once it's ready.