 Hello, everyone. We're going to wait just a few more minutes to allow folks to join. Amy, we're up to 15 participants. Should we get started? I was going to wait a little bit. I was also trying to figure out who was signed in as TAG Observability. But given as they seem to have dropped, we can go ahead and rock and roll. All right. Let's go ahead and get started. Hello, everyone. It's June 6. Thank you for joining the TOC public meeting. As a reminder, we are all in compliance with the antitrust policy notice for this meeting. And if you're here, you've found where we're at. The meeting logistics are on the screen. They're also in the TOC repo. Next slide. We have several TOC members here today and we'll be doing some updates from the tags and then any additional questions for everyone towards the end of the call. So let's go ahead and get started with tags stored up. Projects applying to move the hoodles. Moving this one up to be a lecture that we get a chance to be able to cover all of these. Yep. Artifact hub is still an active review from Dave. Do you have any additional updates? I do not have any additional updates from before. I think we're still working through getting the due diligence together and ready to go. Awesome. Thanks. Thank you. I don't see that Erin is on the call. I know that she is still working on it. Cube flow is in public comment. Flat car is still an active review. Duffy, Nikita or Katie, do you have any updates? I think I'm sorry. We just have to, I think we have to sync and kind of move that thing forward again. Okay. Ricardo open your. Yeah, but he's just picked this one up. So I expect for the update from him. Yeah, so expect that one to be kicking off soon. Justin is still working with your PC on upcoming changes. Justin, do you happen to have an update? We have a meeting scheduled. I think I can't remember exactly. I mean, when is it? Yeah. Cryo, I believe goes to voting today. Is that correct, Amy? That is correct. We are public comment moving to a vote. Awesome. Kata is in public comments. Sillium is still with the license scanning team under licensing review. Falco, we're working on the project for some focus areas to continue to move them forward. And Istio is in voting, which I believe wraps up soon. Is that correct? We're real close. So I'll be sending out like what votes are currently open today. Okay. Awesome. TSC members, please keep an eye out on your email for open votes. All right. Let's get started. Great to see so much movement here. Now we can get text storage. All right. Sorry. Do you mind if I just ask one thing on that last slide? Go ahead, Craig. There's a quite a lot hidden in that last sentence there that says projects waiting for sponsors are on the meeting minutes doc. I did note that there were three or four projects that have been waiting now what seems like six months. I just wondered if there is any plan on having more visibility into allocation of sponsors or when those will move forward. So that in voting currently and when they complete the votes, then those sponsors are been available to be able to come take on new projects. Yes. Yeah, so I'll add on there. Craig, we do have the incubation and graduating projects black backlog on the TOC project boards. We're going in through those trying to identify projects that have been in the queue the longest between the two of them. We're actively working through things. All TOC members have been advised that as they are starting to wrap up and turn projects over to public comment, take a look in the backlog, which ones have been in there the longest, which ones align with background. If you have that luxury to be able to do that depending on what we have and then figure out which ones you're interested in taking on next. I've already talked to several TOC members who have got a few projects that they're they're looking to pick up as soon as we we kick some of these out. I will let everyone know that in order to ensure that TOC members are not over committed and being distributed too thin amongst all the projects. We're trying to enforce a to project cap on TOC members to try to distribute the work as as thoroughly as we can and try to get these things moving forward. So if you have any questions on a status, take a look at the project backlog boards. We're trying to keep them up to date. We apologize for any incorrect information that was on there in the past, but we're working through improving it. Thank you. Yep, not a problem. Alright, tag storage. Okay, hello everyone. So a few updates on some of the projects we've had quite a bit of activity on a number of different projects which are looking to join the CNCF and presenting. So I'll touch on those first cloud native PG had previously applied for sandbox and is going to be reapplying they are a an operator Kubernetes operator for Postgres that manages the entire lifecycle of databases within Kubernetes and also does things like replication and other failovers and high availability. So it's particularly interesting for moving safer workloads into the Kubernetes environment. Pelican is a very interesting project in that it is an exceptionally mature. caching subsystem similar to memcachity or redis for example, and used to be part of the code base at Twitter. Due to some of the things that have been going on there, the entire team has moved on and they've also open sourced their that code basis as a result and has some it has some particularly interesting cloud native applications. So they're looking to to consider joining a sandbox. Xline is also very innovative. They are deploying new consensus type protocol called CURP, which is designed to remove some of the latency that we have in things like the raft protocols, typically, and their idea is to have a strong consensus key value store, which also has an SED compatible API. So there are some interesting use cases for that there. And when we store is a local volume, local volume manager, PVC kind of products, which are projects which allows the migration of pvcs between between notes as well as as well as local storage management, which which again is kind of innovative because we haven't seen the sort of data movement aspect than any of the other projects like Karina, for example. Other than the projects. We've also got a bunch of work on going around some of the white papers that we're working on the white paper database patterns is has a lot of content has been completed and we're now in a review phase and sort of plugging a few of the, a few of the gaps. And that's that's actually what's taken the bulk of the bulk of the of the work so far. And we continue to have some upcoming presentations if anybody's interested to join the next couple of calls on projects for we have a presentation around sustainability and storage, which could, which could have some sort of wider interest and another presentation on Kayap, which is a backup project, as well as some other projects coming up. Some some project updates coming up like for proof you go. And then finally, we want just want to remind everybody I've sent an email to the to see mailing list that we're proposing. Rafaela Spatsoli to join as a co-chair for the tag Rafaela has been working with us for a number of years now and was previously a tech lead for the tag he's authored a number of papers and being a presenter with us at cube kind of a few times. And it's very, very highly recommended so please send your plus ones in. Yes, when did you send that because I missed that. About two hours ago. Oh, okay. All right. I haven't seen it. Okay. Okay. Wonderful. Wonderful. I will add that into the co-chair nomination, like the votes currently outstanding will treat that like a vote. Excellent. And Rafaela would be replacing Quinton who's he's sort of stepped out from the storage tag. Okay, does anyone have any questions for tag storage? Okay. I have one and then a request for the paper review that you have on database patterns. Did that go out on the to see mailing list to solicit more reviewers. It has not, but we can do that. Okay, I would recommend that just to get more visibility on the on the work that this group has done. And then the use case template for storage projects. Are you all looking to contribute that template as an optional template on the contribute.cncf.io for those projects? That was not something we actually discussed, but it's something we probably should consider. Actually, that's a good point. Okay. I don't have any other questions. Right. Next, tag security. Hello. So I'm pleased to announce that we have proposed a nomination for our next co-chair. This is replacing the long standing and long serving Brandon Lum, who's, who's just about finished with his term. That is currently on the TOC mailing list for feedback. Secondly, there is a proposal to spread out the chair terms via a nuance of originally how additional co-chairs were added. We are due to have a rather than a finish within the next month or so, which would mean two chairs rotating within very short succession. So this is a proposal to extend her term by another couple of months. So there's at least three months between those rotations and just ease the new chair into the role as supported by the tech leads who have done a wonderful job so far. We have some new publications. So thanks to all the Italian speakers who have done a sterling job of translating the cloud native white paper V2 into Italian. That is now finished and published as of four days ago. And secondarily, we have a proposal for a Chinese translation underway that is currently inviting contributors. And a number of security reviews on the way through. First of all, we have Pixie, which is EBPF flavored. People are interested to jump in there. We are looking for, again, additional security reviews in there. I think Justin Kappos will be leading that one for us. We also have flat car. Flat car is quite a large surface area, let's say, being a full distribution. It is more than we would generally see with a specific cloud native application. However, we had an introductory meeting with the team and spoke about downscoping to very specifically the portions of the system, which are high risk where escalation of privilege might be more of a concern. And of course, on the understanding that it is a mature and well used project. So a little bit out of scope for a little bit beyond the scope of what we normally do, but nevertheless, something we're willing to jump into. There is a proposal for a fuzzing handbook. So this is looking at some of the work, especially around the data logics fuzzing across the CNCF project portfolio. And we're looking probably to add this in to the supply chain security white paper, just as an additional piece. Again, looking forward to a presentation on that over the next few weeks. And finally, cube flow are coming through as well. I should add that we have been traditionally doing cadence of meetings. Initially, every week on US time zone, we then stood up the EMEA meeting. There has been some diffusion of contributors across those two time zones. So the goal of the tag is now to maintain that weekly cadence in North America on the North American time zone while also maintaining the two weekly cadence of the EMEA team, which has probably half to a third of the number of contributors. But as some people move around the world, they kind of switch between different projects. So trying hard to avoid split brain, making sure everything is well documented and we have rigorous meeting notes to mitigate that. Thanks, Andy. Anyone have questions for tag security? No, I just wanted to thank the tag security for picking up the security reviews for the projects because Pixie as you know has already presented in the tag of the ability and we've been working with closely with the team for, you know, getting them lined up and ready for review by the TOC for incubation status. So thank you, Andy for and to the tag community security community. Ricardo's got a second on that thanks for picking up flat car. Andy, while we have you a quick question, as I understand that you all are always in need of security reviewers to support and assist this because it is a volunteer driven activity, I assume that is still the case. And if so, is there any security review resources for individuals that may not have a security background but are interested in learning more and how they can assist tag security and reviewing these projects security posture. There are indeed and thank you for asking. We have security review guidelines. I will drop these into the chat now as well. I would also recommend sending out a message on the TOC mailing list with the open call for security reviewers and a link to what you just dropped in chat. Hopefully we can get some more community members interested in this space. Yes, I appreciate the nudge. There's one more thing in this space which we have considered. We tend to experience individuals being involved in contributing in their line of business interest, let's say. And we have wondered if we can open that up more broadly and ask people if they can contribute maybe to the proceeding or the following review once they have a feel for the way that we pursue the minutiae of how we undertake the thing. So, it's an open discussion attack security right now, but yes, we are very keen to bolster the roster of security individuals. In fact, Emily, thank you for calling that out because I just wanted to call out that the secure the open telemetry project, which I actively work on is, we just created a security work group, which is, you know, related to open telemetry and looking at security use cases for observability. And again, Andy, I think perhaps, you know, those two team groups can collaborate to support the tech security so I'll get the word out for sure. That would be fantastic. Thank you. Sure. Thanks, that's great. Next up, tagger in time. All right. I don't know where are the projects and presentations, you know, like, I think there's something went wrong with presentation. So, let me try to find another. Okay. When you get to it, that's fine. Actually, I can see it here. So I'm not sure why it's not anyway might not be rendering today. Yeah, no words. So, going into the project and presentation that we have, we have a couple of projects that in graduation in graduation process, and they are in public comment. And CRIO. Now the Q flow. It's still in initial in the review as well. We are working on that. And we reached out to another project which is a slim tool that tool kept. We didn't hear back from them yet. Hopefully they can present as soon. Moving to the workloads and the Kubernetes projects. So, Carmada is has already presented in the tag runtime, and they are waiting for a sponsor from the to see. And we had to sandbox projects that have been accepted which is kept her and the keep service tech. Here as well we are working to make sure they, you know, like they already covered all the information that the to see asked, asked them to provide. And yeah, we have in the next meeting, we have the Q clipper project which is a management system, Kubernetes management system, they will present on June 15. Moving to the activities. First thing we wanted to. We wanted to, you know, like discuss here or you know like letting you know that the session in keep calm EU was very productive and that co chairs have a lot of successful. We were talking and people were so interested on meeting them and the talking it to them during the session so the tag is planning to have another one for keep keep calm in a, and hopefully we can have more in the operating sessions as well. We will try to plan for this and we will let you know once we have a draft plan. Another two working groups, still in progress, which are the ml ops and working group. We didn't have lots of, you know, like progress in this yet. Because we have like the weather working group, we're working on the weather working group, hopefully the charter the drafted charter is almost ready so we will send it for to see review, hopefully this week. We already nominated the co chairs and team leaders based on people interest and, of course, we took lots of other other other factors into our considerations and we had a meeting already. Like time and date, and hopefully once we have the to see review and everything is good, we can start to kick off the first meeting for wasn't working group. And yeah, it was, it was so, you know, like, so happy to see it like the wasm con is the thing now and it will happen soon so it, it think up with the working group hopefully we can do more work together. Moving back again to the patch system initiative. The team had the pretty consistent chunk of work, and they are making a good progress to to reach to the landscape phase which, which is pretty excited. And therefore the other working group the IOT and cod, we didn't have much updates on these working group hopefully we can have something to share with you in the future. That's fantastic you all have been very busy. And yeah, for a couple of months I don't know what's happening but you know like lots of projects lots of events, which is happy thing. Any questions for tag runtime. All right, I certainly don't have any you all are doing great work. Very busy. Next. And now it's loaded tag observability. Right. Hi everyone. I wanted to kind of run through some of the really cool stuff that we have been doing in the tag observability and the first and foremost. Thank you to to see for proving our request for work group on the query language standard work that you know different groups are interested in Netflix eBay as well as Apple. We have been looking at some of the use cases where convergence of multiple languages in the industry for observability are leading to more discussion around how there could be a baseline, which is a standard set of again, just standard set of syntax right so based on that the query language query language work group has been set up. We will reuse the CNCF tag observability time on the day on the weeks when the tag meeting is not held. The tag meeting typically is on the first and third Tuesdays and the work group for query language discussions will be held on the second and fourth. We have already had the first discussion. A lot of folks attended very good representation both from end users as well as from different vendor teams that have been involved. That's very exciting because again this is an and I stated the word group goals on the right hand side as well as the non goals. Obviously we are not looking at defining a formal standard or implementations that's up to the. The project spin up based on that that's up to the projects to do what we want to focus in on in this web group is really looking at a variety of use cases, capturing you know what some of the end user pain points are, and the use cases which really require complex queries often for observability data and just looking at telemetry models and establishing and documenting that. We also plan to interview query language designers from different groups within the CNCF ecosystem as well as problem different vendors, and this and also survey, you know, multiple end user groups have been super interested in, first of all providing feedback and also hope to inform the diversity of observability use cases that exist right so again super exciting. This is something that will be ongoing. So, again, please get the word out if folks are interested, whether that is security use cases or. Yes, specific use cases or others again. This does intersect your feedbacks would be invaluable. Just wanted to call out a couple of projects on the observabilities side again thanks to the tech security for doing you know conducting starting the security review for pixie. We are also activating to see guidance on assignment of a sponsor for starting to review pixie for incubation. And the second project which is also in the wings that has just started is open cost which kind of falls under the observability domain, because of a lot of the metrics that are collected. So cost management and configuration management which is typically you know an overlapping area of its observability. Meetings and highlights we do have pretty good participation in the meetings that we have twice a week, twice a month I should say, and Matt did you want to go and deep dive into that we had a super cool. Yeah, thank you. I think over the last few years I've built up enough negative karma with talking too much, so I will try to be brief bright and gone. In this case, but yeah last in our last meeting the video has just been posted. I am right from coming all that came to talk about an MIT open source project called coin.io it is a streaming graph interpreter. I've mentioned this in the past and we finally got him to come. I highly recommend giving the talk a lot of giving the talk a watch. It's about 35 minutes are, and it starts with the theory of observability that goes back quite a bit deeper than an older than you might think beyond. We're getting kind of control theory and with its roots and philosophy, you know about how we observe the world around us and all that, but really the focus is on streaming graph interpreters which are in a nutshell something like spark, or something would sit between two streaming pipelines of events, and it, it gobbles up little events and makes much bigger events out the other side. There's a critical difference being that there are no timing windows, because rather than all of the events that need to be matched up as they come streaming in, being bounded by how much memory or storage you have on a machine, rather, it's a stateful durable graph database backing that buffer if you will. So streaming graph interpreters have a lot of applications I think in observability in particular cloud native observability to the high cardinality and the nature of Kubernetes observability so the talk ends with a demo of using coin to understand what's happening in a cluster. So, that's that. Cool. And that thank you for diving deep in that again for those of you who are interested in streaming graphs. This is super cool talk. I just wanted to call out attention to a long term pending request from the open telemetry project again trying to figure out you know what is the best process for reaching out to the CNCF legal team as well as the to see for reviews of different licensing requests or community requests that come up right and and we did file a service desk ticket from open telemetry a while back, and it's been a few months. We have not heard back on the ticket from the legal team so maybe Amy you can guide us in terms of what the process is there. So there's a couple different things going around. I think for licensing request it's best to be able to use the foundation repo, but we can take this one offline. Okay, a lot of different pieces running around in here. Okay, thanks Amy. Awesome. And that's all we had for the update. Thanks. Any questions for tag observability. Okay. Next. Tag environmental sustainability. Hello. So we organized actually a wire back I think a month ago, a getting started meeting, which was quite nice with a couple of new folks, I think around 10 around 10 new faces. And we will work on those slides over time and then have again getting started meetings after each major conference so every time we expect a lot of new contributors or new folks are interesting in the tag. We will organize a getting started meeting. We published a blog post. I think two weeks ago. It should be published today. Also on the CNCF blog. So we have it on our website already. And it should also be published today or tomorrow. So it's about cube corn and cloud native at cube corn, basically, and we had a couple of sections in the blog post where we had interview style questions and folks from the tag answer those questions. So I think this was a very nice idea or or thing to get folks from the tag involved in a blog post. They can quickly fill out a form answer those questions and they appear in the blog post. And we also organized or invited the author of the scarf under project. The scarf under is a similar tool or project as Kepler but it has not this. It's not bound to communities as Kepler is it's it is just like a resource which you can deploy anywhere, but it's governed under different organizations or different foundation. So this was a very good demo for us to know a little bit more about the tool itself, but also to get a connection to to the author and also to to the other foundation potentially. We published a couple of months ago and we've talked about it and the cloud native sustainability landscape document. And it has been translated to Korean, which is very nice. So we see there's some some eyes on the document and with with time potentially we will also include more different languages but this is like on like if if a contributor steps up and has interest and we have to support and we're happy to include more languages. Also, and we have been talking in the tag about this for quite some time because at the moment a lot of our efforts are focused around communication and and so on. So we have been starting and creating an issue about the working group around communication, which I think is is a very good step. And the issue is, I think has a lot of thumbs up already but it's still under discussion, I think. So we will, I think, wrap this up soon soonish. There's also been an effort to maybe organize a hackathon at the next QCon. This is that by by max we organized last week a meeting with some folks who are interested in this effort to discuss maybe different projects which we can which which are fit for a hackathon. So I think this is very interesting. There's also another effort about organizing a cloud native week of cloud native sustainability. The idea is that we use the community groups. So we have in the CNCF all those chapters, they organize meetups. And we have this this network and the idea is that we leverage this network and that we organize in a particular week the second week of October, all around the globe cloud native meetups around the topic of sustainability. And we already have over 20 meetups interested or organizers interested so it looks to be quite quite of an interesting event. We will have in the next weeks and months, some session around organization so we can support those local meetups in the best best way we can. So very excited about that. We have also invited the green software foundation. This is not on the slide here but I updated. I updated, I think the slides a little bit late, but we have invited the green software foundation to join our next call tomorrow, which I think is very interesting. There are obviously a lot of expertise as well in the sustainability space. So having like a stronger bound to them, I think makes sense. We also were thinking about maybe having like a role like an ambassador role that somebody from the tag is joining the green software foundation calls and giving us an update. So we are kind of have like a better loop or better understanding what's going on in their software foundation and their foundation. But maybe this is like something for the future right now. Not sure if somebody has time to do that. Also, we have been working on refining governance and guidelines. We pushed a new process around reviewing blog posts. This has been a problem a couple of months ago when we first had a blog post submission and we noticed that we are missing guidelines how to review it and it was a little bit messy. And now I think we have a very interesting process. Maybe something we can also document in the best practices effort. There's like another issue open under the TSE. So maybe this could be interesting that you and the last two things we have been also talking about tag roles and like a leadership ladder because some tag members are interesting in moving moving up roles and have different leadership roles. And we've been also talking about the host playbook. So how to organize a meeting and so on. Awesome. Thanks so much Leo. For those of you that are interested in learning more about that hackathon definitely check out the issue link there was a lot of great information and discussion on there. I think the folks in tag observability might be interested in checking that out. So, Leo, thank you so much. Any questions for tag environmental sustainability before we move on. Okay, next. Tag contributor strategy. Hello everyone. We've made really good progress. Dave Sudia in particular has made really good progress on revitalizing the maintainer circle so this has been exciting to see so we held one with with Nate and Lee just a little over a week ago. And we have one coming up on community management with Paris Pittman on the 28th. So we'll be announcing that one soon if you want to hold it on your calendar that would be great. We also have some really interesting things coming out of the mentoring working group that are pretty exciting so Catherine Paganini has been working with a university near Washington DC, which is a university Gallaudet Gallaudet. I'm not sure how to say it. Thank you. So it's, it's a university for for the deaf and hard of hearing and so she's working with them and meeting with a professor to, to look at how we can make our communities more accessible to contributors in the space. So any community members who are deaf, hard of hearing or fluent in American Sign Language, and who are maybe interested in collaborating with us on this effort, have them reach out to us at tag contributor strategy we'd love, love to hear them and their experiences and get more people involved in this, this new initiative. So making really good progress on in that the work that Jay Tolima is doing with the Maori in New Zealand, and some some work with government initiatives to to help them move into careers and the cloud native space. So that's part of kind of a national national program to get more, more native Maori people into IT careers, and in particular in our case the CNCF. So that also is really, really exciting to see on the governance side we've got some governance reviews in progress so we're doing governance reviews for Istio and telepresence right now. So in the last group we updated our slides a little late. So if you go back to the slides later, you can see that we've added a few things to the general section in particular we have new tech leads. So we have Ali Ok and Rian Kleinhans who are stepping in to fill Carolyn's very big shoes after we we lost her. So they have been stepping up and doing a lot of really great work within within the tag. So I wanted to recognize that by moving them into tech lead positions. In particular Ali has been doing a ton of work on the contribute.cncf.io website, and in particular, upgrading some hugo versions and working on how to migrate some things that were unfortunately running out of Carolyn's GitHub accounts and so we're using the process of working to sort that out and working with some folks at the CNCF. Rian has been taking the lead and working on our tag contributor strategy roadmap so that we have a better feel for what we're working on what's coming next and how people can get involved. So there's also a lot of great work happening there. And then our friendly monthly reminder that any CNCF project is welcome to come and talk to us if you want some help with governance or building your contributor strategy growing your contributors. So feel free to drop into any of our meetings slack channels mailing lists, you know if your projects need some help. Any questions for the tag. John, I think I had a question about getting the contributor tag contributor strategy, you know team, more involved in the projects, the opposite way that is can we invite you for example open telemetry and, you know, is a very large project. You are, you know, folks from the tag contributor strategy to come and speak to the to the GC and the TC, for example, right because we have a regular meetings but typically what I've noticed is that most projects don't go to the tag contributor strategy. It's kind of isolated and separated out. Yeah, maybe you know having more presentations into the projects themselves might be, you know, useful to get more books involved. We have a whole community team that you know and a group that works on the project itself. And there's a lot of activity that comes out of that community group but they could benefit from you know actually working with the contributor strategy group. Yeah, we'd certainly be open to that I would say reach out to us on on our slack channel or the mailing list with when the meetings are and maybe some some idea of some of the challenges you're facing that you'd like for us to talk about. And then we'll we'll see if we can find somebody who can who can come into your meetings as well. Awesome. Awesome. Thank you. And you know projects that are having particular issues or want to review on something or maybe they're updating their governance and what some advice are also always welcome to just file issues and tag contributor strategy and we can deal with those asynchronously so you don't, you don't have to pop into a meeting if you if you've got a question we can, we can deal with some of those via via issues as well. Okay, that that makes sense. I mean, again, all good. It's just more that you know there are often a lot of discussions that the community repos for example on hotel are very active. Lots of different discussions happening there but they don't, you know really they stay centered in the in on the project itself right and books typically don't intersect. So I'd love to see more collaboration there. Yeah, that's a good idea. Thanks. No, totally. Thank you. Any other questions for tag contributor strategy. Okay, I have a recommendation for everyone if you're a tag chair or a technical lead or a maintainer of a project you're interested in becoming a maintainer for a project at some point in the future highly recommend going to that community management session with Paris Pittman keep an eye out from tag contributor strategy for information and details on that even though it may not be immediately relevant to something you're working on. There are always good sessions to understand what is going on in the movie and the rest of the community some of the community concerns that different maintainers are encountering. So highly recommend that. Right. Next. And there's a maintainer circle slack channel, which is where all the announcements get made so if you're not already on that that's a great way to get notified when the meeting gets scheduled. Definitely. Thanks, Don. All right, next up. App delivery. Yes, ma'am. Here I am. So, I'll just walk through this. We have opened an issue for chair elections. I'm not a chair right now but I nominated myself. I'm kind of the chair right now. So I'm definitely looking for more contributors. I'm a little concerned that I'm the only one that's nominated myself there I know it's a big domain. Maybe some of the leaders from some of the related groups want to like a native or things like that month propose themselves. So yeah, check that out. We do have a project presentation with litmus chaos coming up. We have a meeting frameworks currently fall under our purview. We had a discussion with CD events from CDF a few weeks ago and I just wanted to make sure you all saw that. We tried to identify ways we could support CDF and CD events continuous delivery foundation. I don't know. And CD events is a major project from them. I think that's a couple of things. I think they want one of the things they asked was about patterns for integrating events and reacting to them and I kind of said I are serverless working group which I always have my eye on most about cloud events. Ask them to talk with them some to continue me through the list are we G so we G is just what I call working groups artifacts. So we've had some productive couple meetings after our you know initial back and forth asynchronously. The charter is is ready for review I opened the elite well one of the leaders opened up PR in the tag repo and I opened the thing that talks today so take a look at that see what you think. And there's a lot of different examples of forming we G so. And there were a lot of opinions in the meetings to so I'm sure there will be more in the PR so comment there if you want to change or need more info. We did want I'll bring up this ask because I'm probably going to open a service desk ticket for it. We probably need to get repo. I think media types for artifact schemas. So, I'll probably open a service desk ticket for that. So, rather than, it'll be better than the folks going and just creating a GitHub word is the feedback. Because if I if I see it right, this is asking for being able to help gather OCI pieces as well. Media types. Yeah, so it applies. I'm worried we're going to be crossing streams here and I want to be more clear about it but we can, we can take it offline. Yeah, we've been discussed OCI has been involved in these discussions and some of the OCI folks are in the meetings, and we actually put in the charter explicitly how we intend to relate to OCI. They're pretty supportive of it. It's, you know, the work we're doing is bottoms up effort it's not to set a spec it's more to gather. The fact is that people don't have the motivation to register all these media types of IANA. So we're trying to bottoms up gather them together find conventions and eventually it might affect it might affect OCI artifacts to O or OCI image spec even to over some discussions within OCI. Cool. It's a pretty cool way to partner with them because they're mostly on the spec side and we're mostly on the software side. Okay, continuing down the list we G platforms. Yes or tell us it's part of or tell us but it's the same folks I mean and porous is interested in content addressable discoverability for all things but I'm encouraging them to focus only on software artifacts. That's actually how OCI works internally. It's just content addressable so. Yeah, yeah there's the there's always the CDF and CNCF and that kind of stuff OCI. Let me move on to the next one. We do platforms so here is a lot of stuff in development because I need to push it along a little bit more. Some of our folks are in depth on that we want to push it forward maybe have it ready by Chicago. Korean translation I think the same person that did the environmental sustainability to ours but we haven't quite figured out how to get it merged in there yet if somebody wants to. It's really almost done it just it's the Hugo figuring out how to negotiate them. The platform survey is live. We haven't got a ton of responses and to be honest we haven't really promoted it. Yeah, I mean it's just we need some help if folks want to help promote it's been on my backlog to write a blog post about it and explain what we're doing. But I haven't done that yet newsletter marketing same thing actually this is really good I just talked with some of the folks that are interested in this and we do have a few people that want to. In a vendor neutral way share you know information about application development and delivery on Kubernetes. And so they're pursuing ways to share, you know the stuff that comes to our tag and some of the projects that we're working on working on like potato head. We want to share this last bit which is within from the platforms group which is, you know, probably accomplished a lot of the core of what it wanted to do. But we want to continue somehow pursuing synergy standards conventions reduction of complexity for platform API's, you know, the ways that you actually call the platform for portals where there is some confusion in the industry and some of the examples are meant to do things like backstage, and secrets bindings management which comes up frickin every conversation I have. But it's, you know, there's not that much money in it, frankly, I think in solving the problem it's hard to get everyone together on there's about 20 different ways so that's definitely been an hour. You know, we're trying to find ways to tackle other open issues so you're passionate about it. You're passionate people to, to simplify these domains. Last thing cube con Chicago everyone else mentioned it so I'll mention ours to we've run, you know project meetings for the tag at the past couple cube cons and they were really good for facilitating learning about ideas coming from each project. You know, some cross validation collaboration. I noticed that the pre day events are proliferating. We seem to be as twice as many in Amsterdam is Detroit, maybe there were much more before the pandemic I'm not really sure. But where I was thinking about a lot of those are app delivery projects, and so I was thinking about trying to coordinate that a bit most of them are only an hour or something anyway. So that we can all attend each other's and learn from each other's. So maybe that will transition into that. But with with folks so it's five months but it's it comes up faster than you expect as five months from today. I think Josh that's very helpful because again, I have you know we've had the same issue where their project meetings on the pre day at coupon and typically they're all at the same time. So, you end up not attending the office. Yeah, and in fact, you know I was kind of thinking because I don't know if you all have heard but there's a proposal for an app developer day on that day, and I was thinking about how that fits with the project meetings does that negate the need for them. But I've actually been thinking like that event is towards end users to the, you know the people that come in and want to learn, whereas this these project meetings. I don't know if end users want to come that probably indicates that they're pretty powerful and user anyway, but it's more oriented towards the project maintainers and the leaders to introduce them to each other. Yep. I mean, I think both and both are valuable. We're having them on the same day. We have the same issue with observability also because we have the observability day on the same day as the project meetings and everything else so it's typically difficult to pick. So, at knowing that that's difficult and having done the schedule a few times for cube con. If you both could take a few moments and type something up and paste it in either the TOC channel or the tag chairs channel concerning like scheduling conflicts associated with cube con and we'll make sure that that is sent over to the events team and the co chairs for when they're aware and mindful of it when they're building out the schedule. Sure. Emily, you can definitely Josh and I can coordinate for sure. That would be fantastic. And just file an issue on TOC repo. I just posted in the Slack channel. I'll direct them to it. Awesome. Thank you. Any other questions for tag app delivery. Okay. Any other questions we've got three minutes. Okay. I appreciate everyone's attendance today. I look forward to seeing you all next month with some more awesome updates. Please have a safe happy and healthy week everyone. Good to see you all we do sandbox review next week. So new sandbox projects. Cool. Awesome. We'll publish it. We'll publish it after it's it's done and votes open. So, hooray. Thanks. Thanks. Thanks. Thank you. Thank you. Bye.