 All right. Greetings. See if you folks in the line will hold for a bit to come on in. All right. Emily, we're at 22. So I think we can probably go and get started. All right. Thanks everyone for joining us today. It's April 4 as a quick reminder. Your attendance in these meetings, it combines with the Linux foundations anti trust policy notice. A few notes on logistics on the slide. If you have any questions, please jump over to the to see Rupo for more information on our meeting schedules. To see members present today. And, and onto our agenda. We've got some tag updates and some questions to see members will provide will also be providing updates on where projects moving levels are at the end of the discussion today. All right, let's get started with tag storage. Who do we have from tag storage today. Hi. So from tech storage. We had a presentation from the project Pelican in our last meeting. Pelican is a project for in memory cash in. It's a fork friend open source project under Twitter. The maintainer who gave the presentation was a former Twitter employee. They are looking for advice on how to grow their community. So we recommend them to donate the project to CNCF. They're interested. There isn't a project for in memory cash in CNCF currently so this seems to be a good candidate. Also the project has been used by Twitter in production internally. So it's probably production ready. We need to figure out some potential issues with copyright and the license, because it's a fork for of an open source project under their Twitter GitHub. Maybe it needs to be renamed, or the name needs to be donated to CNCF by Twitter. Sure, sure. I have it. Let me actually see. Sorry to interrupt, but it seems relevant as far as like, Oh, hey. Yeah, link. And we also have other projects project. Pro biga and excellent coming to do presentations in the next few meetings. Pro biga is currently in, it's currently a sandbox project in CNCF and excellent is applying for sandbox. And we also made a great progress on the white paper that we are collaborating with the D okay community. The first draft is ready for review. Can you send that out to the TOC mailing list so that the community has an opportunity to take a look at it, or if it was already there, I must have missed out. Oh, I was just thinking it's a little early still I like to get more feedback from the D okay community, the data on Korean is coming to be before we send it out for general review. Okay, let us know when that's ready. Thank you. Okay, thank you. Yeah, that's, that's all from me. Thanks. To see members, do you have any additional questions. Okay, let's move on. Thanks. Tag security. Awesome. So just a couple of quick updates. It's going to be a quick one from last time. We keep going EU security village schedules now out. We do have an on conference. So this is a thing additional additional input on the topics that we'll talk about. There should be a doc or a hack empty that will be coming out. We're hoping to get some topics to see how we can break out the sessions that, but this is going to be the first security village that we do so we're very excited. That's going to turn out. The work on from the supply chain working group we started working on a paper called what is a secure supply chain policy. Essentially this was about, you know, how do I make a policy around supply chain, what are the things that I should check for and how should I be checking for them. And as a group discuss we eventually settle on a re scoping of the topic to be supply chain security expectations versus realities for executives. And so the new goal for this this piece of work here is to have a short document about like less than 10 pages to kind of talk a little bit about we are looking at supply chain security. As an executive in a cognitive space, what are things like broad kind of mindset changes that you may have to think about. So breaks down to three, three main topics like securing over time, you know, if law for law for shall was released today, it doesn't mean that it wasn't in your cluster the day before security over uncertainty thinking about, you know, known unknowns and how to back in set and security securing a scale in terms of, you know, how do I then scale controls out around, you know, knowing how to secure over uncertainty and time throughout my entire organization. So this is a re scoping of the book. There's already a good outline in the documents which is linked from the issue. So if folks are interested in that or have any other ideas on what should be covered. That the issue number should lead to that. One last thing that went to the highlight is we we made a proposal to spread out chat terms a while back. The background context on this is we have two of the three jazz, having the terms and at the same time. And the idea behind that as we hope to spread out the term so we have like a little bit more continuity. We also have ability to do channel is transfer a little bit easily. That's it. So first question is where can folks that are interested in the on conference for the security village submit suggestions of topics. I believe that is, I'll put the link in the chat, but there should be. It should be on the coupon schedule. Yeah, I'll drop the link in the chat right after this. Thanks. And to see members if you haven't had a chance to take a look at that message, please do so. If you have any questions, please direct them to the security tag chairs around background and reasoning for those share terms, but we should be able to unlock them. So they can move forward with their election. Any other questions for tag security. All right. Let's move on. Tag runtime. So today, I run this is ever happy to present to tag runtime today. So for that runtime about the presentation and communities. We have a couple of projects to present at our pie weekly meetings like CRI. Oh, and Kada for graduation and Karmada for incubation. Great progress that we can notice for all these projects and the grass in adoption and contributors. So, for example, Karmada they had many integrations with other CNCF projects like Argo CD Q edge, and other long list actually off CNCF projects, in addition, of the grass in adoptions, like China mobile and other 15 adopters. And also the number of contributors has been increased by 50 compared to the sandbox and 3000 stars, which is, you know, like, in addition to a really good roadmap. When it comes to Kada. It's like the project has had reached like 6000 stars, more than 2000 260 contributors in and gross like 280. So since the incubation. So it's, it's like great progress we can see a we can see from the maintainers and contributors in general. And also the roadmap plan was was really great. We had very good conversation with all the project that presented to the tag runtime. And we had a couple of feedbacks. These feedbacks have been captured either in the meeting notes or in the GitHub issues. So, yeah, and also we have a very busy schedule and in the upcoming meetings, many projects have already been signed up to present, like the ZOT Kepler Q Marine racer. In addition to other projects that we already reached out to. So we are thinking about increasing the meeting cadence to be a weekly instead of five weekly. We have multiple projects that we wanted. They wanted to present at the same day. And for that, we wanted to call out that you know like that runtime is looking for more contributors. With that workload, we are expecting and actually we already have any question related to that. So moving to the activities. We have a couple of work work groups to the first one the IOT edge work group, which is continuing on. Sorry, continuing working on the edge native application principle, white paper, in addition to working on the edge native landscape, which reached like 156 projects so far. And I think that we wanted to mention that the work group has invited Larry Peterson, the CTO of the open networking foundation to present on a preface as one of the biggest name and software defined networking posting specifically and industry. He will discuss software defined networking and the open networking foundation. This would be very interested to invite all of you to attend at your convenience. One thing that we noticed that the KCB, the coronet is like control plane age. The folks from KCB, which already actually applied to Sandbox, to be a sandbox have been collaborated with the IOT edge working group on a consistent space. So Nikita thankfully just reached out to them and they invited them over to present to tag runtime meeting. Hopefully they will sign up soon. Moving to the patch system work group. They still continue working on the CNCF patch landscape. And for the container orchestration device, they're working on CDI support in singularity merge. And the feature actually to add the CDI support in container D is already exist in 1.7 which was released recently, and this feature they is very important to the DRA work that which are, or they are already, you know, like working on at the same time, which implemented, you know, like implementing and, you know, like enhanced, you know, like in the last two releases of Coppernet is 1.26 and 1.27. Finally, talking about QCon 20 years in the EU. So the tag runtime has scheduled a four for four hours meeting. So folks can come, come and go meeting, you know, like meet anytime. So we encourage if, you know, like if we can spread the word, the word that if anyone wanted like a dedicated meeting, it would be great if they reach out to the tag runtime, select channel, and we can try coordinate this meeting in advance. And another good thing to end this was that the Covernet is on each day is already sold out. So, yeah, that's it. Thank you. So folks like tag runtime has been super busy and a lot of things have just popped out of the queue. Does anyone have any questions. All right, let's move on to the next one. Observability. Hello everybody. We've got a couple updates. The last month in the lead up to coupon has been pretty much in the tag, largely about a working group that we'd like to launch. But briefly last month in our update, there's a TOC issue. As of this morning, sorry to sneak attack anyone. But there's a link to the actual document in there. It's also in the slide. That's gone through several rounds of community review. It's been driven. It's been driven by Chris Larson from Netflix and VJ from eBay. And they've kind of, you know, they've been establishing a lot of a lot of buzz and a lot of activity and interest around getting reviews on the document. There's been a bunch of updates and it's probably time to put this on the TOC radar formally and say, Hey, we'd like to launch a working group. They will be the chairs and I think we have a lot of interest from the tag membership. I can be brief and be done there or speak to another level of detail. Just let me know. But in Q&A we're moving on. I put links to our last three meetings. Another thing we mentioned last last month was Pixie had come late in February to give an update that really was was fairly 30 or 40 minutes. It was good. But with a lot of good Q&A and they covered the growth of their community, how they're engaging with it topics like stabilization of the code base and moving to cementive versioning. We had some discussion around CI CD deployment models work that's been gone on to make it a little more turnkey to work on Kubernetes, you know, polish on the home chart and things like that and they did a demo. I believe they're looking for a TOC sponsor, but I haven't talked to Zane in a week or two. And they've made an incubation proposal. The other two meetings there, if anyone wanted another level of detail to see what's been going into that document. But as I said, we really largely discussed the working group proposal and charter and the scope of it and all of that. And then we've been doing some coupon planning. We've got a maintainer track talk in the EU coupon that I'll lead it will be giving. There's also a durability day with a ton of planning that's gone into the CFP. That that committee has been really driving hard as well from the outside again. And then this the last, the last two points are LL is, but I believe that we'll have representation at that meeting. In a few weeks in April. All right. Any questions. Oh, the profiling work in open telemetry is really transitioned entirely to open telemetry at this point. So the, so the text doesn't have any activity there. Successfully transitions. All right. That's fantastic. Okay. Let's move on. Environmental sustainability. All right. Hi everyone, it's Max speaking. Yeah, we're very much excited about the QCON you we're going to have a tech project meeting planning out some agenda and what we're going to do there. Exactly. We will present some of the survey results discuss about a couple of documents which we have currently and pre review and looking forward to get them done until QCON as well as to try to do a kind of micro workshop for a topic which comes in the end of the presentation to Yeah, beside that we have the environmental sustainability survey results. We're currently drafting a blog post together for releasing and publishing it and do some final mock ups on the on the slides itself. We had in the last month's a presentation from cube cream. It's not written here. And we're looking forward also to see Kepler on the 12th of April. We can do it with the other tech together. So Kepler doesn't need to present it twice. Nevertheless, it's for us quite interesting and relevant to see how they do their measurement on the system and how it can help to identify basically the resource consumption, especially in the energy consumption. And then last but not least, and I would say this is the most interesting topic which we currently have in there as a proposal to define a measurement and approach for the CNCF projects to give a baseline and an understanding of their software carbon intensity footprint per the projects. And in this regards we're already talking with Falco or better to say Falco approached us and said like hey, we're very much interested in to understand like how energy hungry is our system and how we can improve it and what are the next steps. So there will be the best next test candidate. We had already first discussion on that and they're happy to be the test candidate in this case. But when we have identified whether which which approaches the best to to provide this baseline for form project. The idea here is to make a simple approach which can everyone basically copy paste, which is maybe not that precise but a good starting point, and then a more complex approach for, yeah, practically break it down for for each individual system. So we have to to formalize a way that that everyone can utilize this and that we can help the projects to to get their understanding of their own power consumption. That's fantastic. So, for the survey that was done. Are you do you have any activities that are being planned as a result of the outcome of the that survey. So, we have to two outcomes. The one regards the survey is like to get a little bit better and the question which we are asking maybe breaking it into two directions, because we have seen that a large group of the participants either live more in just a pure cloud or they live pure in a real data center environment, and they'll be one or the other question do not really apply for the one another user group and then the survey results looks very, very different partially. So therefore we are thinking about to changing here the approach a little bit. Besides of that, we try to break down some. Yeah, initiatives out of it, as we see that there are some common challenges in like defining the starting point of how do we can make something valuable out of the approaches which we take to maybe reduce and optimize our infrastructure and how we can make it visible. Obviously, they can reduce some amount of the infrastructure but which impact does it have and sometimes region based for example can get very complicated at this point. But sometimes it's because of the region that ever run it in Germany the system itself I can optimize it as much as I want but currently the energy mix is not that good as like in Finland for example. So it sounds like there's still a lot of work yet to be done with that results. Always. Any other questions. Okay, moving on. contributor strategy. Hi, this is Catherine. Yeah, so for keep calm. We have our second kiosk this time and we hope and are that we are better prepared we're going to have a handout and some more things to get the word out. Because as you know it's really important that projects know about us because there's a lot of help here. And then just as a reminder for everyone, we have a keynote Don is going to do a keynote very excited about that about building a sustainable CNCF project and contributor base. And then we have a panel where this time we're going to talk about what we get out of this. And hopefully that will motivate people to participate as well we've been always talking about what the tag does this time we're saying like well, actually it's not only giving you get a lot of it out of it too. So new new strategy no angle hopefully will get more people engaged and then maintainer circle we're going to have a one at coupon. The exact name is not very sure but it's going to be about bringing end users into the project communities and gauge with them. So that's going to be on Wednesday at 11am. And then on the contributor growth site. We have a new page, which helps newbies to get started with open source lots of valuable information in there. And then finally live, we did a video talking about the contributor survey. It took a long while but it's finally live. So there is a link there please share with the community. And then we have a new facilitator, we are on Klein House is going to facilitate the contributor growth meeting a working group so excited about that and then we are participating in Google season of docs. We have Toranga kids day and coupon EU kids day. And on the mentorship side we have will have office hours on Wednesday at 230 and the repo is getting an update to make it a little bit more user friendly for mentors and mentees and then on the governance side, the team is working with the backstage project to get that to help them in that regard and then last but not least a quick reminder to everyone please encourage all the projects to reach out to the tech. We're here to help whenever you talk to them. Thank you. Awesome. Any questions for contributor strategy. Okay. Moving on. App delivery. Yeah. Hello, Alice here update on tech at delivery. First one we really up leveled our web property and by we actually we mean the tag together with tremendous support from the CNCF helping us to get this done so there's now a dedicated website for tech at delivery. So general information, the white papers and the blocks out there. So, very excited about this it also helps us to share our content better than we could do in the past and again also shout out to the support from the CNCF who helped us tremendously getting this done. So in April, this is now ready this was already sent out a while back to the various mailing lists blog post in the PDF version will be available by mid April so well before cube com targeting next week. And together with tech contribution strategy we're also targeting a survey link is here as well, specifically around platform engineering and how internal platforms are built. This is also currently looking into building an example platform. So the issues linked here as well this is still early stage the ideas showing people how you can use CNCF projects and can combine them together to build a platform because most of the building blocks are actually there. I think everybody's aware of the CNCF landscape made into a puzzle this is actually about assembling that puzzle and seeing how well the in real pieces fit together. Again the idea is not to create like the one platform, but to share examples of how you can use different projects together. So the initiative driven by open it ups initially, it's really but improved. It started as search ability for artifacts but now actually merged into improved metadata so how can I find certain artifacts in an artifact store. As we all know it's not just container images there is a lot of different topics. And this is also ongoing right now there's collaboration obviously with OCI or as and the artifact have to move this forward so the idea is that we had just have standardized metadata that you can use and the people hopefully also use that they can search the repositories and find what they're looking for this goes from everything from what type of artifact that you're dealing with how you name it versioning and so forth. So you, there's a meter plant on Tuesday. Now we can actually link to a blog and our fancy new website that we have where you know the details. We have a booth also in the project pavilion for discussions and meetups so we also inviting people to give like lightning talks and engage with us on specific topics so there's a dedicated calendar for this as well that's still under preparation. So there is also a session on cloud applications and by applications we mean application definitions platform and operators to covering the main topics we're working on right now. And under the other section there is still that one Google Doc that was started a while back on how do we define an application in Kubernetes. So we're sure that like lots of comments in there that go in a very different directions we're still working this in what we also discussed in one of the last meetings is that we're looking at how would you define an application using the various approaches that are currently available in projects. So not like starting the refers like what do we want it to look like, but what are your options right now where are similarities where can we, what kind of can we agree on. So basically this is taking the idea of like the standard application focused tags that you could use on your Kubernetes resource like one step sort of had to be fine like this is my application or more it's a larger atomic set. And then what you would have is this Kubernetes primitives very early stage. Interestingly everybody agrees on the problems like everybody loves the problem, but we're not yet at the point where we're clear what the solution is going to be going forward. That's it. Question. Okay. For individuals that are interested in contributing to we're getting involved in the package management metadata discussion. Is there an open issue on the repo to direct them to our Slack channel. So this one I think there's today's like discussion but it's currently the individuals but the issue I think is not yet. In this slide very slightly with a link. Awesome. Thanks so much. Any other questions. Okay. Up next projects applying to move levels. So we're going to try something different this time. We're going to be providing a little bit of updates on where things are at to ensure that the community has some transparency and where these are sitting. We understand that many of them have been in flight for a while. It's because we are actively working on multiple efforts within projects. Right now we've got artifact hub and active review. I don't see Dave on the call. Dave, do you have anything to add on that one? Um, no, the only thing I thought was I think last time we talked a little bit about how with artifact hub we had stalled for a while because we weren't sure what to do with this type of project. And I think since then we've kind of aligned with the TOC that. Artified hub should move forward in the process and we're starting to do that. I can't say we made a ton of progress but we're, we're getting there. Okay. Keycloak is currently in voting. So folks that are interested in supporting the project moving levels, please check out the mailing list message and you can always plus one to show support for the project. Erin, are you on today? Erin, you're not with us today. That's right. Okay. Kubeflow, Ricardo, an active review. Don't see Ricardo on the call either. So, okay, move on. All right, flat car, Duffy, Nikita and Katie. Yeah, I can talk about it. So like the flat car folks shared DD doc with us a couple of days ago so we're going to be reviewing it asynchronously. We also planning to meet them at like in person at KubeCon and the Tagrant time meeting so actively talking to them and it's an active review as well. Alright, GRPC, Justin. I've reached out to April again. I haven't had a head back but I'm going to write up a document about the about the things that are open issues which are mainly around around governance and how we manage that which has always been the issue but I'm trying to arrange a meeting with April. If there's a better contact, I think it's still her who's the right person. I think so too. So I think you're running down the right way. Yeah, yeah. Let me know if you need help. How's that? All right, Cryo, Kathy and Nikita. Yeah, so we have completed all the user reviews and I think we are wrapping up when the KubeCon ends. Yeah, I think it's ready for public comments. Alright, and Kita. Oh, okay. Kita is a user review stage. We have completed the review with Microsoft Azure and also Cisco. We still have, you know, another tool to do. Yeah. Recargo, would you like to add anything? Kita? It's Recargo. He's not on today. Okay. Yeah. And also for the Cryo, yeah. Nikita, do you have any input? No, I think that sounds about accurate. Okay. Okay. Silyam is, we've completed all the review and it'll go to public comments sometime after KubeCon for Falco. Justin and I are meeting later this week to go over a final review of the project to make sure that everything is in order to move forward with it. Istio is currently in active review between Nikita and myself. Nikita, do you have anything to add? Not really. I think we'll be doing reviews or synchronously for an hour and starting at the center. Okay. Anything else? Amy, did I miss anything? Oh yeah, I think, you know, for Kita projects, Recargo is also the TLC sponsor. As a quick update, we did make the community aware that on April 4th, which is today, we will providing some updates to the request on moving levels and making some changes to that process. So please keep an eye out in the Slack channels as well as the mailing list for an update on that or just finalizing the messaging on that currently. Does anyone have any questions for the TLC? Matt? I had a brief one, more of a clarification just based on some of the chat I was seeing. To be clear, the working group that some community members came together around is not to define the language. It's to do activities such as a broad survey of existing languages, both vendor and open source attributes of those language, what is important to what different kinds of personas. Basically to do all the background work necessary to inform the potential creation of a spec that would be ostensibly in a different open source project. So the scope of this work group is really the free work for that in an open way to kind of gather the supporting materials so that it can be informed. I'm being repetitive. I just want to make that brief clarification. Thanks. Thanks Matt. And if it's not already on the issue where you're tracking the working group formation would recommend just adding that language in there. It is awesome. Anything else. Right. Well, thank you everyone for joining us today. We will see you next time. Thank you all. Thank you. Bye.