 Hey, and good morning. We've got a few folks on the lawn here. We'll wait our traditional three to five minutes We do not actually have Liz today, so I will be playing the part of Liz It's gonna be a good time Hello and welcome Justin Cormack who has turned on this video and I can see it. Hello Welcome welcome. We'll do full like, you know, happy welcome time You know as we get all the way through here, but and good morning Hello Lots of folks joining in and we're only two minutes past so I'll give it a few more minutes in here. Thank you I'm holding a little bit because I don't yet see our first group on the line for six George yet And you know, it's fun. It's after so be able to give them a second. Otherwise read their slides All right, it is five afterwards in here. So I think we will get going I know we definitely want to be able to welcome our new TOC members and kick off our New group here. So we'll just go ahead and get started Assuming that everything looks like both two there goes our normal and I trust policy notice Our meeting logistics because this is where you all are and here's our TOC members present today Welcome to our new TOC. We are now at the point where we now have 11 of you Yes, hello. Welcome. Welcome Now it's your time to be able to like, you know drop in a couple notes in here. I see a few of you here not all at once Welcome everyone so excited to work with everybody who's just coming on board Yeah, and this marks our first meeting of the term you all officially are established is like real members This is now our official TOC So part of this is also being able to let the community know that if they are looking for people to be able to help sponsor either their SIG or some of their projects that these are the people to be able to go to and You know, that's that's basically it Yeah, Tristan said anything from you guys Yeah, just want to say hello. Thank you very much to the maintainers for Appointing me. I think it's really exciting that that we've got a maintain a position that's rated for hold by the maintainers because there's extremely important important people in this group and If you don't know me I'm always happy to talk to people. I'm based in the UK, but I'm in the in the US a lot so Feel free to ping me and I'd be love to talk to you On the same note, I'm not sure if everyone can hear me But hi, my name is Katie and I'm very very excited to be part of the TOC Member board. I'm looking very looking forward to collaborate with everyone and I'm based in London as well So as previously mentioned, if you have any questions in regards to anything, I'll be more than happy to help Yeah, hi, I'm I'm Shen Shen Leon. I'm based in a Bay Area, Cupertino really excited to be on the TOC I've been working with the You know Kubernetes and a lot of folks on the TOC for a few years. So so really excited Hello, everyone. My name is Todd. I am also based in the Bay Area very very excited to be part of the TOC And feel free to reach out to me. My email address is there very excited to Listen learn understand what problems folks are facing and look forward to helping work with this community to address those And Cheng unless you're already gone. Yep. We're good. All right. Lovely. Good to see all of you Thank you so much. Yeah, we will be seeing all of you for The new people who are stuck here for the next two years. Thank you very much So, all right our agenda We've got our normal SIG updates I'm hoping to be able to have some process updates at the end of the time as well And we have some space for any other items of business. So With that I will hand it off to storage which has a lot to say today. So please go ahead Hi so So first off we are As you as you're aware, we had launched our storage Landscape so the 18 months ago now. We're planning to do a 2.0 release And this is going to incorporate The latest database editions that Sugu and his team have been working on And we're just about completed there in the waiting review and we've also had a revamp of the management interfaces section to kind of reflect the changes in the ecosystem over the last couple of years And the idea is that we'll be reviewing this next week and then merge this into the Into the into the mainline doc and publish the 2.0 doc for kubecon The performance and benchmarking white paper we had had a bit of a lull over Over sort of Christmas and it's the new year But we've now added a couple of other authors and the drafting and testing is in progress And we're expecting an updated drafts next week as well We've had for the storage use case library, which which is a reminder. This is this going to be a library to cover best practice and Different options for how to deploy storage for for different use cases where we've come up with the first set of categories that we're going to be that we're going to be working on and we'll have updated templates Shortly again, we want to launch the use case with the first five or six use case categories for kubecon We've been discussing the the Process and the template for sandbox and incubation processes Erin has put together the Merged documents From that that were available from the different templates in the different six It would be really great if we could get to reviews and comments on that and I suspect obviously that that will be the topic for the talk and sick chairs meeting to And then finally we we we reviewed dragonfly including installing it and doing some sort of basic failure testing And we've said we've sent feedback and clarifying questions back to the project team As soon as we get the responses for that will incorporate it into the due diligence document and Finally project harbour the storage elements of harbour are due to be Are due to be reviewed possibly at the February 12th meeting depending on how the sacred time Review is is proceeding that's it for me All right, any questions anything else people want to be able to ask about this We are likely going to talk about the process template at the bottom of the meeting as well Oh, I see something in the chat from Josh Talking about benchmarking and Kubernetes. Yes, I'd love to hear from you Josh Maybe we can we can join up some of those initiatives Super. All right, we can move on Sex security is January on here, but that might not be accurate enough. We've got any of those folks on the line I think I see Dan Shaw in here updates from the space out of the world All right, we can move on App delivery are they here? Let us see Okay, yeah, we've got our These folks are working on the final project review I know this is something a lot of people have been asking about as far as what's going on with like how our projects are moving through And I think this is a pretty good example of being able to see which projects are actually in flight Their meetings are going to be this Thursday. So if you're interested about this, please look on the CNCF public calendar and you'll learn more there. So, I Will drop on through here SIG runtime I know we've got some of those folks here Hey, I'm here. So hello Yeah, so A few updates So the SIG got approved a couple weeks ago. So thank you for everyone who voted finally approved So We're looking at meeting next Thursday and there's going to be a presentation on sandbox presentation on volcano and then We'll make a recommendation and Based on that We'll talk to the TUC members Whether we want to make the to go forward with that or not and then next up will be Kira that's Sorry volcano is batch workloads and Kubernetes Natively And then next up is Kira that's Kubernetes event driven Auto scaling That's also schedule for sandbox review and We're scheduling that meeting Two weeks from Thursday. So then the next meeting After that the one that we have coming up And Harbor so I heard From the six storage folks that they're actually waiting for us. So so we're actually waiting for some more critical mass in the SIG So the SIG just got approved So once we get more critical mass then we'll start doing the due diligence and as far as the runtime components for harbor The other update that I have I don't Amy. I don't think we have enough Quorum in this meeting. So I'd like to call vote for the new a new co-chair. That's Diana Fidima from Red Hat So I'm looking for suggestions about what will be the best course of action here. So that Think we have line. We'll start. We'll start a proper vote. Okay. Great. Great. Awesome. So and and then so we have A new tech leads and contributors. So we have a bossy from red hat And then From Microsoft Sorry, I'm actually think I lost my slides here. So Yeah, so and then we have More now more now Patel from from red hat. So I'm going to nominate those two folks. So so the process for nominating Tech leads is in it's a two third vote from the co-chair And to third vote from the TOC, right? So I'm going to set those up for votes as well. So I'll need some help from you Amy after the meeting or you know going forward Yeah, happy to take a look at that. Yeah, and Yeah, and that's it for the updates. I'll take any questions. Anybody has any questions? I think Just to just to clarify this the last time that We wanted to and A co-chair or Or a tech leads We just needed According to the sick charter we just need a two thirds majority of the TOC members to vote so so I don't know if we have quorum today, but we can possibly do a verbal vote or or Then maybe do it by email separately if there aren't enough people online Yeah, I don't think we have quorum today. So I just counted I've got seven out of 11 So Well, we do have seven out of 11 Let me check just to make sure so I see just in Cormac. Yes, I think seven is the number we have to have right I believe so but I'm gonna check to make sure we've still got everybody online The people that I'm missing right now are Brendan Burns, Brian Grant, Jeff Brewer and Liz Rice. Liz. I already knew I'm I'm here. Oh Score I was a little late. I was a little late All right Yeah, so maybe I can call for Dan now. So I Need to look at the herd bio just give me a second here. So Okay, I got it here So Okay, yeah, so Diane Fidema She's interested in being the second runtime coach here. She's a principal software engineer at Red Hat in the AI center of excellence in the CTO's office I have a lot of experience in the field And being the second runtime co-chair. She's a principal software engineer at Red Hat in the AI center of excellence in the CTO's office I have a background in high performance computing and have been working on AI machine learning applications and benchmarking at Red Hat for seven years I'm interested in this role because I'm working with our hardware partners to enable hardware acceleration GPU FPGAs etc that will run on Kubernetes and open shift and there's a link to her LinkedIn profile I'll paste it on the chat There So, yeah, so just need a vote from the TSE members All right for the first time in a while we actually have quorum and can do a live vote I will go ahead and kick it off Yeah, I'm not sure if we've done this in a while. So we've got Brenton Burns on the line We've got Justin Cormack, Katie Jumanji, we have Matt Klein, Michelle Narelli, Sad, Shingliang and Shingliang Yes Anyone I've missed Christian, do we vote verbally or do we just Do a plus one in the chat because I would love to be able to have records for this. Thank you Amazing. Thank you Yes Drop a plus one in the chat. I see Matt Klein. I see Justin Cormack. I see Shingli. I see Michelle Narelli Shingliang Sorry, I'm driving. I wait until I get to a safe place to put all of my phone Okay, then I will I will I will consider this a voice vote for you then Thanks, you can put that in the chat if you need a record Is that a plus one or a minus one? That's a plus one, please Thank you. Okay I believe we have our new chair. Thank you very much everyone Thank you very much New co-chair. Excellent So the vote is plus one from Matt Klein, plus one from Justin Cormack, plus one from Shingliang, Michelle, Katie, Shingliang and Sad And a verbal plus one from Brandon. So this passes. Thank you all Cool. I'm glad we had everyone here for this. Alright Anything else that we needed to be able to talk about for a SIG runtime? Cool Nope. Alright, welcome everyone The one more thing is that we're going to do the votes later for some of these tech leads And so it will come up like in the next few days That's perfect. Yes. Alright, cool. So as we have Corm all as well. Alright Another questions on SIG runtime. Anything else? Nope. Alright, then I will move us along SIG network is unfortunately not able to join us today. I believe Oh, actually, I take it back. Ken might be here. I might have some of those here. Ken, are you on the line? I am. Sorry, I'm mute. Oh, yeah, no, no. So we have been meeting on the first and third Thursday of every month and have had quite a bit of interest and so Definitely would enjoy others and especially the new TFC members if you want to kind of join us sometime and check out what we're talking about You're welcome to and it's been mad has been a great job of keeping us on task and you can see how to connect with us. And there's really nothing else right now that they gone. Thanks. Great. Alright, any questions for SIG network this morning. Then we will move along towards our new work in progress. SIG contributor strategy, which that name may or may not change so Paris I'll pass to you. Hello everyone. Good morning afternoon evening wherever you are. I am Paris or can Google. I used to do this contributor experience thing for Kubernetes for a while. Nice to meet you all. Josh say hello as well. Josh Burkus probably have to go. Alright, Josh is another ringleader for this and it's been a great help. So for those that were not on the lines for the last two TOC calls we proposed this little shindig of a thing called contributor experience. But we've changed the name because we do not want to duplicate Kubernetes community and thus confuse folks further so we're looking at contributor strategy. What do you all think I'll ask you at the end so some of the areas that we're going to be focusing on from from our proposal standpoint is project governance. Josh taking taking much of that contributor outreach and growth and maintain our health and leadership circles, which I can explain in a minute. But all of these things would equate and boil up to ultimately a contributing MD project health check for evaluation periods during during CNCF projects. No, that doesn't mean we're going to audit that we're going to audit your contributing markdown file that's just me attempting a really terrible pun. That's why I said naming, naming is hard TV day. But hopefully you understand and get what we're trying to do here. So how we're going to do this we're going to recruit more people we're going to get the word out. Please help us how we're going to do this is get involved with more project mailing lists, email our charter out to folks try to get some people to help us. Form working groups for each of these focus areas. We already have some of those going but you can see on our charter. AB actually if you update the slides and hit refresh you're going to get an updated you can get an updated deck you don't have to do it right now. But in the in the updated deck there is a link to the charter and things like that that you can check out and help us get the word out there's actually a parking lot of future roadmap things that we could do if we had to help to do it. Josh and I have done a lot of those things before for instance like contributor metrics, for instance, but we just don't have the help right now we want to focus because this thing can get sort of broad fast. Some other things we're going to do is be drafting guidelines documentation evaluation criteria again for that health check status check of projects as it relates to their contributor activities. And then of course continue with discovery, because we want to hear what projects actually need. We already have a ton of information from to see members like Matt with his information about like what projects need doc, as well as like Chris a is done maintain our surveys in the past with CNCF. So we do have some of that data as well. Some immediate impact things Josh and I and a lot of other people that have shown interest already have tons of training materials talks etc. On things like, hey, we use help wanted an issue and good first issue, but we're still not getting people like what's next, or hey I have a contributing markdown file so what things like that like we can help out with or like shadows and apprenticeships and things like that and building that into your programs and projects. Alright, next slide Amy. So we are still drafting this charter. We have to go for a vote to the TOC Amy I don't know if you want to fill us in on what that timeline looks like. But our next meeting is next Thursday, not this Thursday is 10am Pacific. Yes, we still want you need you. Please help us. Josh, should I miss anything. Yes, that's about it. So next meeting will be finishing up the initial charter. Because of the nature of the SIG, we want to have that charter a lot more nailed down than necessarily other sig charters have been. In that matter, as a demonstration as part of our charter we want to actually outline the process of handling working groups within a SIG, because the CNCF has not had that sort of process documented before since it's new. And that was a request talking with some of the CNCF staff. So the goal is going to be to get that nailed down and then to actually, I guess put this thing up for a vote on the next TOC meeting. I'm doing the the hand wave back and forth because like I'm not necessarily certain that we need to be able to have like a direct TOC meeting vote for it. What really happens is that everybody does exactly what you're doing right now is like, oh man, we'll get our charter all kind of put together and like we like it enough that we would, we would agree to be able to do this. And then you put it into a PR and that's where we run a vote from. I mean I feel like the charter is in a good place. Josh, let's get off the let's take off the let's get off the line today and I think we can. I feel like it's almost at a PRC. So, let's see. I have a question about details for contributors strategy, strategy meeting details. We can follow up with that offline. Mostly because I don't think you actually want to read like a zoom link out loud. Yeah, we can put it in the slides. Yeah, we put it in the slides. Yeah, we can put it in the slides. Yeah, since we're not official, we don't have like the official channels. I can make you official channels you seem like you're ready for that. I mean, if we can get the channel some, let's do it. All right, and then we'll put those on the slides as well. Another question like this. All right. I wanted to ask that. I'm sorry. I just really do not like. Well, I want to call back to like, you know, I'm violently upset about it, but that doesn't mean that we want some some conversation in male English. How about this? How about this? Is anybody upset with our initial focus areas? Because the deal is like it's humans, right? We've got like 50 million things that we could do for these projects. But like, how can we boil this down to impact the most projects with, I mean, Josh and myself and I think Jared and like maybe a few others said that that we have like 68 hours a week, for instance, like we even like went to the nitty-gritty. And so it's like, well, how can we invest our spine here wisely that impacts the most. So that's kind of this is what we've boiled down so far. And we really hope that we can grow this to other levels. I've moved us back to the actual initial areas of focus to be able to let people see exactly what the scope of this is. Any comments, any feedback? Hey, Paris, this is Ricardo. Yeah, I think this is great. I think, yeah, initially, you might want to focus a little bit on the, you know, kind of make it smaller, you know, start small and then grow from there. So, because there's a lot of different aspects and, you know, and helping out contributors and I, for me, I think one of the, the important ones is maintain our health. So, because, you know, some of the feedback and the mailing list was that some of the maintainers were burned out or they're not being supported, you know, that type of thing. If there's a group of people and documentation that helps them out, you know, I think it's, it's just wonderful. For sure. And that's the, the circles that I didn't really go into, which is focus groups, honestly, I know that sounds weird. It's not like focus groups isn't like we're just going to get marketing out of you all, but it's like circles as in you're also going to provide camaraderie. And some of you already may be in leadership circles outside of open source, maybe like at your company or something where everybody gets together and, you know, you share things and like share best practices and whatnot. But that's really also where we can hear as a sig to what needs to happen and what we need to do to make things better. So it's sort of a kind of a really great feedback loop for us, and then also provide training to you specifically as mentors. And then we can even talk about some of the hard stuff like burnout as well. So that's kind of what I meant by circles. I could jump in here. So I've been working with Cheryl to figure out how to get end user feedback in SIGs and end user participation. So that may be something that this SIG wants to look into or have some hand in, like in the future, but I don't want to increase scope here. So I just wanted to mention it and drop this, the link to the issue that we've been chatting on by no means do I expect the SIG to take it like right now or whenever, but I just wanted to throw it out there. So if there's interest later down the line. For sure. That's honestly, that was about to be the fourth bullet, Michelle. Honestly, the fourth like Josh, you know, Josh has been like tremble. That's like, no, that's, that's definitely on the chart. That's in the charter as well, honestly, as one of our pillars, I think, and we just want more help. So we know how to do it. Like, I feel like I know I have some ideas as well. So if we can recruit some more help, that's going to be the fourth bullet. Yeah, awesome. I think Cheryl be a great resource. Like I mentioned, we can just make sure the scope that you'll have to find here looks great to me. This is a great, a great starting point, great charter. We can just go forward and see, you know, how much, how much Cheryl needs in terms of interaction. I think she's, she's got a really good grasp on how to communicate with the end user members and and I'm sure she can be a great resource here. So I'm going to be inviting her to some meetings or having her give us an update or or something might be something for sure. And yeah, we have some best practices too with like we're trying to create these, you know, user groups within the Kubernetes upstream community probably very similar to like what's going on here where you know obviously users want to give feedback to us but don't necessarily want to come to a SIG meeting. So maybe we can do that on a larger scale collectively to and again yet reason 455 as to why I want to do this thing. So, yeah, together. Thank you. Really looking forward to this. Thanks again. Yay, other questions anything else around this. Yeah, you guys have a plan to grow the SIG. I mean, in terms of like getting more people trying to get more people involved. Right. So, you know, with, I think you talked about the Kubernetes user groups. You guys have any list of things I think it would be a good idea to come up with a list of things of, you know, places that you can reach out and and try to get people involved in the SIG because it sounds like there's a lot of work to do. Yeah, yeah, there's actually on the updated slide. I was like doing slides literally like during this meeting, you know, that's me in detention kind of thing. Anyway, No, there's on the updated slides I have a little bit more about that bullet for recruit more people. So if you're on the slides, the live slides now we definitely intend on doing sort of a campaign. Once we have the charter flushed out the campaign being going to more project mailing lists like y'all stuff mailing lists. Also using and trying to beef up the maintainer list that CNCF has to to get some more collective voices on there. Also reach out to Cheryl, which is what we just discussed and try to get some more time in front of the end user community. Officially informally and figure out some more some strength, some, you know, some strengthening strengthening the pipeline there. And then of course, also going to Kubernetes. I know a lot of Kubernetes folks that are interested in this as well to collaborate. So I think once we get started and once we get up off the ground and get a charter and get some more communication pipelines going so slack and our mailing list and things like that. Right now we just don't have any way for people to contact us unless they like know me and Josh and some of the other people that have come forward of interest. So I think once we get going, we're going to, we're going to see some hopefully some more people and that's awesome. But yeah, I think folks just want to see us up and running at this point. So I have quickly refreshed slides your new slides are here. Whoo, and a third bullet I didn't finish. Yes. It's live y'all were live. All right, any other questions for signature strategy, whatever we're going to call it all of that. I have a question. Is there any intention to actually promote this for for maybe during KubeCon. Is there any intended maybe books for this specific sake or time with the seat. Members or anything like that. So, one of the things that we do try to do for the SIGs to be able to make sure that all of them get a session at KubeCon at this point in time. I can't guarantee that there's going to be exact session for them, but we will make sure that there is time to be able to meet with all of the SIGs at KubeCon. Awesome. Sure. Other questions. Anything else. Okay, I will actually move us on here, assuming that I can get us do that and drop in towards. Here's your updated revised charter thing in here for signature strategy. I think we've probably gone through most of this. And we can move on towards process updates, but before we do, I know that there was another SIG that wants to be able to talk about forming in here that doesn't necessarily have slides today. Matt, in the interest of time, are you willing to be able to talk about your SIG Yes, I can be brief, bright and gone. Hi everybody. My name is Matt. I've generated and drafted a very early proposal for a charter for one of the proposed SIGs, SIG observability. Observability is something that really touches everyone and us all. And so it seemed like a no-brainer. And I've always been a geek for logging, monitoring, alerting, tracing and the like. My plan is to send out via email a call for who's interested in having a look at this charter. It's in markdown format now, but I'll drop it into a Google doc. I've just dropped it into chat. Oh, well, I don't have it. I will get with you after the meeting about the right place to have the Google doc. Right now, there's a PR in a fork of the TLC, so I can do that as well. Oh, cool. Yes, your markdown files available for the people to be able to look at. Yeah, it's very early and it's just at the start. I think the goal would be for the next couple of weeks to just see who's interested in helping to collaborate and iterate on the charter and then provide cadence updates in the TLC meetings, and tracking to have something ready for a vote in whatever time makes sense. But ideally, I would love to have this launched by coupon. Clearly. So I welcome all feedback and I'm super excited to meet many of you and see if we can launch this. Given the breadth of tooling that exists and what's going on in the whole ecosystem around monitoring and observation of cloud native systems and not just, you know, capturing, you know, the three pillars but gaining meaningful insights into the behavior of these very complex systems at EverQuote here around a cloud engineering team and we every day work with all of our engineering teams and our problems and our challenges and our opportunities are not unique. So with that, I'll be done. I'll have a mail out to whatever the right email. I'll work with you on it. But thank you. So looking forward to meeting with the communities. No, but it's good to be able to see this rise and this is something we were talking about at the end of last year as something that was really missing for the SIGs. So happy to be able to take input on this happy to be able to see who the TLC would like to be a liaison because I believe that is one of the things you are missing Matt. Correct me if I'm wrong. I'm sorry. A TOC liaison is part of the process. So you have somebody from the TOC that you work directly to be able to get information back and forth. Yes. Yes. So that is one thing that we don't have yet. Again, the charter was just drafted an initial draft rather a starting place. Just in the past week. So it's very early days. Questions, comments, anything from anyone on the lines. I said it's good to be able to see this stuff rise up. So. Yeah, so are you going to put this up on the Word doc so we can actually come. Yes. Yes. The next steps is to be able to put this over into a document. And I believe probably a couple of charter review meetings are in order. Yes. I had being new to the CNCF to end user community. I wasn't sure about process and administrative and such. So I have a private PR on my fork. But I was assuming that a Google doc or something else would be more conducive to collaboration. So as I said, I'll have an email out to the relevant list that Amy will hold me with after this. And I look forward to, to iterating. Yeah. All right, we can move on. I believe there's no other questions. All right, excellent. Thank you, Matt. Last pieces here this morning are kind of some process updates and I believe I will turn it over towards Michelle, if you're available to be able to talk about any changes in the flow chart where we are with that. So this would be, we've short handed into the slides but this is a flow chart indicating how a project gets into CNCF. So Michelle, are you available for that conversation. We might have lost Michelle. All right, I will move us around from the flow chart pieces. We'll talk more about the same processes work that's happening. Again, we saw at the top of the hour that the storage folks have been working on a template around Alex, are you available to go in depth for that. So we had, so we started having some regular meetings between the sick chairs and the to see. And the, the app for that meeting was that we would, we would merge the available documents together, one to create a template for the information that we wanted to collect for for projects that we're going through review. So we have a standard set of, of, I guess, criteria or standard set of information that gets collected, which is, which is then also used during, say, review processes or, or perhaps during promotion processes when it goes from say sandbox to incubation, etc. And the second point was we decided to merge the, the process workflow to, to kind of have a simple documented process with some relevant timelines to cover how a process, how a project would work through the, the, the CNCF to get accepted. And that involves going through a triage process with the to see and then getting forwarded for for sick review and finally getting getting sponsorship from from the to see. I don't have the link the latest link which Liz was working on for the for the process for the process workflow. But the link for the for the latest consolidated templates is in the storage sake update page. If, if people want to have a quick look at that. So it's the thing that's highlighted in yellow. So we've taken, we've taken I think template that was available from see gaps plus template that was available from six storage and and merged them together to have to have a comprehensive list. And so we'd love to have, we'd love to have feedback on that at some point we need to have a, we need to have a TSE votes to make it real. Can you talk about what some of the differences or additions were in the templates. Right, what are the additions that six storage is adding that weren't there before. So actually most most of the most of the template was was based on our original six storage templates the one that we used. When we were doing say open EBS and Longhorn and Java FS. And then we added in some of the content. To cover things for the incubation promotion stage as well because our one has focused primarily on sandbox. Got it. Thank you. Lee, did you have a comment question. From my perspective, it was a little bit less it was less about adding new things more about consolidating a couple of different places that criteria and data points about the projects that were laid out there were laid out in various places. And there was not necessarily explicit with whom to have conversations with and when as those projects come for review to go first to the SIGs or second to the SIGs to present twice or not or that that workflow is covered in Liz's presentation she has she has a full sort of process workflow, which unfortunately I don't have the link handy. But I believe she had shared it on the main issue as I was trying to speak to say you'd question real quick with that. I don't know that the template necessarily as it stands today adds any new criteria. But just clarifies just centralizes it. Okay, and so is the ultimate goal of this template to capture the process as well or just to collect information from potential projects that are interested like that. Yeah, the latter. I think that's the template is the identifies the collection of information and then the flow chart that isn't being shown currently speaks to the series of steps. A project goes through for review. Okay, that makes sense. So Ricardo I believe has actually found this particular document and it is way too long to be able to walk through here in the last like bit that we've got here. So we'll put this on a future meeting because I know this is going to be important for everyone to be able to review understand and we'll be moving towards a vote probably before cube kind on this. That actually covers most of this that were on the agenda. Is there anything else people wanted to be able to bring up your credits. I see no chat and I don't see any muted quickly. I will call it and welcome all to our new members good to be able to see all of you. And we look forward working with you. Hey, everybody out. Thank you everybody. Thank you. Bye all. Thank you.