 Good morning. We're going to give everybody a few more minutes to be able to come on in. I heard from the spiffy spire folks and they are going to be a little teeny bit late. So we don't have a little bit of time to be able to get in here. So greetings. Good morning, folks. We are holding for a hot minute because the spiffy spire folks are kind of the ones. Kind of we need this morning. So, yeah, okay. I see thumbs up select that you can at least hear me. So, well done. Okay, come on. I'll hold for another 2 minutes. If I don't see them dropping on in from there, we'll go towards being able to talk about like projects currently in voting what's currently happening in here. Because that's really a nice way to be able to pull stuff together. So, yeah, who was the sponsor for spiffy spire for incubation. Do you remember? Oh, goodness. Let me go look. That is not data that I keep in my head. Unlike all of the other data that I keep in my head. Let me go look it up. I assumed it was. I mean, there's a lot in there. Let me go take a look. I know it's written down somewhere. Was it me. It was it wasn't back to you had to go look it up. Yes, I was just thinking I remember I remember doing it now. Okay, Justin, you're on this point. Fine. I mean, like, this was, in fact, like a couple of years ago and a lot has happened since then. So I understand. Yeah. Okay, Andrew's also here from the spiffy spire. Like, folks. Yeah. And Andreas, let me know that he's running a little bit late this morning so that is actually good to remember as far as like, yeah, no, Justin Justin Cormack, we might actually like call on you more directly. I'm going to actually move us over towards the projects that are currently in, like, you know, as things are moving around, but welcome. You have made it. This is our normal antitrust policy notice. This is our normal meeting logistics pieces because you are here you have made it to the particular meeting well done. Our TOC members are currently tracked up here. And in fact, we do have quorum today if we wanted to be able to do something, but it's so much better to do it by email so please don't. This is our agenda and I'm going to move us towards the projects applying the move levels first in here. For general updates, general comments, anything else running around and Justin Cormack, I will pass to you and Toto is currently in voting. Yeah, and I was inviting seven out of 11 on that one right now. So, if you haven't correct Harry pass and do you want to bow? Where are we on to bow? Oh, thank you. So, so we have finished the did you like the diligence doc for triple FS. I filled over all that project ready so I will send out all the materials I have all including end user interview of course so I will send all the material in the Slack channel to let everybody to take a look. If we feel it's great. And then I feel it's safe. We actually to put triple FS for public common period. So this is a constant as well very promising here. Nope, that is splendid chaos mesh. Oh, sorry, cloud custodian. If I've got Ricardo on. Okay, I don't. So we will move on to chaos mesh in voting. They are currently passed the vote so we're just really waiting on the team to be able to help like make PR happen. Press releases happen, not pull requests. Volcano just hit public comment, and that's also for a Cardo project. So Elena, I will pass to you on Cupid, which is changing the slide for public comment I just haven't refreshed them. I mean, the convert is in, is in public comment period, and I do believe that we are hitting two weeks more tomorrow, but Amy, I'll, I'll rely on you. Okay. I'm going to go double check on all of that because there's a lot running around. But thank you for the update. Captain. I finally got going on that. So just starting the review process. And I plan to have some feedback into the DD document by the end of the week, or early next week over the weekend probably, and then I'll be scheduling interviews. So I might be coming your way. All right. That is perfect. Thank you. K native currently in voting. I currently have seven out of 11 as of before this meeting. You should say the official voting right. The official voting one. Yeah. But yeah, official voting, like now an official voting, all good things will come together. And we have Liz Rice's backstage, which we will be looking for a new sponsor when we hit the end of public comment. Oh, and I see Liz Rice in the call. Thank you. Anything to say around our go g rpc. No, I'm going to get, I'm going to get back on jrpc. If anyone'd like to be interviewed me, please. We have a lot of users of g rpc. So there's a spot for choice for people to interviews. Lovely. And Harry to you. Yeah, so we may already notice in the select channel that our goal is working on their security issues and they have already public several blocks teams actually help a lot here and maybe team you have more information to add. Nothing more than that. So we were working with them on their security posture trying to get them to write things down. You know, enhance their processes a little bit and ensure like whatever they are doing is like visible documented. And so people can go take a look and feel better that, you know, things are going on fine. And if there is a something that's getting get gets reported, then it gets worked on and things like that. So I think there's at some point when we feel comfortable, we have to get them back, reboot their process for the graduation one more time. And we probably have to, you know, we have to, we have to figure out exactly what are the steps that we can grandfather from before and what else do we need to do new. Nope, that sounds like it is all reasonable things. So, alright, I'm going to move us back over towards our graduation proposal for Spiffy's fire because I think we've got all of that team on the phone. Unless anybody had any questions I didn't see anything in chat I saw a note around like custodian status like things are moving hooray. Alright, seeing none hearing none. I'm going to pass to Andres and the Spiffy's fire team. Thank you Amy. Hello everybody. So, yes, spiffy inspire we are proposing the projects, the firm to you for graduation. It's been quite a journey, the project center CNCF and 2017 move to incubation and the start of 2020. There's a lot of numbers you can see in death stats on how the projects have grown, and so many different areas but a couple of things to point out and I think this has been. A lot afforded all by by the CNCF of a project started by few that that's a big gap in the ecosystem has really harnessed a lot of different vendors, so many of them like fierce competitors, and we established thriving community, a multivander effort. We have reconstituted successfully the steering committee, it was formerly the spiffy technical steering committee that were the initiated early believers to the project. Most of those members have transitioned and we have new folks in there. The technical standpoint is, it's just really amazing to see the robustness and the stability that the projects has have achieved, and also the breadth and depth and integrations of other ecosystem projects that have picked it up, ranging from the popular service meshes, GRPC, native capabilities and through cloud providers, EKS service mesh being one, several others. The end user community has also, well, quite of uptake in the end, well everything we do is in service of making organizations more secure, so that's been really rewarding and fascinating to see. Since incubating, we also transitioned what was originally the spiffy days, our gathering and hangout into a co-located event at KubeCon that has been successful by many measures, it's been very well attended. There's been great participation again from end users, speaking about their usage, scenarios and outcomes that spiffy and spire have enabled for them. So, yeah, I think, judging from our own evaluation of the rubric for graduation, we were there, we think we need or exceed all the categories. Since incubation, Justin Cormack, thank you for graciously leading the due diligence for us, we went and conducted a third party audit. We acted upon the findings of that audit, and we made the project even more watertight than it was. We have written a book that gathered members from the community at large, thank you Emily Fox, congratulations on setting now the talk. You participated in the book, you were a tremendous contributor to it, it's called solving the bottom turtle, you'll find the link in the graduation proposal. So, yes, it's just been like proliferating and growing, we expect to continue to grow. That's well in affordance of being a CSEF project. And with that, I, well, we have the rest of the steering committee members here, I don't know if anyone wants to add on anything to that, but pass it on to the talk. Thanks to them, hearts to. And thanks Justin for the link to the book. I don't know if any of the other steering committee folks want to be able to weigh in. Andrew dress up, come on in. You're totally muted and they don't know how. How's that. We are now unmuted go ahead. Okay, great. I also don't know what camera I'm speaking to so choose one. I didn't have a lot to add other than what I said, this is, you know, this, we're really excited by the momentum. And, you know, I think as well as the sort of the sponsoring institution behind this. So, you know, I think it's a very diverse set of containers represented by, you know, a large number of different vendors and so we've been able to, you know, gain a truly child, which I think has been very welcome and impressive. And that's it. Happy to be here. I'll actually pass to Justin Cormack first saying nobody else kind of like putting their hands up here. Um, I mean, I think that, um, yeah, I remember, I remember going to, I think one of the first public spiffy meeting at cube con and, I don't know, Austin, maybe in a, in a bar with with carry it with. PowerPoint karaoke. And I think it's, it's, it's come a really long way since then. And yeah, I think it's really interesting how it's built a community through very different governance structures, very different people. Um, it was, you know, kind of through, I remember when I remember talking to the team when the acquisition of Stara happened to find out what what what HP was going to do and if this was going to be a positive move for the project and what was going to happen because it was still you know, kind of unclear them, but I think that really the, the projects shown that they can work across that, you know, across security. You know, with security people across all sorts of different things, I think that the book has been really helpful for helping people understand the shape of the problem they're trying to address and what the and these kind of these kind of bootstrapping problems and identity problems are really hard to help people understand that I think those kinds of that kind of thing has been incredibly helpful in in helping people discuss, you know, discuss these kinds of security problem in the community. And so I think that kind of educational materials are real lesson to other projects that it's fun to do. And I was amazed by the way they did that book in two weeks as an immersive sprint based process which was really interesting and it worked really well so I think that it's been it's been kind of really interesting watching this, watching this journey. Yeah, book sprints that was the one yes. I'd love to try on some other things. Yeah, you know and hindsight. Absolutely. It's a lot of the struggle was like how do we how do we solve the problem people think they have in order to have a chance to explain the one they don't. So yeah I think thinking outside the box well the book is one of many examples of while bringing plural views and thinking outside of the box let's try different things let's pull pull folks in and let's cater to the different ways that people consume content pay attention learn about things. Thank you. And thanks for for your involvement in the project. And we're continuing to look for it. Still ways to go. Hi. So, when I was going through the graduation proposal one thing kind of like stuck me was, you have a maturity framework for some projects. How was that, you know, working out and how was it helping you progress because I haven't seen other people do that. Yes, so we just don't we have had other projects do that we've actually asked for various times because sometimes it's been unclear to people particularly around graduation, which parts of the project they should consider production ready when there are some projects that are clearly not. You know it's all very experimental so it's not unprecedented. Yeah, they have they put the label by themselves without us telling them to basically right. That's a great observation. I think it's, it's not something new there's definitely prior art. I think they're couple motivations, why we did that. While we maintain spire as the reference. Implementation of spiffy. It's not the only implementation of the project. We also maintain a number of language bindings. We have go spiffy Java spiffy. There are a few others since incubation we also folks have an interest in building systems on top of spire have a spire federation controller for multiple trust domains, Brandon Lohm and Marius from IBM started that project. And it was all at a time that we were dealing with growing pains, our bandwidth of attention of our maintainers was pegging. We were treading water, and we had kind of had this official projects and we try to take care with people building things around this best effort but we were doing a great service. So rescinding a little bit control, but like stipulating a framework for people to be able to develop this things on their own as long as there's proper representation of well as this fully supported by the project officially, or well it's nascent effort and it's somewhat experimental so that is part of the motivation there. We have a maturity label right now are the language bindings as well as 20 act. And so now I'm going effort. There's a number of things in the spiffy inspire ecosystem that we haven't vetted against it but we're hoping to accomplish that. Hopefully that, like shares a little bit of the rationale behind it. So you touched on something else that I also wanted to poke at which is, where do you see yourself, you know, post graduation like, or what, what are your aspirations as a community, what do you what else do you want to do, essentially. That's does a great question. I'll take a stab. I'm sure Andrew has plenty of perspective on it that I think it'd be beneficial for the for the group to hear. I think it's very important as a core infrastructure project that people are considering trustworthy that no one running spy and production experiences and outage because of spire so reliability stability making sure that the project is watertight is going to continue to be a priority for the project. And number two, it's growing integrations ensuring that the top 50 or top and open source projects support native spiffy authentication, and that we start bridging and debalconizing pockets of infrastructure that are fragmented. The dream is is a world of secret list authentication across the board and to end. Andrew. I don't know how you're muted again. Double muted type that folks. I'm gonna look at this camera to that's probably better. I think Andrews gave a great summary. I don't have a ton to add to it. You know the projects, you know we've tried to keep the, the core, the core problem that we're trying to solve, you know, well bounded and well scoped. There will be, you know, as always, ongoing efforts on stability and maintainability and ease of integration. In terms of growth going forward. You know, as Andrew has mentioned, we'd love to see more richer upstream integrations native integrations into things like say secrets managers identity management platforms and so forth. And a lot of that you see captured in the, you know, early incubating projects, you know, within the within the spiffy ecosystem itself. And then you know I think your success for us, you know the next say five years would be to see more of the industry align around the spiffy API's to align around, you know, particular things like the workload and Federation API to allow as Andres mentioned, you know it kind of the organization of workload identity and decide to have greater attractability between the different platforms and solution sets so we think you know that graduation will facilitate the momentum that we already have there. Last trailing thought is well all without losing sight of our values. And well democratizing the technology like make make it something that it's in a direction that set it and forget it. It's consumable by the industry at a large not just like an expert level system. What other questions dims dims you can also feel free to pass to anybody else. Well as a resident security folks like I should call on Liz and Emily. Emily can be called on Liz unless you'd like to. Okay. I can say that in the years that I've been working with the spiffy inspire folks both with the book as well as with the security assessment and security tag. They've all been very security forward and the design and the thoughtfulness of the product as well as the documentation and ensuring that it's approachable to the vast majority of intended users and even the unintended users. And some great conversations around how we can present material that reaches the most amount of people where they're at, especially for a very large project with a lot of complexity and its potential implementation, both within the specification as well as the reference implementation. One of the things that the project sets within the ecosystem is, it has a lot of potential different use cases so I'm really proud of the work that the team is done, and both their embodiment of security from that perspective, but as well as their commitment to diversity and inclusion within the community and the thoughtfulness and the language selection that they've been using throughout their progression from the security assessment when I first engage all the way to today. I will pitch really, really quickly. I think it's an awesome project and I'm only jumping in because things asked. I think it's a really good project. I will say I have personally, and this is just personal, so it's anecdotal. I haven't seen it being used a huge amount amongst the end users that I've spoken with. That's just anecdote and I haven't gone out to look for it. So that's my only kind of anecdote to add. But I do think it's a really solid project. Tell us who they are. We'll go after them. No, no, no, no, no, like that you're supposed to be able to like hey no we know people using this in production part of the challenge is being able to like, I understand being able to find it. Okay, thank you Liz. All right. Any other questions, comments, overall thoughts. New to see members any other questions that you have around this. I see a good friend of the project and we call Paul Holland arm, you know, something that's been very encouraging for us has been see folks from problems that I would say are like the last mile beyond like outside. Just the last mile from like, where we reach at and parsec is a great example of expanding and extending like, well, a wire protocol and abstraction to hardware devices. And it was a sign up, like incorporating spiffy. And that's been really, really encouraging. Well, knowing that we're directionally correct, and that we paid enough attention for people to seamlessly integrate and extend this this interfaces and like tackle the problem at like different problems, specific to particular industry says to be edge and IOT, which is some of the key use cases of parsec. Paul is correcting the record here. Oh, I'm sorry. Go ahead. Come on in. I guess this brings us to the hard part. Who's willing to step up and step up and sponsor right to me. Yes, but I mean we seem to be hitting like kind of the end of questions here and the end of like the kind of just kind of back and forth. So, right, this is the next part of being able to come step in, or other questions that we haven't gotten to question on sponsorship. Well, I had spoken to a few of you, as we were gearing up for this. Could we have more than one sponsor have them tag team it is that something common or typically not not a practice. I mean, yes, I would be highly in favor of that in large part because we've got kind of new folks on like to see and being able to help them kind of walk through process in here. Separately that also means if somebody gets overwhelmed or busy then like there's somebody else be able to pull them across the line. So, yeah, fun being able to have like pairs on this one. There's no prohibition against it. How's that. It helps. Thank you. No, that's fine. I mean, I'm happy to work on this with someone else if that's. I'm also happy for someone else to do the graduation as I did the incubation, say, whatever he wants. But if you're willing to sponsor, I will be happy to assist you in that as my first one. That was Justin Cormack so Dave, Dave is quiet in here Justin Cormack and Emily would actually be a perfectly fine pairing. Oh, you type in the chat. Everybody in okay fight for it. I probably shouldn't be the one being able to lead it simply because brand new and like the first time out like I wouldn't do that to you. But Justin Dave fight for it. I mean I'll rephrase that and ask Justin if he wants to do every one of the reviews or like he said he wants to step back to the incubation. So it's your call Justin. I really don't mind. I really don't mind to be honest. I believe what I just heard was Justin Cormack to lead, and then both Dave and Emily to assist on like interviews and various other things in here to be able to like pull all of this together. Bear. Well work it out. Exactly. Okay teamwork. Well done. Any other pieces that we needed to cover this morning. Yeah, on process. Well we, we have collected what we have collated a number of like public case studies and public adopters I know the process entails conducting private interviews. Do you need us to wire up those conversations for you or like, do you reach out directly to these organizations back channel. And do the interview. How does this work. Either way we can, we're happy. I mean, if you've got contacts that's often very helpful if people want to come forward that's also helpful if we have people we want to talk to we can do that so it can be a mixture. We can talk about it offline. Okay, sounds good. All right, I have put the official note in chat. Excellent. I think that closes us out on that we've gone through our projects plan to move levels and we are now in the point of questions, anything else that we can cover today. Well we're at a timeline for conducting this interviews, I think that's a few weeks, three weeks or like, as long as it takes. Like we want to get good answers right. Yeah, it's kind of it's hard to give an exact timeline because it depends on people's availability and scheduling and things. Naturally. As long as it takes people to respond to emails. I mean, it's not a great timeline but it is true. If they have Calendly it helps. Realize Calendly was going to be like the internet main character. Part of it really depends on being able to have people be responsive so the more that the project can help on people like end users and all of that being responsive the better. Right on. Well, again, super stoked and fired up. Hard to believe we made it this far, but we're looking at the evidence so pretty cool. This is great. Justin you also mentioned contour might be coming up next. I was paying to me this morning. This morning or last night. Yeah. Okay, when I see that particular proposal come through, I will put it on the schedules. Like, we're kind of backed up on things for a bit like I can't see that actually coming up before like this time next month. And our next sandbox review is also an annual review meeting as well so we should probably look towards like how we're going to deal with all of that just procedural notes. And also like upcoming things for a there's going to be a sandbox meeting review for a that is March 8 for anyone else on the call. Amy the other one that I had for you was the to see chosen seat nominations. What's what happens today today at a new specific time that closes hold on I've even gotten this written down. The next piece around that one is going to be closing nominations close on February 22. That's to see nominated. You're going to get a form at about noon today. February 22 through March 8. We've got that two week qualification period where both the to see and the governing board vote will do a very short election from March 8 election opens. Pretty much noon that time. And then March 15 election closes at 12 p.m. Pacific and results be announced that time and March 18 our new person is going to be joining us so. Who's the existing person from the. Sweet. Elena, it's Elena, and we love Elena. Thank you. Thank you for your work with us. I know that you're probably not going to be standing again. So, thank you, Amy. Yeah, I want to give other awesome folks an opportunity to stand and be left it. Thank you. Nope, that's wonderful. Yeah, only rules around that one are Elena can nominate but Elena can't vote. Any other questions that I can help answer for folks. All right. With no other questions, I will send all of you back into your day it's good to see you and congratulations to spiffy spider for making it here. Well done. All right. Thank you for your time.