 I realized I didn't write speaker notes for this one, so I'm just kind of going to wing it. But I think that as we walk into the last day of KubeCon, I thought it would be nice to take some time to reflect on the things that I've been working on in the past, the things that I want to do next in my life, how I feel about the community. And I think the answer is I'm tired. I'm super tired. And I think I've spent this week having these wonderful, deep conversations with you, despite everything that's been going on in the world, everything that has been going on in our lives. And I think the consensus is roughly the same. We're tired. So I wanted to do a quick run-through of some of the things that I've been working on in the past and trying not to trip on stage. So many things. One of the first things I did was co-chair for SIG Azure in Kubernetes, co-chair for SIG PM, co-chair for SIG Release, helped co-create the Kubernetes enhancement proposals process, helped build the Release Engineering sub-project, was a new membership coordinator, founded working group naming alongside Celeste and Chase and Zachary. I am a maintainer for DEX. I am a co-chair for TAG contributor strategy. I helped co-found an inclusive naming initiative and set a reminder to myself to stop clicking the clicker. So I say all this to say that I've been involved in quite a few things in the community and kind of across the cloud-native ecosystem. And sometimes you've got to stop clicking the clicker. So first off, slow down. Everything that you're going through right now, actually, can we take a moment to say how many maintainers do we have in the house? Round of applause or raise your hands. How many people are looking to be maintainers at some point? Come on. All right. So I want you to stop. I want you to slow down. I want you to recognize that a lot of the things that are happening today in your life, they're not your fault. And this is some advice I got from a wonderful open source dragon recently. Burnout. I think one of my favorite talks was a panel that we did after going to AfritubeCon Seattle. I think we were all sitting in our rooms, blackout curtains, shut tight, on Twitter, just tweeting about how tired we were running from event to event, talk to talk. I think during KubeCon Seattle, I did six or seven talks. And it was like, oh my god, I'm so happy to see you all. I've never seen you before. You only existed in a slack thing before to me. And now you're real, OK, bye. I have to go do a talk. And that proceeded for a while. I think everyone was feeling that way. And we decided to get together and do a panel. So we did that panel the last day in KubeCon in Barcelona. We did this panel twice, both there and for open source leadership summit. But it's huge. You have probably heard since then a million talks about Burnout. It's real. Pay attention. Watch out for the signs. I'm not going to go into it because, again, you've seen a million talks about this. But there are a lot of things going on. There's social unrest in the world. And that is not great. There are so many opportunities for us to be kinder to ourselves, kinder to the people around us. We have to be cognizant of that. There's a whole panty going on. There's a pandemic. We have been locked inside of our houses for almost two years now. And it erodes if you've seen the previous keynotes around building the culture of the community as kind of a joint talk between the steering committee and the Code of Condit Committee. Something that keeps us kind of strong and sane is being able to keep that connective tissue between all of the communities that we interact with day to day. And this has completely eroded our ability to do it, right? So first tip I'm going to give you. And I almost don't want to do this talk because, like, Christoph and Paris killed it. They covered so much of what I wanted to say. But I think I am also terrible at slides. I've been looking at all of the slides this week, and I'm like, wow, I'm good at riffing, but terrible at slides. So I'm going to just give you some tips. Stop signing up for things. I think one of the songs that I wanted to play is from Paramore, born for this, right? And I think that this community is so special. I think that we were born to do this. We have these special skills that, like, honestly, you're just some of the most incredible people I've ever met in my life. And it makes me want to do more. And it makes me want to do more and more and more. And I feel like that's the same for a lot of you, right? And so we're constantly angling to want to build more for this community, for the dozens of communities that we're a part of. And at least that burnout thing that I was talking about earlier. It leads to not really understanding where, during that burnout panel, we were talking about the lines between Kubernetes I do for work and Kubernetes I do for play, or the working 14 hours as an SRE, or signing up for so many projects that you can't really maintain any of them effectively. Stop signing up for things. Don't feel that you need to be the person who does that thing every time. And I see a few of my friends making faces right now. We need to figure out ways to scale ourselves. So Kristoff and Paris talked quite a bit about contributor experience, talked about the long-term strategy for the community, talked about the release team, talked about some of the techniques that we've built into the process to ensure that we're not the only ones working on these things, right? So I would say one of the things that I've noticed that has been most difficult for me is recognizing that we don't have an easy path kind of in any of these communities to move from contributor to maintainer. And there is a significant gap, right, between like I can do the thing, I've built a process to help people to do the thing. And this is something that I'm recognizing in my new role. I have this contributor hat, I have this maintainer hat, but I've also got this like sponsorship hat, right? Like a new foundation has opened and you must do this and give this money and talk to this person and put someone on a board and yada, yada, yada, right? Or you have to read this proposal or someone wants to open source this project internally and it's something you've never done before. So I think everything that we've kind of worked on in the community across the last few years around, whether it's the CAPS, the PRRs that they were mentioning, building out the release team, building out the release team has been one of the most fulfilling day to day things that I get to do or that I get to like oversee in the community. And prior to that, I would try to pop into the release team as they were starting up and say, hey, I give this crazy speech. I'm like, we're gonna tear down the release team. It's like, we're gonna build processes and tools that are so cool that we're never gonna need a release team anymore, like never. That hasn't happened yet. And I've been giving that speech for like multiple years at this point. So I stopped giving the speech and I haven't had the time that I wanted to spend with the release team. But I also don't need to anymore. We've got like all of these awesome contributors that have been in SIG release, that there are some things that happen. And I read about them later. I'm like, oh my God, that's so cool. Like how did they, I don't know. And because we have given people, and it's not just SIG release, it's, I mean, I think, you know, contributor experience is a perfect example. Tag contributor strategy on the CNCF level. Because we've built processes to enable people to become leaders, there are things that we're gonna miss. There's things that we're gonna miss. There are things that we are at least out of the way for. And we can't see everything. We can't do everything. So figure out ways to whatever project you're working on, whatever, you know, and this is not even just open source. This is also in your own life, right? There are things that you can put in place to better understand like your day-to-day, the day-to-day of the teams that you work with, not just on the open source, but also on the corporate side, that allow you to move out of the way of that process. So I say to maintainers, and this is my last slide. I'm again, just riffing with you all. So I say to maintainers, try to figure out what fills that gap from contributor to maintainer. Because as you try to teach and you try to do that one-on-one mentoring, there are only so many people you can do it for. There are only so many people you can do it with, right? And if you try to take that, if you try to take that individual approach with everyone, we're gonna go back to that burnout slide, right? Well, no, we're not gonna go to that. But that's how it starts. And you, you know, and if there are things that you think that you're the only person in the world that can do, you're wrong, document it. Or ask someone to help you document it. Or record a talk, a demo, something, right? To move yourself out of the way. And those conversations become, go ask in the channel. Or check out this video that we recorded. Or read these documents that we hacked up just now, right? You create opportunities for contribution. You create opportunities for people to ask questions that you maybe made the assumption that everyone knew. Or you maybe made the assumption that only you can do. So I leave you with figure out ways to scale yourself. Figure out ways to scale that burden from moving from contributor to maintainer. Because I think the imminent threat that we have for so many of these communities are maintainers are burning out. Maintainers are burning out and we don't understand how to put people in those seats to continue the work. So especially for some of the people that I've chatted with this week about this, please take care of yourself. Try to put things in place. Slow down. Stop doing so much. Stop asking for more things. Stop accepting more things. Learning how to say no. Super important. And yeah, that's it.