 Yeah, it might be a short meeting today. I don't know if anyone's got any agenda items, please add them to the agenda. If you want to register your attendance, please add that. So the doc is folks know there's going to be a security release of a boy coming up in the next few hours. So I'm sure everyone's super excited about that. Very exciting. Yeah, do we do we have anything on the agenda today? Yeah, I had one item and that was kind of interested. So I'm currently working on essentially the next generation XDS work. And that's after a lot of my time that includes work on a data plane API. We had someone at Google who is basically essentially the VQ XDS maintainer, but he's now moved to a different project. I'm kind of interested to figure out if we can find someone who's interested in essentially taking on becoming an authoritative maintainer of the two XDS move onwards and who's able to basically provide a lot of the community supports and, you know, everybody do triage and fix bugs and do all this kind of stuff. I mean, it speaks to a wider point that we're now as a community, I think getting to the points in which the Linux kernel where we have large pieces of the system, which would benefit from folks who are interested in taking on more maintenance related role and ownership of those parts. While other folks are, you know, busy working on and let's say your features is their day jobs. Some folks might be interested in just adopting a more maintained and like role and like using the term maintainer very literally here. And I think this is like one big chunk of work which would benefit like a lot from having someone who's, you know, both got their sort of inclination and time to actually take on this kind of task. So, throwing it out there. I'm sure there are other big sort of parts of envoy which would also benefit in this way. Okay. Yeah, I mean, yeah, that that makes sense to me. I think to your point, I don't know that we've done a great job of ramping up people to do this type of long term maintenance. So, yeah, I think I think we should probably send an email on this maybe to Envoy dev. And, you know, I guess like longer term, as we as we get the bots running, you know, to allow people to approve different portions of the code base. I do wonder if we can expand if we can expand our maintainer ranks and, you know, potentially allow other people to own smaller sections of the code base. Yeah, that's a good point. So, yeah, I mean, that's something that we'd have to think through just because that the tooling is not great for that today. You know, like, I think GitHub is often is often doing stuff there and we've got the bot from it, but you know, it's something to think through at least long term. Yeah, that makes sense. Okay. And also I will say I think I think in general where we tried to kind of create this extension policy where we'd have like, kind of a non maintainer owner and a maintainer sponsor. And I wonder and I thought the hope was to kind of try to encourage more people to become maintainers so that they get their extensions. And I think it's kind of had the most opposite where our maintainers like, Oh yeah, I'll take that one. I'll take that one. And now we have the increase in could be so that kind of the increase in maintainers. So, maybe we can do the same in terms of like, No, you have to have at least two people willing to do this and you guys just own this extension. Well, or, you know, to your point, one of the things that we could start being a little tougher about is that if we see organizations, you know, that are doing a bunch of extension work, but they're not maintainers, you know, we could basically say to them that, you know, you, you need to carry some water here. And that might be, you know, not maintaining everything, but it might be, you know, becoming an expert say on some of the older V2 XDS APIs and then they need to do that maintenance. And, you know, for some of the people who I think are in that situation who are doing extensions who typically are our vendors, it's honestly possibly in their interest because they're going to be doing things like V2 installations for quite some time. You know, so it seems like it might not be terrible to ask for something like that. Yeah. I guess the one other thing that I did want to at least mention about the V2 stuff and I'd like to hear your thoughts on this Harvey is, we have talked about some of the V3 stuff getting backported to V2. I assume that you would still be involved in the code review and the development of those types of things, right. Yeah, absolutely. Yeah. I mean, and I think that's also an opportunity for the person who has become the V2 maintenance to also take on a more active role in future work and someone would actually like to do some of the development work there. I just feel that there's definitely a long tail of stuff in V2 which is we have to support for a very long time and I personally don't have bandwidth to do on top of everything else like that I'm active with so yeah. Yep. That's fine. Anything else folks. I guess just one other announcement about EnvoyCon there was an email sent out we were supposed to send out the schedule yesterday but it turns out that they're not sending out the schedule for coupon for quite some time and we're trying to avoid duplicate talks between EnvoyCon and coupon. So unfortunately the announcements have been pushed back for about a month. Okay, well, let's go. Security release happening. Alright, talk to you all later. Bye.