 Let me see. The lightning talk speakers are largely sitting in order. So because of the delay, we're going to move some of the talks until after the keynote so that we don't miss out on lunch. So we will simply stop at one o'clock. And the rest of the keynote comes after Linus Neumann has given his keynote. All right, so let's start with the first. I believe that's actually this one. Kevin, it's your turn. Please, an applause for Kevin. So I will put it full screen. Hi everyone. So my name is Kevin. Yeah, that's a hard to pronounce. But Kevin. So if you want to try, but Kevin, I prefer Kevin. And this is my first time at this conference. And so I'm glad to be here. And thanks to the next cloud team for making it happen. So about me, software developer company called Andela, back in Nairobi, Kenya. So quite a long way from here. Open source enthusiast and Liverpool FC fan. And this is not a Liverpool FC jersey. So, yeah, my talk is about how to get started contributing, right? Three months ago, I didn't know anything about next cloud. And two months later here, I'm giving a talk. So, yeah. So the first, first, I think I'll try to build an approach of what I use to get myself to a contributor level. And I think the overall theme of this is try to build trust, try to, yeah, basically build trust with the maintainers who work so hard on the software, right? So they are good first issues. They are labeled like that on GitHub. If you can filter, you'll see there's a label called good first issue. And when I took this screenshot, there were 82 open issues. So these are issues that are easy to get started with. And you think about it, that means there's 82 potential contributors who can start contributing to next cloud, right? So for this, if you want to really get started, it's a good idea to start with that. So how does this benefit you as a contributor? First of all, you are able to successfully set up and run the project. I think this was tough for me the first time. So just trying to work on a new issue gets you there. You get familiar with how contribution works, for example, signing the commits and stuff like that. And you also set yourself up for future success by knowing how to contribute more and more in future. And the last point is really what I want to focus on, you gain trust, right? If you can show that you can fix that small issue that has been labeled for you, so it shows that you are really interested. And I think the maintainers can really trust in more in future if you start fixing the small steps, right? So benefits to the maintainers, it's a real existing issue. That's why it's on GitHub, right? So if you fix a real existing issue, it helps, right? They're also able to see what are the things that prevent, for example, new contributors from starting, right? So I think for maintainers, they've been doing this for quite a while. So I think they get that perspective of how does it feel for persons totally new at this? How does it feel for them to start contributing and also build a larger community? For example, I say there's 82 issues, that means there's 82 potential new contributors and it's good for the community to have more contributors. So the second point is actually use, next cloud yourself, this way you get to see what it's like as a day, using it on a day-to-day, what potential issues you come across and in these steps, you discover new areas you can contribute. So if you're using something on a day-to-day basis, you're more familiar with how it works, how you think something should work, potential contributions you can make, stuff like that. So these were my first contributions. It's mostly about accessibility and stuff, but you get that different perspective as a first time user. For example, if I'm used to navigating stuff by keyboard and I notice it's not possible in next cloud, then I report an issue and if I can, I potentially fix it. So benefits for you, if you discover an issue, you have to eventually file a bug report on GitHub. So you learn how to do that. It's also the best place to contribute a fix because you discover the issue. More interaction with maintainers, example to ask, you can ask questions on your stack, you can address the feedback and that interaction helps you gain more trust. That's the point, gaining more trust. So for maintainers, it's easier for them to provide guidance and help when you care about your issue, you discover the issue. So they just guide you towards fixing it, helps set expectations. For example, the first time I tried to fix everything, but Kian told me, hey, focus on this particular issue and just focus on that for now, the rest you can always raise new issues and start on them later. Also new perspectives. So for example, for me setting up next load on Mac, I didn't find instructions for that anywhere. I asked around and I figured it out, but I think it helps identify potential issues. Also explore the apps. There's lots of ways you can contribute. There's a mail app which has bounties, which is nice. Yeah, this is my contribution to the mail app. So with this, I learned a lot. So yeah, that's it. I think I've gone through this. So let me just leave you with one final thing. Don't take my word for it. This is someone on Twitter. He really was excited about contributing, right? He's really excited. You can tell. And also I live with this coach. So read it and I hope you can encourage others to do it from that. Just try it. Try it. You never know. Yeah. So that's that's my talk. Thank you.