 Good morning. Greetings. We'll give it a few more minutes for folks to be able to come on in, but anticipating a short meeting today. Also, I know that Liz is out, so you get me this morning instead of Liz, so yeah, fun. Yeah, we'll give folks a few more minutes to come on in, and also making sure that I can see some of the app delivery folks. Thomas, you might be on the spot this morning. We'll see. Dims, I already caught you, so you're good to go. Out of curiosity, who signed in as a tech security? That's me. Okay, cool. No, no, that's perfect. I was like, I know it's a very limited amount of people that can actually be tech security. So well done. Cool. All right, we've got 26 folks in the line, so we'll go ahead and get us started in here. Welcome. Normal anti-criss policy applies here. You have made it to the meeting because this is the August 3rd meeting, then it's kept over in the TOC working doc. So our morning today is going to be tech updates, and we'll be talking about projects applying the move levels. Happy to be able to take any other items of business as well, but we will rock and roll with tag app delivery, which may or may not have updated their slides, so we'll see. Thomas, do you have anything for tag app delivery? So I'm not really sure if others will join the meeting. So there's nothing really new from our side. As we are currently dealing with the DAPO submission, they will present their project in the next two weeks. Furthermore, and this is wrong in the slides here, the operator white paper has been released, and therefore this is finished. And another thing which is also wrong in the slides today is that we sent out a request for public comments for the cooperative delivery working group, so everyone is free to comment on this, and we would like to have a vote of the TOC regarding this working group to get this started. Yes, furthermore, there's nothing really new from our technical advisory group at the moment. You have a link for the, wait, operator white paper. I know you've got it over in the slides as well, and folks can see that. I'm sorry? Do you have a link for the operator white paper ready at hand so folks can move you? Perfect, thank you. Drop it in the chat when you have it. Perfect, all right. I'm not seeing anybody else from app delivery unless they'd like to be able to have themselves now. We will hop on towards contributor strategy, and I know we've got some folks here from them. Yep. Perfect. Good morning. I'm short and sweet because it's summer of 2021, and lots of people are in PTO. So as a result, not a lot has happened in the last month. We're currently choosing a tag logo, which the designers at CNCF have given us several suggestions. The recruiting playbook is in review feedback with our TOC liaisons. If you want to take a look at that, there's gonna be some changes to it that they've suggested. And then next we'll be going to Community CRM, which is a tool recommendation. And that's kind of it for this month. All right, any questions? Anybody else have anything to add as far as we're going on and taking contributor strategy? All right, seeing no questions in chat and nothing else in here, drop onto network. And Lee, I know you're here and I know that I pinged you for slides here. So I'll just let you do it live. Okay, thank you. Yeah, the slide is, so I'm very tardy on filling it in, but it is up to date, and I'm not gonna make you awkwardly refresh it out, but. You get one, you get one per meeting, so it's fine. Okay, all right, thank you. Give me a second. Sure, thank you. So yeah, you know, it's not a dissimilar story from what Josh just said. There've been some folks on vacation. I attempted to take some myself that didn't really work out as a side note. There are a couple of projects that are under active review. So Cilium is actively under review, going through due diligence, which is concluding. I think we are ready to, is Justin with us? No. I don't believe so, but that is good updates. Thank you. But yeah. Yeah, but we're, but it's there, it's done. It's ready to, he's done, I'm done. And the write up is quite concise, but the diligence was done. And so that just needs to be sent to, or Justin just needs to take that forth and make it public, I guess. Chaos Mesh presented this last tag network meeting and they are currently a current sandbox project. They're proposing for incubation. I'll link to their incubation proposal is there. I'll just do a short couple of comments. Just they'd been like almost to the day a year since they had presented their sandbox proposal. And the project itself has done, built quite the community, has any number of adopters. They've just done very well, just watching them go from, you know, just having started up to where that project is now. So it was nice and I'm not, that wasn't my plus one per se, but it just kind of a nice reflection to see that happening and to see folks really taking community to heart. So big announcement, if you haven't seen press releases and things as Lincordy, graduation accepted, graduated, is now there. So we're clearly very proud of that project. Other sandbox projects had been accepted recently. An order of business is overdue. And I mentioned this last time that we met and that is a nomination of an additional co-chair. Currently it's myself, Lee Calcote, Ken Owens. And we'd like to nominate co-chair Ed Warnacky. Ed is a distinguished engineer at Cisco and has been quite active in tag networks meetings and helping Stuart already. So it's nice to be able to, I think this is hopefully more of a recognition of the fact that this individuals are already performing that stewardship. So we just need to get the nomination sent out. Yeah, I think we'll forego an update on the working groups because it not much has progressed since last we met. All right, thank you for the update. Like I said, you get one free refresh every meeting. No worries. That's great. Yeah, and thanks for the update on the projects. I'll watch for the nomination for Ed again. Any questions, comments, notes? All right, thank you, Lee. Moving on, tag observability. Yes, we are also feeling the summer slump. We are considering to simply skip the meeting next in two weeks. We have put that to the question in the meeting in a few. We had a few presentations which are recorded. So anyone who wants to see them more than welcome. One project is considering donating itself to CNCF. That's the Prometheus operator, which is obviously quite close to Prometheus, which is why I suggested if they wouldn't prefer to join Prometheus or Prometheus Community as GitHub orgs, they're taking this internally and we'll get back to the tag. But just as an FYI, they're considering donating themselves. And also Logano's logo news. It's currently ongoing, but we are waiting for updates from the artists. That's on me. I will check in on that one. Thank you. Happy to help. Questions, comments, anything else coming up for tag observability? Yeah, Lene, go ahead. One question. The presentation recording reached you. Where can we find them? I will get you the YouTube link while we're on the call. Thank you. If you could post it in chat, it would be perfect. It's part of the normal tag. So it's just part of the normal recording, but I'll look up that list and put it in chat. Thanks. Great, thank you. Other questions? Right, I'm seeing no one else come on in. So tag runtime. Hey, good morning. Yeah, so we've had a few meetings. So some updates on the projects and the containers and runtime space wasn't cloud presented in our last meeting. So they became a sandbox project too. So they were cold differently. They were called WA-SCC, and they changed their names and they applied for sandbox in this CSF, and they got approved. And so we have some other sandbox projects that are related that already got accepted. So one of them is Crosslet. That allows you to run web assembly with Kubernetes. Another one is Crater. And that one is a Kubernetes state machine, Kubernetes operator state machine. And another project that got accepted together was ORAS, which is OCI Registry Storage. All those projects are related and they're already in sandbox. We also have a presentation from the folks in the Kata containers community. They're going to be talking about confidential containers on September 2nd. So that's using a trusted execution environment. So we're looking forward to that presentation. In the AI, Edge, and Machine Learning Operation Space Volcano, which is a project in sandbox, they're presenting on August 26th. They're going for incubation. Yeah, so that one is Machine Learning Workloads do in batch workloads on top of Kubernetes. Another project called MLflow, which does end-to-end machine learning, it's scheduled to present on August 5th. That's our next meeting on Thursday. And then finally in projects in KubeDL, that's deep learning or Kubernetes deep learning workloads. And that's already in the CNCF in sandbox, but they're presenting to give an overview of the project on August 19th. And as far as tag runtime activities, we are also choosing a logo. So in our next meeting, we'll discuss that. So there's six proposals, so we'll choose one of them. And then we also have a KubeCon North America maintainer session schedule. And yeah, that's all that I have for the updates. Very good. I like how you seem to be partial to one particular logo. Yeah, yeah, so I like that one, but we'll see. OK, I'll watch that space for more. Questions, comments from the group? All right. Thank you, tag runtime. Security. Hello again, everyone. Just some quick updates from us. We have a new micro survey out specifically on cloud native security. We're looking to collect information from various respondents to help make the content that security tag delivers more actionable, more relevant, and useful for the community. So if you haven't already done so, please take the time to complete the survey and share amongst your colleagues and friends. That way we can solicit input from the widest audience possible. We've also got a new security resources section within our repository for projects. This was the combination of actually it's one of our oldest issues that we've had. This came out of the security pals pilot that is still ongoing, as well as some additional feedback from the community. So you'll find within that subdirectory information about embargo, how to create a responsible vulnerability disclosure policy, and some templates within it. We also recently had our half-year review of our security roadmap. We have a lot of things that are currently ongoing. Four of those major projects, we're hoping to close out very soon, with two more projects kicking off. We also had 52 submissions for cloud native security con. It is now closed. We actually had two more come in very late. So we're up to 54 now. And the quality of the submissions this go around has been stellar and phenomenal. And we've got a lot of really hard decisions to sort through everything. So this will probably be one of the most successful cloud native security events that we've had. We also recently had a presentation on shift left automatic generation of network policies, which was a proposal to automate the generation of Kubernetes network policies for just the right amount of connectivity. They had some good feedback on that that occurred on July 21st. And that is everything. So thank you. Yeah, go ahead. This is Josh. I would love to see the security resources for projects get merged into the contribute side to have everything in one place for the maintainers. So I'll ping your tag later. OK. Come up with a way to do that. Yeah, just hit us up on Slack in our channel or you can DM me directly and we'll work to make that happen. Thank you. OK, other questions? All right, seeing no questions. And thank you for the update. Moving on to tag storage. Hi, this is Xin from Tag Storage. Hey, go ahead. So in Tag Storage, there are three projects that have applied for incubation. The first one is Langhorn. We are currently doing a DD for that. Survey has been sent out to the end users. So far we received results from three production users. And so we are going through those. And Louise has been going over their project repose, doing some deep dives, and working with the project team to do the reviews. So that is going well. And the second one, Chuba FS, we have a draft DD doc. And Rafael has been reviewing the doc and providing feedback to the project team. So that is also ongoing. And the third one, Open EBS, there were some concerns regarding some of the licenses used in the project. The project team has been working on addressing those issues. I think most of those are addressed now. And the project team is working with the Open ZFS community, trying to upstream some of the changes they made to ZFS. So that is ongoing. And we are going to schedule a meeting with the Open EBS team to go over the current status and trying to come up with recommendation to TOC. And so in addition to those three projects that are under review, the three tech has been working on the cloud native disaster recovery by paper. So we have been discussing that in our tech calls. And I think all the review comments have been addressed. The doc is ready. So we're planning to send it out to the TOC mailing list to get wider reviews. And so now that the DRY paper is in good shape, we are going to go back to the performance and benchmarking web paper and trying to finalize that. So that's all from the tech storage. Great. I know we've got Saad and Harry on the line as far as for both Longhorn and Chubow. Any updates there from those TOC folks? Saad, come on in. Yeah, I need to sync up with Luis on the results of the survey. So I'll try to do that offline. OK. And Harry, Chubow. Yeah, for Chubow FS, I just had a meeting with their maintainers. So they are currently still need to update several parts in the due diligence doc. And the job is already submitted to TAG for other tech chairs for final review. So this is com status. So I will say the due diligence doc could be finished in the next few weeks. Yeah. Excellent. OK. Thank you. Any other questions around storage? All right. Thank you, TAG storage. I did jump the gun a little bit about being able to chat about projects that we're currently moving around. I've made an error on the slide. Kate is currently in voting. Questions out here, as far as things moving ahead. We've got updates from Cillium as well. We've got updates from Chubow. Anyone that anyone wants to be able to talk about here? All right. Seeing no one on mute, that basically covers our agenda today. Any other items that we need to drop in? Briefly, I'm obligated to bring up Chaos Smash. I don't know if those folks were successful in, they're currently proposing for incubation. And I don't know if that team was successful in landing as a sponsor. So I apologize. I don't know if this is the list of that. OK, yes, it's labeled. This is just the people with sponsors up here. The projects waiting for sponsors are over in the public working doc. And I will drop that into chat as well. That is a perfectly fine question. And I will take a note to add that into this slide for next time. Here is the link for it, where you should be looking for projects that aren't listed here. Other questions? Yeah. I want to think with the voting or the projects in voting, maybe we can show the number of votes that they have already and how many are remaining. So I'm speaking for Kader and that is out for voting. And that's within the scope of the tag runtime. So I'm not really sure how many votes they'd need to go into or to get passed to go into incubation. I can add these. I'm not going to do it right now, but that's perfectly fine. And where I'm pulling this data from is the public TOC working doc. So it makes sense to be able to add that in here. Awesome. Other questions, comments? All right. I will send everyone back into their days because it seems like we are complete here. So all right. Good to see all of you. Be well. Thank you. Thanks. Bye, all. Bye. Thank you.