 I didn't have enough coffee for this. Oh, you want me to just read from here? I can absolutely do that. Yeah. Hi, everyone. James Strong. I'm one of the core maintainers for Ingress Engine X, our favorite Ingress controller. We are embarking on a fun journey this year of trying to look to replace Lua with JavaScript. So if you have any networking experience and JavaScript development, please come and talk to me because we have a lot of functionality. And we're going to talk more about that in our project. Also, non-code contributions. We need examples from all of the cloud providers. We need examples on how to do weird, crazy things with networking. So if you do crazy things with Ingress, please come talk to me and we can do documentation. Thank you. Awesome. Thanks so much. The next respondent we have, Jun Yang. Are you here? Oh, okay. Great. We need some walk-up music. Two names? Let me see. Oh, Yang. Hi. I'm Xing from Six Storage. We have some very exciting projects that need help. So let me highlight a few. The first one is a cozy container object storage interface, trying to make object storage the first class citizen in Kubernetes. Why is that important? You may know that object storage has been a popular choice in AI machine learning. The future is alpha. We are trying to move it to beta. So come join us if you want to be part of it. And the next project I want to highlight is a volume group snapshot. It allows you to create a snapshot of multiple volumes at the same point in time, which is a big deal in terms of efficiency. So come talk to me, Yang, if you are interested in contributing to Six Storage. Thanks. I want to promote our weekly issue-to-yage meeting, which happens every Wednesday at 10 a.m. Pacific time. We often go through our bugs, but we don't have enough contributors to fix all of them. So we have a huge pile of bugs. We are looking for people with any expertise. We just need go-rank and basic Kubernetes. And we can find a bug for you, maybe even a feature. Thanks. All right. Thanks so much. I see you all filling in the forms now. Thank you with a lot of TBD. I'm going to find you afterward, and we're going to make sure that we get all of these links in here, because that's very important. So next up, Patrick, Oli, are you here? Yeah. OK, and then after that, on deck, we have Ben Elder. So I put in one thing. I'm sick-testing tech-lead. I've done quite a bit of work on the end-to-end testing. And at some point, I realized that we are doing frameworks for end-to-end testing with Gingo, and we do the same thing for Go tests with integration tests. And the only reason is that we do that because both have different APIs to, say, for example, report a failure. And I started thinking, can we unify that? Can we have a common API for, I'm a test. I need to report something. And we can. I came up with something that's now in Kubernetes, core Kubernetes in test utils K testing. And I'm looking for other contributors who are interested in exploring how to move that forward and whether it's useful, whether we can get rid of redundant code in Kubernetes, which is hurting us when everyone writes tests. They always need to learn new things, how to do things differently. I think we can make it simpler, but I need people who will bounce off ideas, get them to help write perhaps some code, get it changed in Kubernetes if we come up with something useful. So find me if you're interested. Thanks. Thanks. Franco, you're on deck. Hi, I'm actually kind of doing this by proxy for Michelle Shepardson, MRI and Slack. We're continuing test grid UI development under Kubernetes. If you're not familiar with it, test grid, testgrid.kates.io shows your test in a grid with fast flexible interactive front end. Last year, we started writing a new UI to replace the existing closed source one, but it's currently an MVP and needs more work to complete it, make it perform in a feature complete. If you've got experience in front end or you're willing to learn, hit us up on sick testing on Slack or Kubernetes six slash test grid on GitHub. Thanks. Thank you. John Belomaric, sorry. Hey, so I'm here on behalf of sick release, but also on behalf of a little bit of sick security. We're starting to do our redesign and modernization of the Kubernetes security feed. And over the past, I don't know, one or two years, we've been putting out some tools and information, some security metadata on the Kubernetes releases. And we are now about to start doc-photic data information into our normal projects. So the new security feed is going to be ready signed from the point that the Product Security Response Committee, like the Secretary Response Committee, takes generate study information all the way to the releases. And we plan to do that the binding thread for the security information that we put out. So if you have experience in security, building CLIs, even if your CIG wants to get involved in that information, please hit me, Puerco or PJ from Sick Security, where this is a cross-cig effort. And then you're going to see the gaps going up really soon. Thanks. Hello, John from Sick Architecture. And you may know me from production readiness reviews. And I am here to ask for more help. We did promote one person to an approver. Joe, I don't know if he's here today. But we could use more shadows, more approvers. We have a handful of shadows who help out. And we have a sort of ladder you can climb to help spread the load and make those go faster for everybody. And I also have one other thing for Patrick who's up here. But he and Kevin and others have been working on dynamic resource allocation. We will have an uncomfortable about this later, hopefully. But the point I want to bring up is that device vendors for, you know, specialized hardware devices and end users of those devices, we really could use your input right now. A lot of our input comes from Intel and NVIDIA. But there's more people out there than that. And we want to make sure that we can actually handle your use cases. So please come to that on conference on that later. Thank you. Thanks. Madhav, where'd you go? Madhav? OK, cool. Hi there. My name is Mohamed. I'm one of the Sick Cakes in for Leeds. And I've got a few things. So in case you missed Ben's email last month, the default cluster is going away later this year. We need to get rid of that as soon as possible so we can get on with the proud migration that we're planning later this year. What else was there? So we have a couple of services that we're trying to integrate with SSO. So it's very easy to onboard and off-board people. I'm looking forward to talking to Sick Docs about Netlify and a few other services as well. And the final thing I want to add to that is last contribution to me I talked about getting rid of Keevap. I'm still working on that. So I need some help with that as well. Thank you. Hi, my name is Madhav. I'm one of the tech leads for Contrabex. Apart from that, I'll also be doing a call for help for Sick Architecture, but that's for later. In Contrabex, if you'd like to help out with some of the automation tooling for annual reports that we had done pretty scrappily for last year, reach out, we have two questions for the annual reports. With this tool, you have one. So make the process even easier for essentially all SIGs. So if that's something you'd like to help out, please reach out to me. From a Sick Architecture point of view, I help out with essentially keeping Kubernetes on supported Go versions. So we do a lot of Go Bumps and testing of Go versions as and when it happens. So if that's something that you're interested in, diving deep into each Go release, what changes the Go project has made, working with the Go team, all of those things, if you'd like to help out, please reach out. I think there's just three people doing it right now. We can definitely use more help there. So yeah, thanks. Hi. So we already covered between John and Madhav. We covered a little bit of the Sick Architecture, but one thing that I do want to emphasize is like, when we're talking about SIGs, SIGs, SIGs, you are in a specialized area, but there is a lot of work that goes on between all the SIGs too, right? Like we have to do API reviews. We have to do PR reviews. We have to do conformance tests. We have to do enhancements, taking care of the enhancements. It's like with the release team for every cycle, we also have some people working on enhancements together with them to develop the tooling and things like that. So there is a lot more work across the SIGs where we really need help because we don't have enough people spending time above individual SIGs. So please consider coming and helping us. Like for example, Jordan is very well coming around API reviews and like he always wants people to come and spend time doing API reviews because that is going to help everybody, right? So getting to know like our deprecation policies and like how versions queue works and those kinds of things are, you get affected as a SIG, but when you come and work with us, you know the nitty-gritty details of like, why are we doing it? Like why are these guys are bonkers, right? So you will get to know more about it. So you can then go educate the rest of the people in your SIGs. Please consider coming up and working across the various SIGs. Thank you. Hi everybody, my name is Ian Coldwater. I am the co-chair of Kubernetes SIG Security. So here are the asks for SIG Security. For our external art audit sub-project, there is another external third-party security audit coming up this year. And this year we are working on changing up the scope. So if you have anything that is external to the core Kubernetes project outside of KK, such as for example, Kubernetes SIGs slash cluster API that you want included in the scope for the external security audit, please let us know because now is the time for you to get your thing included. For tooling sub-project, we have two shadow roles that are being announced soon. If you are interested in getting more involved in tooling as a shadow, come to the next SIG security tooling meeting, which is Monday the 25th at 5 p.m. EU time, 9 a.m. Pacific time. For the SIG Security self-assessment projects, we are always looking for threat modelers. So if you're interested in threat modeling or learning how to threat model, go holler at them. And for the SIG Security docs sub-project, they are looking for contributors for a couple of things. They want the contributors for the RBAC tutorial and the security hardening guide. So if you are interested in doing security documentation or learning more about security in order to do security documentation, come holler at SIG Security docs. We are 100% new contributor friendly, all skill levels welcome from the newest newbie to the burliest graybeard. So come holler at SIG Security anytime. Thank you very much. I'm Casem Fields and I'm one of the co-chairs of the special interest group for contributor experience. And I'm also a co-lead of our sub-project for contributor communications. So the contributor comms group is a great place for net new contributors. In particular, we have a SIG spotlight blog project which is always available because there are so many SIGs within Kubernetes that we always have SIGs to do blog posts about. This is really great for brand new contributors because it's an opportunity for them to interview the leads of a SIG and then write up a blog post about what they learned about the SIG. So it means for new folks that they get to explore the project, learn about how the community works and actively contribute and get recognition all at the same time. So great place for new contributors there. We meet weekly and we are also active on our Slack channel which is SIG Contrabex comms in Slack. A couple other areas where we could use some help. The contributor site is written in Hugo and if you are familiar with Hugo, we could really use some help there. Or if you know anyone who is familiar with Hugo, please let us know. We'll have a working session usually here at the contributor summit where we hack on the contributor site a little bit but we could really use more help there. Also some automation that we have going on. We use Zapier to do a lot of automation moving our Zoom meetings into YouTube. We also use it for a number of communication social media use cases. So if you're interested in those as well, that would be great. And social media. If you are into social media and you wanna help us communicate with contributors through social media, we could use your input there as well. Thank you.