 Hello, Naglian, Tom. Right, a few notes from the starting. Right, afternoon all. I've just shared the meeting notes link. Okay, hopefully you can all see. So, yeah, first item to note is that the events on the 17, the calls on the 17 and the 24th will be cancelled because of KubeCon and recovering from that. Also, worth noting that for those of us who have a clock change savings time change next week, the call will be moving back an hour to its more usual time. I think probably we've spent a lot of time on the last couple of weeks going through the events. The one that I think is worth spending the time on is the informal buzz of the feather session. So, there is an issue in GitHub that was raised. Excuse me. There's also a discussions forum. And there's also a form which people can fill out if they are interested in attending and whether they've got a, you know, an item for discussion or not. I haven't seen the latest numbers, but I understand there's a few people have signed up, which is nice. I don't know if Taylor or Lucina, you've got an up-to-date view of how many people have signed up for the informal session. Good morning. Yeah, it looks like 12 people have responded so far. So, feel free to share the form with your community, especially those who will be attending in person. Yeah, absolutely. Thank you. So, I don't know whether either you or Taylor want to add any more about whether there's any further input you want to help organize that with just in case you're sharing the form and the details of it. I didn't understand the question other than the form, the organizing part. What was that? So, is there anything else you think we need to run through today on this call in terms of shaping it, organizing it, or anything else? Or is it just a case of us sharing the form within our communities? Well, I do think we should organize it. I don't know if to organize it some more. I don't know if that needs to happen on this call. I don't know. I think the two things I was thinking were making sure that if we're going to have something like a birds of a feather that we have that we can start putting together like what is the any topics or whatever. I mean, normally what my experience with birds of feather is people can come up to like a whiteboard and just write in a few minutes or whatever. Short talks. But if we have material together that people say they want to talk and we can start putting it, then that'll, I think, get other people ready. So what do we want to do for anything like that? And then the other part is the working session. If we're going to have things that we actually want to try to actively work together on. If we're going to have something like a bird of a feather over there, then having one or a few, you know, two or three, I probably wouldn't choose too many, but things that we'd like to work on and maybe have that together. Like for instance, the best practices. I don't, I don't think we should say any best practice, every best practice. But if we say, here's a few that we're interested in. We can always adjust these things when we're there. But if we have some content ready, whether that's one of the ones that have already been put forward or something else, then if we have content that's, you know, 20% or 50% done, it's better than zero in my mind. If we want to work on the glossary terms, then picking, you know, a couple of terms that we are interested in and starting that so that there's actually some content. People are in my mind more likely to contribute if, if there's something there and it gives them an idea. So I would say organizing the working session and the birds of a feather would probably be it. Okay, I think that makes sense. I agree. If we've got a couple of open pool requests, or, or Google Docs or whatever, you know, however we want to structure the work, but that's been started because I agree, people will find it easier to get up to speed with ideas and so on. So when you mentioned the, you mentioned the glossary, and there's a couple of, couple of issues we've already been relating to that. I mean, we could, we could just create either Google Docs or a discussion item in GitHub that starts to collect the glossary items that we want to define. I know there's some discussions already to kind of collect or do in this issue. As far as today or just work before we get there as promotion and just a general preparation, we have the, for the gathering. So we have the form. I've, we have the, our planning doc ourselves, which is more for internal Google Doc. In fact, is this your screen, Tom? Yes. Okay. Can you bring up that document? It might be easier just to look at what we've done and what's left. Do you mean you could part of the Google Docs one? The Google Doc, the planning for the gathering. Yeah. Yeah. Probably should just name this planning and doc, but they, yeah, so there's all that section there. The rest was content to let us know what we're doing draft content, I guess. So we've, we have the form. We're planning to do that with some places. So if there's more places we'd like to share. What's not on here, but we should probably add. Lucina, I think you were, you've already started some stuff for Twitter and we're planning on continuing that. Marketing it. Yes, I can. Continue promoting the gathering when I promote. Yeah. All right. So then get up. We have a discussion form. Can you click on some of those and bring them up? Tom should be clickable even though it's direct. Oh, look at that. So that, you know, some of the stupid is just kind of where anybody could stumble across us. Number one and number two. Potential areas for, you know, talking. If someone wanted, and I'm not saying anything here. Do you see any responses? So no responses. But, you know, we can have people do discussions here. If wanted, we have a. The issue for this. So there's an issue for the event. Has anyone added anything else on the issue? No. I mean, if you had some, some interest in doing something specific in the event, or if you think some colleagues might be, we could get them. Okay. Go ahead. Yeah, I was just confirming. Yeah. So, so on that point, and Thomas graph has already signed up by the form. But based on a disc, one of the isolated colleagues Joshua. Someone was named and introduced me to him and Liz Rice and suggested they come along if they can. Okay. So, I don't know where we all where we'd like to put everything I was trying to provide some different places. I don't know. Until we decided and not, you know, hold off until it's a week till. But whether. I think whether. Of course, the form helps us gather some of it in one place, but then publicizing. So. We can add stuff into this issue or put it in that discussion. As we're going forward. I think we could. We need somewhere that's like a, here's the public agenda document. So that can be. There's, there's many choices there. The other place where it's published is in GitHub under. There's a new events folder. Is that on there. Maybe that's not. That didn't get added to the Google Doc list. I guess it didn't. Put it in there. Okay. Okay. So this events folder is new. You know, right now. There's no, here's a CNCF. All telecom. Top level, I guess it. Well, it's just CNCF. There's not like a CNCF taco. And at one point we put some stuff under the telecom user group. And, and it kind of seems like the CNF working group is. That place. There's, there's nothing at a top level though. So, beyond that, so figured for now. Putting events that are related to. The working group and. Maybe the certification test suite. Even. Telco days mentioned here, but we could always put stuff here. But in any case, this is it for the community gathering. And we could use this as here is the. This actually is the document that we. Do PRs to to add the. Agenda. So of course, having the location designated somewhere. Or everywhere is going to be good. But as we put together stuff, we could publish it here. And then point people. Like, what is the easiest to market? So if Lucina is going to be saying, Hey, here, go here. Come to the event. The form right now is great. Come sign up if you want to go. But where do we tell people to go read for updates? We're not going to be updating the form over and over. So where do we tell them? So this can be a, if we want. For the actual event live when we're there. We can of course do work in individual. Places where we have stuff like the, the glossary. Right now it's just an issue, I think, but some of the best practices actually have Google docs. So we can just work on the drafts for those. But in addition, we have. You know, how do we do live notes or shared notes or whatever? We do have a draft. Ether pad. We haven't shared it yet because I think that those are just public and I'm kind of afraid that we may end up seeing like a bunch of spam in it. If we just post it a link to it. But this kind of. Gives an idea of what I was thinking and I don't know Tom and Nikolai and. Lucina, anybody, Akash, if y'all have some thoughts on this, then we can adjust, but this is kind of how I was seeing. The agenda and how we're going forward potentially. And. And. I, this is totally just more of a draft right now. If we have the birds of a feather topics and, and then working session, then. You know, we can add stuff in here, share this and then put more. But do y'all have some feedback or thoughts on, on what we could do. I think in terms of this, the agenda, I, I like the idea of having the. The kind of the quick lightning talks to start with, and then a working session. And, and as we said earlier, to bring some already started. And. Work for the working session. In terms of capturing what's happening on the day, I think he had as good as anything else to use. You know, it makes it easy to catch what's going on. And I agree. But having a single place that we can point people to, like to get her article. And. It's a, it's an easier way of, you know, making sure everyone's got the right information. Can you lock face. But it adds. Probably. I mean, I don't really care before, but. If we. Link this from other places, like the. Events get have. Document. So that people can see here's, here's all the content that we talked about. And the live. Or the notes. And all that. It'd be nice. Just. If it in. A read on. Awesome. Yeah, it looks like you can create a read only. Specific URLs read only. Rather than. The link for the document. Did it randomize it? Looks like it. We. It's the same result of each time. So it's probably some. Some hash, but. You'd have to really care about getting. Well, maybe we. We post the random one. The read only. We could put that right into the. Different places that we want to share. Yeah. What happened now. And then anyone that's saying. They're interested. We can give them access sooner. And then. Share it directly whenever we're there at the event. Yeah. I didn't, I didn't know where to put the. Cillium ABF for Delco workloads. So I just put it like a topic discussion at the top. But it could be a five minute thing. That's what we're talking about. I was leaving it. The idea of. An open longer discussion. So the fight, the birds of a feather. Hopefully we can. Just keep those short. And not let. You know, one of them turn into. 20 minutes or an hour. From five minutes on the, on the other hand, it would be okay. I think to have. Here's a larger, longer discussion. You know, it's kind of thinking. The multi network. Okay. Were you there? I don't remember. And ended up talking about the. Potential adding a new Kubernetes object that. Had the. Information about declaring. You know, multiple interfaces. Not as a, I think it would be like a super. I don't know. I don't know. I don't know. I don't know. I don't know what it said or a. Of what. Maltis. So compatible with Maltis and other things, but. Yeah. Generic. The whole multi network group. So they. Kind of. They had some specific agenda items that went to work through. And. Questions and separate for, but they also had kind of. Open discussions around. Use cases and other things that were important. I think. So they didn't have a birds feather, but they had kind of working working session time and. Open just topic discussion. So. Okay. I think leaving some time for that. So that if we want to dig into something or someone has a. A use case and. They want to talk about. A problem space and practices or whatever. But technology is coming forward and we want to explore how it. Fits. But what were you thinking or whoever put it forward for this. This flexibility of seeing that plugins. So that was the discussion I've been having with. With us. So obviously. Certainly we buy. Our communities platform from a vendor. And whilst. C&I plugins are using a standardized C&I. There is a, there is a series of kind of validation and certification steps. But we would want to go through. Before introducing a. C&I that isn't kind of bundled with the product. Into the stack. Because it's another. It's another thing. C&F and that has to. Check. Yeah. Their application works with. So it's more about. Just a. I don't think I've really got an opening statement. I. You know, maybe. Maybe I need to have a little chat with. The. I've been talking to and see who's going to come and. Kind of how they want to frame the discussion is. I'm more. Suggested it on their behalf. Rather than. I think in terms of the ordering, I wonder whether the shorter. Kind of lightning talks should go before. The longer discussion. Set items. Just so we don't. Kind of potentially run out of time for them to. Happen. All right, I agree. Can you just move that down. And maybe we rename it to call it. Open discussion ideas or some, some other name. Can you get that read only late. Link and then add it to the. To do list in our planning document. And then post it to different places wherever is appropriate. What else do we want to do? I probably think a much else. Am I. In terms of the logistics of location. Is that being dealt with or is that something to deal with still. Still needs to happen. Lucina has looked at some alternative options. Like co-working spaces. I don't know. I don't know. I don't know. I don't know. I don't know. A bowling. A bowling place. Other other ideas. So if, if it turned out that we don't want to be at the RAI. Nothing set yet. So. Okay. Do you. Or do you need. Help. Or. Only want to. Sort of assist with getting that sorted or. Go back. There's a section just for the logistics. Or is it a checkbook section? I think it was that. Yeah. The ideas for where to go. Lucina, do you have any feedback? I know that all of the co-located events. For Kubecon will be held. On Tuesday. The 18th and some of them are. We have a meeting room available. I know they are. Morning, half the afternoon for our full day. I think if we wanted to try to find a space that are. The conference. Center. We could do it. On the fly. Or. We could ask the events team if they have a meeting room available. I know they are. We have a meeting room available. So that. They may or may not be able to help us. Get a, an official room at RAI. RAI. In the past, there's been talk about. You could use the lunch room. Or informal meetings. And then of course there's the hallway. I've only been to that conference for one time. I can't recall the exact layout to say meet us in the. Corner. I think we're going to have a meeting room available. So. I'm going to go back to the last meeting spot. Yes, across the street is a co-working space slash. Coffee shop. Okay. Talkie. I haven't emailed them yet. To see what their meeting room. Opacities. And now we have. Well responses of folks who are interested in attending. So that group, the group of map size. Should be easy to accommodate for. If you want to have a room. That's a little bit longer. A walk away. And there's a hotel and now, and how. Hotel. There's no vacancy for rooms at this time as it was an official. You come. Then you block. But we may be able to use the conference room. If it's not already booked at that time. And then the bowling alley. The six minute walk. I know there is going to be a. The big about being fired bowling party hosted by our mo. At that. At that bowling alley later on in the week. So they may already have. Some more requests for, for meeting. So it's up to. Would they. Ask the same team. If they. Have time to help accommodate that. Which. If we have a small group under 25. Then that seems like a good option. We have a target of. Attendees we're trying to meet. Or would we be okay with a smaller group of. 15 to 20. I think it'd be nice to get more, but I still think it'd be worthwhile meeting. With. It's hard to know where the people are going to. You know, respond to the form. Later. If that's all. It's hard to know whether people are going to, you know, respond to the form later on, or not respond to the form and turn up anyway. Etc. I'm not really sure how history tells us. I expect that. There will be some number that show up without ever communicating. And. If it's more than the group that. Shows up to. These calls, then I think we should do it. If we have the opportunity to talk to anyone new, good. And if we. Make progress in the working session also good. So. Yep. As long as we have it. A space that's. Known and easy enough to get to them. We may have people that. For whatever reason, didn't know about it. That are at telco day and go, yeah, I want to go to that and show up. We may double whatever the number is. And. I'm would like to get. General. I don't know if this would be a good place for NSM. To come and. Talk. We had had some. Talking to Ed and stuff in the past. The thought of having. A working. A working session. I don't know if this would be a good place for NSM. To come and. Talk. We had some. Talking to Ed and stuff in the past. The thought of having. A working session. With like some best practices and some use cases that were interested in the past. But nothing has really happened for a while. So maybe they'd be good. And then if there's any other projects like, hey, we shouldn't. We've had a lot of work from litmus, but is there another CNC a project. For the five minutes birds of a feather. For a. Working session where we're writing about use cases and putting content in. I feel like there's. This should be a, here's a time where we're really trying to encourage and move forward on. Collaboration between different parties. Have you been working in the. What's the NSM folks? No, no, not recently. All right. I can reach out to. Some people. Any ideas for. Like. Here's a CNC of project that we should really have. We should really be talking to. Is that a fun talking using any CNC of projects or caring about any interested that we should try to get to come chat with us. The ones I'm aware of are. Silver. In terms of things we interact with directly. Obviously we've. Not directly. Silver and camera. Not quite sure. That would fit camera. Want to. Reach out to because that's telco API. So. In terms of. Yeah, no. I don't know. The only ones I'm aware of are. Silver. In terms of things we interact with directly. Obviously we've given that is and. But not. Not directly. Silver and camera. Not quite sure. to reach out to, because that's telco API stuff. So there was a GSMA announcement at Congress about some API initiative, which is being delivered by the camera project within CNCF. So that could be relevant. Thanks that that's been brought up on some prior calls as far as what are the different projects How is anyone working together? Do you know anyone working on that, Tom, that we could invite? So I know I've worked with Peter before and Nathan. I know there are some other I doubt any of them are going to Amsterdam. Right. Yeah, there's a bunch of people there, but I don't think any of them will be going. I can reach out to Peter and maybe we email the mailing list. I'll reach out to Peter and Nathan first. All right. They can share it within the community if they think it makes sense. Yeah. Okay. Sounds like there are some plans. Let's see how we get on for next week's meeting. Is there anything else you want us to talk about today? Are any of the best practices something that we want to try to publish before the event and any of them? Ventress. If you just look at the, probably have issues that we could work on before them. Um, well, so, so I think the glossary one is, is, and it's not a best practice, but that could be a good one. I had started. On one of them. Within Google docs. Which one it was. I think it might have been. Yeah, this one. Okay. So we could, I could, you know, flesh this out a little bit more and then, you know, have that as a starting point perhaps. And I think you had started one as well. I tried to add one for every issue. Select the readiness was the one that you put in there. Right below. And of course we have the related. So I have a doctor for each of us, they're related, but it was just to keep them separate. Yep. Go ahead and click on that. I don't know if that'd be there. So I, I think Victor had started it this way in a different document. So I've just been cloning him and starting, but it's just the. Mark down copied in and then fill in the sections. And of course you got to do a little bit of. Playing that when you copy it back, but. You're basically doing that. The sections. And if you scroll down so that. Any in black is kind of the ready. The red is here. This is just copied over. We need to change it. So these have no motivation. It looks like that the static. External. Resources that you had. Was pretty close. It seemed like it had a lot of the content. I mean, you know, similarly, so, so. The code in this document was italics was. Copied from somewhere else and. Okay, okay. Non italics was ready. All right. Well. I mean, so that part is not done, but I think the references and readiness. Unless it was a liveness. You scroll down. Okay, so there's a proposal kind of started the proposal. Yeah. That's minimal. Notes. Added some more notes. Yeah. That's it. What was that? I wonder why we put that someone must have. I thought that was related though. Yeah, it's not red. So. There was something. Said. About the. Development side. And. I think it might be in the liveness, but. Victor was talking about the different. Attributes that you can use for these checks like a liveness and readiness where. The. How often you check and other things. And. That's probably something that we need to ensure it's on both of them. Yeah. Increase CPU usage as a result of, yeah, this is, this is it. So that seems like it's related. Need to check which ones are actually the same in them. But we're going to have some related content there. I think that quote. From that cloud native documents, probably a good reference also. And just keeping. These are both of them. Please. Okay. So perhaps. So we've got a meeting next week. And then. There's a meeting. The week after. Just thinking about when we should make a decision about which. Because obviously these will get worked on over the next couple of weeks. We could then make a decision about which ones we take to the working session. Based on. Which has more to go. And that's just got me thinking that actually. April the 10th. I don't know what it's like in the US, but that's Eastern Monday. And that's a public holiday in the UK. So. I won't be around. I don't know. All right, April the 10th. I don't know if there's a public holiday elsewhere. But either way, that means that my, my last meeting that I'll be attending before. Is next week. So either next week or a week after, perhaps we make a decision about. Which of those Google docs we take for the working session. Based on how much work has been done in them. It's unsensible. Yeah, it looks like it's just a holiday. That's just a, I mean, I'm just looking at one of those calendar places. Easter Monday. Worldwide. So we could. Do we want to just say. Not will cancel the town. Because it's a, it's a public holiday in UK. Germany, Ireland, Italy, and Spain. I have that in my outlook already. So I suspect some of the European countries as well. Yeah. Let's just go ahead and put. Canceling. April 10th. Easter Monday or whatever. Thanks everyone. Thank you. Speak to you next week. Cheers. Cheers.