 Hey Jeffrey. Hey Nikolai, it's been a while. It's been, yeah. Have you been? I'm good, yeah, I'm fine. Hello, good morning, good afternoon. All right, start this meeting. It seems like Tommy's not going to join. I'm not sure about Taylor. So, let's see. Does anyone have any particular topic to talk or share? I don't know, like, do we want to discuss, start discussing about the PR, the issues that we have open. One of the best practice, try to pick out one of the best practices and discuss more about that one or like, or just going through the normal schedule and share the incoming events. So, I just want to hear if he has Nikolai, Liko, all your, anyone? We have an opinion. I'm playing some catch up after a break in the action. Okay, check the issues. Last time Taylor opened a few issues regarding the proposals over best practice. I remember correctly. The latest was about, well, this is controversial and we still the discussion and I don't know if we are going to have something or some of it later. I remember that in the last time, they were talking about putting things in, in a Google Drive to start discussion. Victor, it's at the top. There's a link at the very top of the issue of the issue. Oh, yeah. This one. Yeah, I think it's a little bit further above references. It says working draft proposal. Thanks, Oliver. Sure. And I guess Taylor did the same for other issues that we have open. In order to start like interaction and putting things there. We have been taking the time to take a look and to do these proposals. Some of them like this one, like, like having one single process per process type or category per container has been for a while and we have discussed a lot of projects and best practices like supporting with documentation. And it would be very nice if we can just finalize the review and submit the PR or like include like a subject practice. This one just to give a little bit context about the discussion is mainly what had to happen is by one hand we have like, like, making the container for one single concern, like, or process type. The benefits is simplicity. Log handling and things like that. Probably the disadvantage or something that has been pointed was a little bit about terms in performance. And also this is not like a mandatory thing. It seems like you can find that the best practice for containers or content creation. So, yeah. This is your feedback regarding this and hopefully we can close this in practice. So the thing is like, and maybe you have to remember that discussion. So this is nice to have like a definition, a final decision for definition for CNF. So should be nice if we can actually in the fine, the concept, I guess, if I remember correctly we, we did see our attempts to define like CNF. But the definition is not there. So, the idea is if we can agree in a single concept and propose to the glossary, the glossary actually tries to collect some of the cloud native terms and explain it in an easy way like they have like a piece type of template where they try to over as simple as possible like maybe what is the concept, the problem that is addressing and in general how these benefit the community. So hopefully if we can do something like this and propose it to the glossary team, they can give us feedback and also exposure. There's a lot of sub themes in that group which are translating the terms in different languages. You can find like, I guess, like seven or eight languages. And they're more common. So in terms like exposure and agreement, I guess it's a good idea to define something, something here. So regarding the proposal for multiple interfaces, these have been on hold because maybe what we have seen is the effort that the community has been doing trying to incorporate things in the API. So for now, we don't have like a best practice on deal. They release those changes in the QNATIS API. This is why this is a particular issue is on hold. So hopefully we can have something soon. And probably the other thing is like with the incoming release of something that we have to rethink about the way that we, especially the best practices we are offering in terms of onboarding TNS. So I guess in general, those are the main things in terms like issues. I don't know if you want to take a look at any particular issue or like you have any things that you want to discuss in terms like the issues. So regarding the events, those are the events that are coming. Probably the only one who is not listed here and the community is still deciding the specific dates. The natural community planning to have like a small summit in Sunnyvale offices. So some of the possible dates are ending up. August or the first week of September. If you have, you want to have the opportunity, you can join. I guess they're applying to the third hybrid event. So anyway, they're still in discussion. But then on that, we'll, we have the regular foundation events like the open source summit, KCDs, places like Texas and UK, and the Cube Crown of course, probably that's it. So if no one has any other thing to add, probably we can conclude this meeting to next week. Okay, well, thanks to anyone and see you next week. Bye bye.