 Okay. Let's start like that. I have a story to tell and the story is the day I became an open source developer and this time I want to share insights from my learnings and there will be no technical detail at all and it's just about the learnings in these 12 years of developing that I find very interesting. So, WordPress can handle many languages. We know that and we know also there are functionalities that we get from plugins, not from the core itself. So, and it was in 2011 like that. There were even less, there were even less plugins that wanted to fill a gap like WPML was already there, some other plugin too and however in 2011, in February or so, they decided to become a premium plugin and it was for me like, oh, I have to pay for that. I believe that was, it has to be in the core. I have to pay. No, I'm not okay with that. And I saw already there was upcoming WordPress 3 with the multi sites and I thought, okay, let's come to a decision here. I will step in. I will create a plugin. I will use multi sites and my plugin will be for free. I don't want that anybody has to pay for stuff like that. But that's my opinion. It has not been the opinion of companies for sure. Okay. In that time, we already had some debates about premium plugins and there were, at least in my bubble, something like, a lot of people they were not okay with things like, okay, there are, there are these premium plugins but democratizing publishing like WordPress wanted to do was something like that wasn't fit really well together. And okay, in these last 12 years, that from, from the point that we said, okay, we are not okay with that till companies now being part of the community and giving back to the community, that changed a bit and I'm a bit more relaxed about that part, at least. But I have to say, there are still some things that they bought on me. But at the end, I understood also in time that we have also free plugins. They have complex ethical decisions in their code. Let's say it like that. There are two things I wanted to address, at least today, talking about the lock-in effect and talking about advertising at the dashboard. These are two things I'm not okay, still not okay. That's my opinion, but I think it has to be addressed at least from some people. If you don't know what the lock-in effect is, it's easy to understand. You just deactivate all your plugins and if your site is still alive and you can read the text that you wrote, then you're not locked in. Then you are okay with that. Probably you are not because we will have some of these plugins that lock you in, not that they want to, but the design of the code is like that. So there's nothing to do. Even worse, I believe, is that we have constantly upselling in our dashboards and that we cannot even click on some of these advertisements to not to see them anymore. Some, yes. A lot of them, no. So I think we have to talk about that more often. If you think about, okay, but these premium plugins, they make money and you open source developers, what are you doing? You are not making one, obviously. So my wife even said something like, she always thought that a programmer, as a person, as a money printing machine is not using it. Nobody gets the idea why. And for her even, that I give software away for people, they obviously need the software. It was like, it's exploding my brain. So I cannot understand that. And, but at the end, it's not trivial, not easy to sell software to create a company, being a business man. That's a decision I did not want to make. And I find also that part quite complex. So no point here for me to making money out of that. So despite that, at the end, if you do open source, it's also rewarding. That's not just money. That's rewarding. An expert in the field, maybe indirectly, you get better contracts. So somehow open source can pay back. And if we talk about payback or sponsoring, that could be interesting for open source developers anyways. In the WordPress directory, you have a link for sponsoring and even for GitHub sponsors as the new features regarding sponsoring. You can also, applications can now see their dependencies with open source. They can finance that directly from GitHub. That's quite a cool feature. And so obviously, bigger projects with a lot of users, they can have their profit, they can profit from that. But smaller projects, obviously not. You have still the problem sponsoring. It only comes in, so that is to understand. So what remains is a fun of programming and or maybe looking for recognition in the community, stuff like that. But if you have no sponsoring, and maybe you are not having really a cool contract with company that's even paying you for the time on your open source projects, you will work on your free time. And obviously, busy stays for support for plugins. For me, it's Saturday and Sunday. So yeah, that's a problem that I can have, obviously my family with me. And somebody could also burn off from that. So maybe you have to think about that. And if you still want to become an open source developer after saying that I said that, where could you start? Obviously, you see a thing like a problem and you want to resolve it. And you want to start writing software. You could do that in another way, which is probably a bit wiser than that. It could have something like problem discovered. You found a tool for a solution. Okay, it's an open source project. Fine. You can collaborate with that project. And there are a lot of open source projects looking for developers, for co-authors. It's not like they think like, oh, I have to be the gatekeeper of my project. I give out my roadmap. I don't want that. In reality, it's not like that. Because these projects are often more resistant. If somebody really has no time anymore for a certain timeframe, another shoulder can then take just that heavy load. And often they are much better in quality over time. So obviously, open source is not just open source developers they're doing their private projects. They are also companies. They are maintaining open source. And here's maybe, if you think about what was itself, it's quite important to have a community. Because obviously companies, they don't do that just because they want to be good in the world. They also have to make money because they have to pay their bills and developers and so on. But a community here would really balance, well, these interests, users, community, company. And in that part, open source developers, if there are small projects, they are doing also their part for the diversification. At the end, it's like they give an opportunity because you can select another project instead of the bigger premium project. And that balances the whole story a bit out. I find that very important. And I have to finish. What I want to say, what most open source developers probably wish for, that's what I learned. It's more time for the project, but also more time for more free time with family. Not having support on Saturday and Sunday. We have also other days in the week. And active help from like-minded people who will do marketing, documentation, pull requests, whatever you like. And projects like that, they get really, they are a nice thing to work on. But also there's recognition for everybody because in GitHub and other platforms today, you can see who did the part. And it's also good like a good business card for everybody saying, okay, I did that. You can show that even to your employer. Okay. Thank you.