 So we have this particular meeting, which every Tuesday at 8am, we have every other week We have an Asia friendly call and it doesn't look like we have Nikolai on to discuss. Was anyone on that call earlier today? Yeah, yeah, but it was nothing really important discussed actually, just current situation. Okay, cool. We also participate in the CNCF telecom user group, which occurs every first Monday at 8am Pacific and every third Monday at 3am Pacific. And we also participate participate in the CNCF SIG network, which was currently rebooted and occurs every first and third Thursday of the month at 11am Pacific. We also have had a few major events that have been canceled or postponed. So the go San Francisco, which was supposed to be tomorrow has been postponed until after the COVID-19 problem is abated. The same thing goes for KubeCon, CognitiveCon, New Europe and Amsterdam and NSMCon. So the plan, my understanding is the plan is to still hold an NSMCon. It's just going to be dependent on the new date. Oh, NES has also been postponed. I believe they're going to run it sometime in August is the planned time. We don't have a exact date for that yet either at this point. KubeCon, CognitiveCon, China has been canceled. I do not think they plan to run one this year at all. And so with that, the next set of major events, barring any major issues are going to be the re-negotiated dates for KubeCon, Amsterdam, which will probably happen in August or September. Then we have ONES Europe, which will be in in late September, and then KubeCon and CognitiveCon North America in Boston, which occurs in November. And the CFP for ONES Europe and cloud-native in KubeCon Boston, I believe. Well, sorry. Well, the first one is the CFP is open. The second one, the KubeCon Boston, the CFP is open in April 22nd. And so with that, we have a, as a reminder, we have a project board that we've been tracking things with. So if you'd like to know what's going on or want to know where to get started, please check out the tracking board. And we also see we've already gone over the NSMCon announcement. And so with that, sorry, my system is lagging a little bit. Rather, my documents just crashed. Cool. And we now have an NSM operator, which is hitting the community operators repo. And do we have anyone on the call who has worked on the operator by any chance? Yes, it's me. Hello, everyone. Cool. So, yeah, so was a repo created for you and was that added on or does that? The repo actually is a community repo. So you will find like dozens of operators there. So it's actually will host the NSM operator for OpenShift and also for Kubernetes. And then using your pretty life cycle manager, you can install directly from that repo. So as of now, if you just install an OpenShift cluster, you will see an SM operator on the OpenShift for example. And Kubernetes is on its way. It's already has a PR there. So it should merge by this week as well. Oh, fantastic. So I apologize. I misunderstood. No, that's fantastic. It's getting on to the, this is for operator hub website, right? Yeah, that's it. That's it. If you want to, I can talk a little bit later if you want about it. Cool. And yeah, one thing we need to do is we need to set up that repo for you to push on, push things onto it. So I'll work on that setup thing. Yes, sure. No problem. Cool. So social media, media community team is doing a written update this time. So I'll cover their account unless someone else from football would like to. Okay. So we have some Twitter stats on as of today, we have a 726 followers, so we've added six more. We followed six more. We have added nine more tweets for a total of 1,122. And we've posted information on NSM con and call reminder CNCF weekly webinars and news about CNCF joining Google summer camp of summer camp of 2020. And we've also posted information about LF AI on an ex community virtual. And we also have the information on VMware's open source projects, trending on GitHub. In LinkedIn, we now have 141 followers. And we increase a follower post the same information is on Twitter. Information on NSM con 2020 and similar have been postponed for the moment. Right now we have an empty agenda. Is there anything that anyone would like to discuss? Well, Frederick, if I may, I would like just to explain a little bit about that community repo. And it's really quick. We have two repos. One is the NSM operator repo where you can find the operator itself and the community operators repo just it just holds metadata about the operator. And then with that it is possible to build a hub and to pull the images from the proper repositories and run the operator on the platforms. So if in the near future, we were to move from my private or not private but public repo personal public repo, where the NSM operator is to under the NSM org. This is not a problem because this is the operator itself the bundle that the metadata that is hosted by the community operators repo is to work to the same it is remains the same. And each and every version of the operator will generate a bundle with a metadata that will come into that community operators repo. The cool thing about that is that you will have it available on the operators hub. Both an open shift and Kubernetes if you have an operator lifecycle manager powered Kubernetes platform. That's it. Okay, nice. Yeah, so we'll work on getting that, like good repo up and running. And so in terms of the, so in terms of the repo. How does this thing is similar to Docker hub so like creating a commit against a branch or against master does it automatically update the hub. You mean the the image itself or or the source code. So it's based upon the it's based upon the image and the latest on there right. Yeah, yeah, I actually have also a personal query repo where the image is hosted. And I have source code on a GitHub repo. And the GitHub repo this is kind of confused that it is a GitHub repo that is called the community operators. There we have just metadata the metadata is just saying hey, here we have an operator that does this this this and that's and we have the path for those images so we know how to install it. It's kind of metadata repo only. And one on the image side is it isn't quay.io. It's just like a public image repo. Nothing, nothing special about that. And the code itself is the one I'm eager to kind of move to under the NSM org. And the other two, it doesn't matter if we keep a quay that I always should be like a repo under also than the NSM org, or we can just change the repo for that particular image to something that NSM is already using. Okay, nice. Well, thank you for the, thank you for the quick description on that. You're welcome. Are there any other topics that people would like to to discuss. Okay, if not, we can break earlier this particular week and we can and we'll reconvene next week and we should have Ed back and the scenario will go over all of the variety of updates that we have for ran SM. So thank you everyone for your time and we will see you all again at the same time next week. Thank you. Take care.