 Okay, hey, it's me again, sorry. Can I have a quick show of hands? Who here is never stressed when working and has plenty of free time left over? Yeah, that's, okay, some blessed people over there. Very happy for you. And so yeah, that's really a problem. So let's talk about how we can fix that. I hope that it's very easy to read for the people in the back. I wasn't sure if it's big enough. So making yourself obsolete. This is basically something that I've been doing since a few years because already in the beginning I was sure that I wasn't able or I wasn't gonna be able to do all this design work that we're now having to do on my own now. So I was already making sure that, yeah, I was kinda making myself obsolete, making the community inclusive to get other people on board. And so there's a few steps that I wanna share with you. How I do it, how other people do it, what kind of worked and what is very easy also to implement. And that's four steps. First step is be transparent and they're sorted by difficulty, so to say, or time investment. So be transparent is the most simple one, onboarding, then building a team and then telling everyone about it. So the first step is being transparent and welcoming. So these are two very quick hints for that. Having a helpful read me. I think I said it two years ago or maybe earlier also already having a screenshot in the read me, having instructions how to install the app for a developer environment. Because me for example, I'm among all your technical people but I'm for example a designer and I don't know by myself that I need to do make in a terminal, right? And a lot of other people also don't know that if there's a make file that you have to do this magic command. So just have a section saying that. And yeah, other things for example, if you need to NPM install or any of these esoteric tools, right? So another thing is having the tasks in public. So don't have your private to do TXT. Don't actually don't put them in your next cloud because no one else will be able to see them and you won't be able to really tell everyone what you're working on. Rather put them on the platform that you're working on which in our case is GitHub. So put them on there, use tags, use milestones, maybe use the project board, whatever you like but basically offload your to-do list on the public tool. So that leads us to the next step that's onboarding. So actually getting the people involved. And that is when you have all your issues in the issue tracker, you can tag them with good first issues. For example, Kevin also said in the beginning today that good first issues are really great starter point and the amount of good first issues you can basically equate to the people that could possibly contribute to your project. And so what they basically are is almost a fix already. So you basically describe everything down to almost the point of doing it yourself but not doing it. But like saying for example, where you would fix it, the file name and how you would do it, what you would suggest how to fix it but that as an issue and then somebody else, somebody else can pick it up, might be a typo or like a pixel thingy, some small stuff. And then the other thing is involving everyone or anyone. Anyone who opens an issue, anyone who brands about it on Twitter or anyone who leaves the comment in the app store, rating, you can involve anyone. Anyone who is excited enough to leave a comment on any platform that you use is excited enough to help you. And they, for example, everyone can review a pull request. A lot of people don't know that they can review a pull request because it sounds very technical and it sounds very involved. But if you actually ask them, hey, maybe you wanna review it and you show them how, then you can do it. Now the thing is building a team. That's the third step. So have a group on GitHub at nextcloud slash app name, for example, have an IRC channel or other channel, whatever you like. We mostly use IRC channels. Yeah, help people on the issues or maybe if you see someone who helps other people on the issues, ask them if they would like to be the person who helps people on the issues or on the forum. And that is also an honor for a lot of people that they are then the official helper person and that takes work off your shoulders. And then, of course, invite people to the conf and also regarding diversity also. For the next conf, for example, I would suggest that every one of you checks in their circle of friends if you have a person from an underrepresented group who is slightly technically minded or is interested in the topic, invite them, bring them so they have a person who they have to already introduce them to the community. And the last thing is telling everyone. So check app ratings, what the people say, write blog posts about it, go to meetups, not only to nextcloud meetups, JavaScript meetups, PHP meetups, anything, and also give a talk there, not only at the nextcloud conf, but also these things. And yeah, that's basically how you make yourself obsolete. Come to the workshop later, it's today. And if you hate me and don't wanna listen to me any longer, there's a great blog post by Mike McQuaid of GitHub and Homebrew where, yeah, he basically has a very similar topic where he talks about it and there's a talk about it to check that out. Thanks, that's it.