 Good morning. So just let everyone remind everyone the recalls are all being recorded. We usually start about five after. If you could go ahead and add yourself as an attendee here on the weekly meeting minutes. That helps a lot and we'll go going here a little bit. Just to remind to folks if you could go ahead and go to the meeting minutes and add yourself to the attendee list. Should we keep going Frederick? Can you guys see me? Yes. Excellent. Frederick do you want to get going on the meeting or let's see we may have lost Frederick. You're very faint. To put on the agenda onto screen share. You're very faint Frederick. You may want to step closer to your mic. And okay so welcome to the network service match meeting. We have this meeting every Tuesday at 8 a.m. Pacific time. We also have a we also have an a's of friendly meeting which occurs every other week. That particular meeting was last week and should be on next week. We also participate in the CNCF telecom user group which occurs every first and third Monday at 8 a.m. Pacific time and I believe any in UTC time on the third week. We also participate in the CNCF network sync which occurs every Thursday. We also have yeah every Thursday at 11 a.m. Pacific. We have some new information in terms of in terms of KubeCon where the KubeCon itself has been rescheduled to August 13th through August 16th. We are in the process of organizing we are in the process of organizing NSLCon and giving it all set up for that time period. It will be on August 13th. We still have sponsored for sponsorship for those who are interested. ONES North America has also been rescheduled. So that is September 28th through 29th in Los Angeles. The ONES in Europe which is going to be an Antwerp was originally going to be or this has been postponed and that's to be to be determined. We do not have dates on that just yet. KubeCon, Cloud NativeCon North America and Boston is still in November 17th as of now and so if anything changes there then we will post it. We don't have any major announcements at this point. So Ashley are you on the call so we can do the social media? Yes I am. Hi everybody. As far as the last week in social media goes we have gained on Twitter at least an additional four followers followed an additional four accounts and had a total of 20 tweets and retweets. In those tweets I got they saved the new date out for NSMCon which is August 13th of this year. Sent out general call reminders, promoted CNCF weekly webinars, got the video recaps out as well for those that are unable to make meetings. Also promoted the CNF testbed call which happened yesterday and we'll get a new save the date out for the next call happening on the 20th. Then as far as Linux Foundation and CNCF tweets we got the new dates out for ONES North America happening at the end of September and then tweeted about the postponement of the ONES in Belgium. Also promoted some online cloud native summits that's happening at the moment I think as we speak right now promoted the LF training scholarship application as well as a CNCF wellbeing working group considering the times that we are living in now thought that was pretty applicable. And then just some general retweets from Cisco and CNF testbed container related as well as telco and bnfs. So as far as LinkedIn we gained an additional two followers promoted the same original content that goes out through the Twitter account and then the plan moving forward is to pretty much continue with the general podcasts and blogs out there and then start ramping up as we get closer to NSMCon and KubeCon in August. Well thank you very much you're welcome so in terms of the in terms of the main agenda so I don't think we don't have anything set at the moment but there are some things that we want to discuss on the development side. Ed do you want to jump into that? Sure I mean I could talk a little bit about what I've been sort of beating my head against the last week which is getting a very simple pattern going in the command repos where essentially we've got a single locker file but by selection of targets and if you just fill the docker file you know docker build dot you get what you expect which is the runtime you're looking for but if you use the the target mechanism in Docker you can get a test container that would run tests or you could even get a debug container that would allow you to debug the thing um and with a few magic knobs you can twist if you'd like to actually copy the binary in from being built locally on your host rather than built in the Docker container because there are times particularly when you're working cross repo where you really that's what you want right because you're not going to be able to if you have to if you should put a replace directive in that's looking for something locally on your disk to go do that then you're not going to be a little bit correctly in the Docker container so you know that stuff has been going on it ends up being a pretty smooth pattern quite frankly um that makes it very very very easy to sort of poke at these commands directly so they have been sort of poking it back um whatever what are what are folks of folks people people were working on this week it's almost not terrible we don't hear very well oh sorry is this any better yeah yeah yeah we had so my my microphone on my phone is working but not my going over my my headset so I talked directly into the phone um anyways so I have a so the cloud native zero trust presentation that I showed earlier uh is something I'm continuing to to uh fix up but what I want to do is I want to more formally define and give examples of of this work in action and so the significant portion of my time has been focused on uh on getting that particular part up in and uh and ready and trying to clear my uh trying to try to clarify some of my thoughts around it and getting opinions from uh from others on the on the approach um and so for me that's been the majority of my of my of my time um yeah I think um we have some uh some uh work that's planned ahead as well that we want to try to we want to try to tackle um so we want to try to get um uh some more of the identity and policy taken care of because we're starting to look at what's necessary for people to run this thing and in production and we know we know that it works from a uh from a functional perspective because we've we've already shown they work and so one of the things that we want to do is we want to make sure that the uh that the identity and policy are uh are in very good shape like we have working identity and policy then but uh that's something that we need to do our best in order to get right in order to properly ship this out and I think one last um one last part on that as well is in the in the long run so this is not really a goal in the short term but in the long term we're going to uh uh we'll we'll also focus on making a lot of this stuff uh significantly more easy to use like I guess stuff should be easy to develop against but we need to make sure that as an operator it's uh easy for for the operator to uh to make use of but um uh right now you know uh right now we'll continue to focus on getting this thing so that it's uh capable to be run or to be run in production and I'm told that I currently have is there anything else that anyone else uh that anyone else has cool well if there's um if there's nothing else uh let's go ahead and um and uh actually there is one other one other thing um something to uh to consider if there is something that you would like to present in uh in this particular uh meeting whether it's a uh whether it's a use case that you find interesting or uh a problem that you that you see that you think needs to be solved um then uh please add it to to the agenda or come talk to me on Slack and we'll see about scheduling uh scheduling UN uh and uh with that I don't have anything else and so um it's sealed back uh so 40 minutes worth of time and with that thank you everyone and you all have a good day thank you thank you bye bye bye bye bye bye bye bye bye