 Good morning, everyone. So glad to be here with all of you today. And to share with you an update on what we've been working on at the Technical Oversight Committee. But before I start, in a show of applause, how many of you have heard of the TOC? Sweet. How many of you feel you have an understanding of what it is that we do? Nice, awesome. So the Technical Oversight Committee, as a quick overview, is the technical governing body of the CNCF. And we work together as a team to evaluate projects for inclusion and to work with those projects once they are a part of our sandbox or incubation project to get them toward graduation. That takes quite a lot of work. There are about 11 of us, but we do a lot of this work. We're also supported in this work by technical advisory groups. These technical advisory groups are focused on different domains. Everything from security to contributor strategy, observability, there are quite a few different projects that are focused on specific domains. This is what we look like. If you see any of these people out there in the hallway or if you have seen them or if they're here, I would love, you know, definitely say hello to them. I've worked with a lot of technologists in my time and I can tell you, I'm gonna show you that each of these are absolutely amazing. They have a passion for open source and technology and they just, they help us make such a big difference in the way that we're doing all of this work. This year we've had the opportunity to all meet and work together for one of the first times in the TOC period and we got so much done in that period. It was just absolutely awesome. One of the consistent themes so far in our efforts this year has been scale. We are, again, 11 people. So how do we actually, how do we help process all of the work that we're trying to do in evaluating projects and helping those projects graduate and helping to understand the health of those projects? How do we actually get all that done when we also have full-time jobs? And so some of the work that we're doing here is actually trying to help automate the work of gathering information about health and those sorts of things. So that's been one of the areas of focus for us this year. As part of the, as another part of the work in 2023, the TOC has been reevaluating a lot of the existing moving level structure. So how do you actually get a project into the CNCF? How do we determine that the project has met particular criteria before moving them to incubation? Again, to graduation. How are we ensuring that we understand the health of that project and we do annual reviews of those projects as we go? So we've got a lot to accomplish and we have a lot more to do and we realize that perhaps you will decide to come and be a part of it. We've been working recently, as I mentioned, on coming up with suggested improvements on the project's moving levels piece. And this has been a lot of work and it's actually involved a lot of people from outside of the TOC just in the community in general, which is very much the open source way. But we've been very, George Castro and Josh Berkes have just among many, many others have been very influential in that. We are also working through a backlog of annual reviews. Understanding the health of projects and determining if everything is moving in the right direction for those projects as we move through. But as we grow the number of projects that work continues to get more, we continue to have more and more of that work. We've created a new project board. If you go to github.com slash CNCF, you can find that project board. The project board intent is to actually provide more transparency around the work that's being done. So if you're curious about what we're up to, that's a great place to start. And finally, we are working to enable our technical advisory groups to be part of that work, right? So that we're not, it's not just other than people doing all of this, it's all of us together trying to accomplish that work. Speaking of our technical advisory groups, please help me welcome to the stage some of the leaders of those groups. We have Ricardo Aravena from TAG Runtime, Alelita Sharma from TAG Observability, Catherine Paganini from TAG Distributor Strategy and Pushkar Jaglakar from TAG Security. I think I need to be there. I need to be there. No problem. Sorry, Dr. All good. Thank you for joining me up here. You got me. You know, it's awesome to see you all here. So a lot of people aren't familiar with the TAGs or the way to contribute to a work that they're focused on. What makes TAGs and their placement in the ecosystem uniquely rewarding and what brought you to this work? Myself, I started attending the events, joining the meetings and getting excited about the technology, about the CNCF projects, about Kubernetes. So it started around 2019 and contributed to the TOC meeting and the TOC was actually growing and a lot of new projects wanted to join the CNCF so they needed to expand. So they created the TAG Structure Technical Advisory Groups to help them out and I actually jumped into the opportunity to become part of the leadership of the TAG runtime. And yeah, and that's how I continued participating and kept reaching out to different communities and making the TAG grow and helping out the projects through the different stages. I got involved in the TAGs as a contributor to OpenTelemetry and as we were working across different projects, especially I was at that time, working with the Prometheus project as well as Open Metrics very closely in the space of observability. So again, working across projects I think really drove me to participate in the TAG because TAG is kind of the glue where all the projects come together and also as a supporting group of the TOC it really enables all the projects to facilitate communication across and collaboration across the different projects. And I found that very compelling in the observability TAG because it really enabled everyone to come together at the table and contribute. Thank you. Yeah, so I started or I initially joined because I had just joined the Linkerd team and that was my first time being part of OpenSource. So I wanted to learn about growing your community and all that stuff. So I joined the TAG contributor strategy and why I'm still around, right? Cause it's really about the people. So I think like you get so much more out of it than you actually think. You meet people from different countries, different companies, different backgrounds, you collaborate, you're really growing your professional network. It's incredibly rewarding. And so that's not something I expected, right? That's not, I thought I'd come in and then I leave or something, right? And there are a lot of benefits like and for instance, like perks like being here on stage with all of you, right? Like we would not be here if it wasn't for the TAG. So there are a lot of reasons to be and join and encourage everyone to really, yeah, just participate in the TAGs. Yeah. I mean, for me, everyone's contributor journey is different. So I'll maybe start sharing a bit about like how I started. I think in 2019, I was a first time attendee, first time speaker. Like many of you, I just popped into one of the maintenance track sessions for a security TAG. Asked them some really hard questions and they were like, you should join our meetings. So I went, joined the meetings, got to know about the work they do, started contributing and with a lot of help from Emeritus Shares became a tech lead a few months later and then led a bunch of different projects. And recently this year, I became coach here. So now my job is to make things better for people who are gonna follow me. So one of the things that the TOC and the TAGs work together on is the formation of working groups. And these working groups will generally be focused on a specific topic or a specific domain, some specific outcome. Katherine, you've been working with one recently. Yeah, so I'm very excited because we have a brand new deaf and hard of hearing working group and it's literally just four months old or so and we've made some big wins. I don't know, you may have seen some of our deaf attendees walking around with their interpreters or they're here in the first row. If you're close enough, you might see them. So that's really exciting. And so basically our goal is to create pathways for deaf and hard of hearing into open source. We really want them to become active visible participants. And the first step is really to make conferences like KubeCon accessible. Because if you cannot come here, be with a community, talk with people, how can you participate? That's the really important first step. And so why? So we're really, really excited that the Linux Foundation Events Team was able to make these accommodations on such short notice. We're literally talking about four weeks. That was when we provided the recommendations. So really huge shout out to the Linux Foundation Events Team, CNCF and especially Chris Anacheck has been like so supportive from day one. So I'm really amazed and really excited about that. But yeah, our members were not only attending. You might have seen Rob Koch gave a lightning talk. He's one of our co-chairs. And Destiny O'Connor was yesterday here at a keynote panel discussion as well. She's also another co-chair. And Jay Jackson also participated in a keynote in a panel discussion. So that's three deaf speakers at the very first KubeCon accessible to the deaf, which is really amazing. Yeah. And yeah, so hopefully seeing, we're gonna see more of this in Paris and so on. So we're working on that. But again, we're just four months old. So I think this is amazing. And so what we basically do, we're trying to create recommendations because we wanna educate conference organizers first because like Linux Foundation, right? But these recommendations are public and we really hope that any conference organizer kind of uses them as well. Project owners are next, right? Of course, like if we have maintainers here, we really wanna make sure that you know how to make your project more accessible. Employees are really important because it all comes down to employment opportunities. That's the most important thing. But also the community, right? Like so we really wanna educate you. We need your support. We cannot make this possible unless the community really supports this cause, right? So I encourage everyone to learn about accessibility. What does it mean? What does real accessibility mean? And little hint, captions are not enough, right? So we are publishing our recommendations on contribute.cncf.io. There's not a lot there yet, but it's gonna grow. So yeah, learn about it. If you see one of our deaf or hard of hearing attendees walking around, swing by and say hi. We really, really need allies to make changes beyond coupon, right? And again, it really comes at the end. It comes to employment opportunities. That's the most important thing. Yeah. Thank you. I think I also wanted to kind of do a shout out for one of the very interesting word groups that we actually kicked off in the observability tag this year. And that's the Query Language Standardization word group for observability. And as many of you know who use different vendor products, Query Languages have been very specific to each vendor implementation. And this word group really was driven and started by end users, Netflix as well as eBay. And other end users actually kicked this word group off where having these islands of Query Languages is really very, very tough for, as a integration point for end users to integrate data and be able to use it for observability across these islands. So the Query Language Standardization group, which is super exciting in the world of observability, really bridges those islands together. It is an attempt to actually draft up a specification of the common query functionality, if you will, which is used across different types of data to be able to then have a specification that can be taken by any project in the observability space, especially in the CNCF, to be implemented. So that's super exciting. If any of you are interested, please, please join in into the discussions. Several vendors have already been contributing to the group and it's a really wonderful example of collaboration with end user requirements coming in and really driving in common collaboration effort across everyone who is contributing to the projects. So with that, I want to say thank you for joining me up on stage and helping inspire all of these wonderful people and I also want to remind all of you that if you want to get involved, even if it's just to find out what's happening in the space, please join us at cncf.io. You'll find all kinds of, you'll find a schedule that shows all of the different meetings, both of the technical advisor groups and also the working groups and lots of really great ways to get involved in all of the work that we're doing here. So thank you for being here. Thank you for being you and we'll see you out there.