 Good morning folks. So quick note, we usually start about five after to give folks a chance to turn up. Let me go ahead and stick the link to the meeting minutes in the chat. If folks could go and add themselves there so that we can get a list of attendees, that would be great. Hey, Ed, can you check your Slack real quick as well? Sure. Yes, I can definitely run the meeting. Cool. So I'm going to drop for now so I can get some, so I can get a little bit of sleep. Yep. Cool. Do take care of yourself. I appreciate it. Thank you. Awesome. So, from our folks, the meetings are recorded. They will be posted to YouTube subsequently. If you can go ahead and add yourself to the call. I'll stick that link in the chat and we'll usually get going about five after. So apologies to folks for last week. There was a little bit of cross wires. I was on an airplane. Nikolai was out on holidays and then Frederick came down sick and so things got a little bit crossed. Would someone be willing to share the agenda? Thank you, Nikolai. Much appreciated. So, and a reminder to folks, if you could follow the link in the chat and add yourself to the attendees, that would be great. I'm going to go ahead and suggest that we start diving in. So we'll start with recurring events. So we do have this meeting every Tuesday. In addition to this meeting every Tuesday and the one and a half hour before we go over issues and PRs. There's also the, you can find those at the Network Service Mesh Community link. There's also the CNCF Telecom users group that happens the first and third Mondays. And the CNCF SIG network, which is currently being rebooted, and it meets the first and third Thursday of every month at 11 a.m. Then major events. Major events have, as you might imagine, taken a bit of a hit in the last week or so. So KubeCon, CloudNativeCon, Europe has been postponed into the July-August timeframe. As a result, the NSMCon at KubeCon U has also been postponed into that same timeframe. So our plan is to essentially follow the lead of the CNCF on the spotter. So I do expect that, you know, barring protracted issues. These things will go on as planned in the July-August timeframe, but we just don't have any further details, or at least I'm nowhere further details at this time. Is anyone else aware of anything in terms of further details on that timing? I don't think they have an almost anything public yet. Yeah, that matches my understanding, but occasionally I miss things, and I've been traveling the last week, and so then I really, really miss things. Cool. So likewise, the Open Networking and Edge Summit has also been postponed, I believe, till sometime in the fall. So that, you know, will get more information to you as we get it. KubeCon, CloudNativeCon, China has been permanently canceled. Not permanently, but for this year it's been canceled. It's not being rescheduled. Open Networking and Edge Summit is Europe. We don't have any information on one way or the other, although it's now right on top of where North America would be rescheduled to, so I'm not sure how they're going to resolve that. And then to the best of my knowledge, KubeCon, CloudNativeCon, North America is intended to continue exactly as scheduled, mostly because nobody really knows quite that far out whether or not there's likely to be issues, I think. So that's still on the calendar. Are there any other events that we should be adding to our list of events at this time? Cool. So announcements. As I mentioned before, we meet the half hour before this to just walk through the issues in PRs, and that's on the NSM project page. So you can follow that link and see the things that are being tracked in the community, and that'll give you sort of a decent idea of what's going on. So do we have our social media team here today? Yes. Hi, everybody. This is Ashley. Welcome. Thank you. And all righty. So over the last two weeks, some social media updates that we have, it has been slower these past two weeks than it has been in previous weeks. So over the last two weeks, we have gained an additional seven followers. We've followed an additional eight accounts and had a total of 50 tweets and retweets. Obviously with all of the cancellations and postponing of some of the major events coming up, I think that has had a bit of a toll on our traffic. But as far as stuff that has been promoted in a SEMCon, obviously the postponement of that and prior to that, just trying to get the sponsorships and registrations up. However, that is no longer applicable until we have some further updates on when that will be rescheduled to. Outside of that, we've had some regular call reminders, video recaps from previous meetings, general CNCF weekly webinars we're promoting, CNCF news related to the CNF testbed, some CNCF projects and a couple blogs, as well as the 2019 CNCF survey, which had a nice write up about service mesh usage in organizations. Obviously getting some information out there about the postponement of ONES as well, unfortunately. And then some general retweets about open source, mostly a good visual from Julia Evans about container networking, network service mesh, a big step towards cloud native NFE. NFE, a good post over there as well. And then as far as LinkedIn, also a little bit slower these last two weeks with gaining five followers only and getting the same original content promoted there as we have in Twitter. So the plan moving forward has shifted slightly with the change in events coming up. So as of now, we'll continue retweets and contribute a podcast and then focusing on the cloud native Zero Trust to meet up happening next week in San Francisco, I believe it is. I guess everything NSMCon, KubeCon related is deferred until we have some further updates on dates and things like that. Definitely true. I mean, it doesn't surprise me that things have been a little bit slower. The whole world has been slightly distracted the last week, to say the least. Right. Yeah, I hope everyone is well and safe and working from home. Likewise. So, so thank you so much, Ashley, for the update on the social media stop. That's extremely helpful. So we had been a little bit late on today's agenda. I know that there's lots of things happening in the background. You know, we've talked about some of those new issues in the PR meeting earlier. We're getting very close to landing the forwarder. Commend repo having something executable there. So I wanted to sort of throw the agenda open and see what folks wanted to discuss here. Otherwise, I'm inclined, you know, when we sort of reach the end of what people want to talk about, I'm inclined to yield back the time and we can check in next week. So is there anything else that folks would like to add to the agenda? I have a small update on the examples. Oh, fantastic. Go buy in terms of the emails for the PRS. Yeah, so effectively, I did some updates there. So go 14, which appeared to have some 140 actually go on 14, which appears to have some impact on the on the building infrastructure examples. And that was a small one, but the bigger one was upgraded examples to use the latest release VPP 301 to align with with the main repo with the core NSM components, which was more or less smooth. I mean, I was just following our PR in the upstream what changes were done there and just applied similar changes in the examples repo for the time being, everything is working. I don't see any, any, any huge, huge problems there. So that's more or less what's, what's going on in the examples. What are the things that that I'm most excited about about them, the 301, the VPP agent stuff the way is that it's now using there was an update to the GRPC protobuf generation stuff, such that it causes the new client code, instead of taking a GRPC dot client connection as an argument, and that's a struct, it will now take a GRPC dot client connection interface as an argument, which is an interface, which means that in principle, it is now possible to mock all the things. So that's, that's exciting. Yeah, I mean, I'm not sure I take advantage of all these things, but let's say that in the example, at least we have the infrastructure now. So if folks want to try things there, there, perfect. That's awesome. Yeah, so that's definitely good news on the examples front. So I think that's getting to be good. One thought I'm looking at the stuff that I'm working on for the command for order piece. One of the things I'm looking at is how to test it. And so I'm considering basically if you run forwarder, it will run the daemon. If you run forwarder space test, it will run tests against the daemon. So we can build a single container, and then we can actually test the container in place. Um, so we'll see how that works out, but that's kind of the direction I was thinking of going. Cool. Anything else for the agenda before we conclude for this week? Not on my side. All right, cool. I will see you guys next week then. Thank you. Thank you.