 So now we have a lightning talk about the prospects of KDE in Automotive and other embedded, traditionally embedded Linux applications, Augustine, Augustine, okay, yeah, it's yours. Okay, thank you for the organizers to allow me to have a few minutes with you. There used to be a time in which KDE had a lot of impact, a time in which the desktop was awesome, right, everybody was talking about the desktop in Linux. And yeah, it was a small world, but we were in the core part of that world. And today, still the desktop and KDE is very important, obviously, for all of us. It's in the center of our hearts. And despite the fact that today we have a better software than ever, that we have more experience than ever, that our community is more solid probably than ever it was before, that we do a few things extremely well, somehow the focus of the software industry, the open source industry is somewhere else. So we rock, but our music is not heard anymore by most people out there. So yeah, we still rock, right, we do. So thinking about how we can put KDE back into the center, the core, the focus, right, bringing attention for others and show all that cool stuff that we do and have, again, a lot of impact, not just in our own world, but also beyond that. I was thinking about for some time, and those of you who know me, I've been fighting for some years, for instance, to go to the corporate desktop and fight a lot for promoting the kiosk mode and other things. So I was thinking, okay, look, we need to find this place in which we can go, and we are alone there, and it's so cool that we can even swim completely naked, right, because we are the only ones there. So we can really enjoy and bring back some excitement, because at the very end as a group you need a lot of excitement, not just internal excitement, but also external one. So I've been working the last year and a half in Automotive, basically doing consulting in processes, how to build distros, and how to be efficient in the software delivery. And I want to explain in two or three minutes why I think Automotive could be a great place for us to be, and what has changed or is changing in the Automotive industry that what it used to be an impossible environment for us, it's becoming a possible environment and will become or might become a great environment for us. So Automotive is going through a disruptive transformation, just like we know we lived in some other industries before. I don't have time for going through the details, but everything that is happening in Automotive, we have seen it in one way or the other in previous disruptive transformations in other industries, especially when we think about it in open source. So now that we have gone through the process of that disruption in other industries, what I believe is that in many open source people that I somehow involved in Automotive believe is that there is an opportunity there for people like us and like always happen if you hit first, you hit twice. So one of the things that are very, very important that has changed in the last couple of years in Automotive is that now there are open collaborative ecosystems that are trying to create assets, code, not just code, but also code together in a collaborative and open way with open source licenses. And that was not there before. So those ecosystems are places in which individual developers can play, obviously if you work for companies you can play also, but foundations or associations, communities like us can play too. That was not there before. There are basically two that I would like to mention because I've been involved in both of them in one way or the other. And yeah, I would like you to take a look because they are creating, in the KDE Spain talk, the Academy S talk, I show a Raspberry Pi 3 with a touch screen and prototype an R&D system for Automotive that is being created in this case for AGL and that is being used in the R&D departments of some of the OEMs that are part of the ecosystem. So and also one very attractive point is that these environments are full of potential investors in KDE and they are putting in these environments millions of dollars for to make developers like us to create technologies that they might use or might not in the coming three to five years. An interesting point is that in Automotive Q is the number one toolkit. So it's a place in which we can go there and not talk about Q. We don't need to sell Q. We just need to sell what we do at KDE because Q is already there. The interesting point, so the following question is, so why do Q need us, right? And there is an interesting point there in terms of the license because as you know, and we were part of that, right? Q changed the license towards GPLB3 model, GPLB3 based model. And as we have seen in other industries with GPLB2 for instance, the reaction of the industry towards openness in terms of license is always very negative, exactly like it happens in other industries before that reaction came into the automotive industry and they have basically banned GPLB3 based code and models, right? So Q now has a challenge in these open environments and it's a battle in which we can really, really help. So there is an, I see as a need for Q to have something like KDE going there, working there and helping fight the battle. A battle that in other words, they're going to lose anyway. Just exactly the same thing happened a few years ago again with the GPLB2 based licenses. They're going to lose that battle. It's just that we can help to fight it. And in this open environment, all these companies, I always put the case of the Japanese companies because they are getting really, really involved. Basically they are learning about open source. So they are using those environments to put engineers there to try to get them out of these left behind kind of attitude that they have. They understand that they need to change. They are heavy open source consumers. Now they are trying to take their steps from being consumers to being producers to being contributors. And they see these environments as learning ecosystems. So we have an opportunity there to do something that we do really, really well, mentoring, helping others to get into open source. And one of the key goals of these environments is to create ecosystems of application developers. One of the main needs that OEMs, entire ones in the automotive industry see is that in five, three, five years they will have to increase the number of features that they provide to the consumers in the cars. And there are not enough applications out there or developers working on applications for automotive. So one of the main goals of these ecosystems is creating those ecosystems, those conditions for application developers to come. That's why they are investing so heavily in SDKs. And we are exactly that. We are nothing but an ecosystem of application developers in some sense. So in many ways our nature, our values, our goals match with what they want, what they need. So if tomorrow, yes, tomorrow, maybe tomorrow, if not Monday, I will bring that Raspberry Pi that I brought to the Academy ES. And you will see how much everything related with the UI sucks. I mean, it sucks big time. I'm amazed that any developer has really developed that and put it there. And now they are showing it all over the world, believe me, seeing four, five hundred people in a private event in the CES in Las Vegas freaking out with this kind of system, with this kind of layouts, it's something hard to digest. We really can kick some butts there. So yeah, I will bring it, I will show it to you and you probably will freak out the same. It's like we can do very well in that kind of environment. So I see that as a way to get in there and bring back some attention based on what we do best. We would have to learn a few things, obviously. The whole ecosystem is learning about open source. So we will find that not everything is perfect in many ways, but they are committed to go into the right direction. At least in these R&D environments, the production is a different story. But we, again, it's nothing very different to what happened some years ago in different industries. You start with R&D, trying to share costs in R&D, and then that rolls out, that open source model runs out into production. First you think that you can control it, and then you realize that the model controls you. And then you adapt your business models to this new model. So working on this 24-7, I see a great place to start with today and hit hard, hit twice. So that was basically my message and done. Thank you for listening. Okay, we have questions. So as I understand it, the mission of your talk is to inspire us and want us to do these things. I think many in the audience probably, you got that point across, I think probably many people in the audience feel that something maybe we should do, and that's a good idea. But the problem is when they now leave this room and they take it with them, we should do that, but they don't know exactly how to go about that. So what are the concrete steps we need to take? What are the bulk items? What should we be doing? Who will take point on that? Okay, that was part... Door autostars. That was part of my... In academia, I had like half hour or 45 minutes, so I had a couple of slides of the first steps. Let me summarize that very quickly. In embedded, and I'm not sure it's going to last for very long, but in embedded they use declarative operative systems, right? And there are a couple of them that are quite popular. The most popular probably right now is Yocto. So for those who comes from the package management based operative systems or distros, there is a learning curve. So Qt is well maintained there, obviously there is a huge business model around Yocto and Qt, we should get there with KDE. Not with everything, but at least enough so we can create demos to start to bring attention and also learn from our side. That's one point. And the second point is we have to go through several... We have to take the journey to get into this kind of ecosystem, seeing how they work, how we can fit there, what kind of applications might be interesting that will make a hit quite easily. And then there is a lot of mindset also. Embedded has always been like very restricted because we think it's very close, right? But especially in automotive, now connectivity comes in place. And we know, for example, from the server world first or from the mobile world that when connectivity came, everything changed. So what today we know as automotive or what yesterday we thought it was automotive is not going to be the same. And so if we are... We need to understand that they are going through a process that might end up like the mobile world or might end up like the enterprise world or might end up in a completely different way. So most of the people here when they approach this kind of new environment says, you know, if it's not fully open, if the rules are not fully clear, I don't want to get in. We don't... Yeah, we need to understand the situation, how they are going and get the attitude of let's help them shape it. So these end up in a different way that the mobile has ended and it looks like more like the enterprise world. So I think those three points are... And I have another three or four, I can describe them in the slides. I can put the Spanish slides or just even translate them. So how about we pick some sort of industry event in that domain and we try to get a boost there and then we figure out what do we want to show there? Actual things do we need to create to have that to show and then show it and talk to people? Yes, it's the industry events. They are like two, three different classes, right? The Linux one, very focused on Linux. Those are easy to reach for us. Linux Foundation through AGL or the Genevieve Alliance would be more than happy to host us there. So we can show what we do. It would be showing it on top of their distro, basically. And then there is a second type of events which are industry events that are very focused on specific areas related with software. Now autonomous driving is very important. Those... It's going to take us a little... It's a little harder to get there. But if we go through the first step, maybe they help us to get there also. There are companies that are like the one I work and others that are getting into that industry. I think that the Qt ecosystem would be also very interesting to take us there because they are already going there. There is a third type which are fairs. And well, I'm not sure that's very interesting for us at the beginning. Well then, let's pick one of the Linux ones, package frameworks for the distro, get Plasma Shell running on it and take a system there and show it and talk to people about what the framework does. I would love to see a couple of engineers and I definitely will help with everything I have. Okay. It's something that we can really do. And it's not that hard. I mean, it's not that hard. Yachto is not an easy one, especially coming from the distros that works. Going through Yachto, it's a different story. But hey, the embedded guys that love that thing because the world was really awful for them before that Yachto thing came. So yeah. Okay. Thanks. Thanks. When you say Yachto is hard, do you mean the governance of Yachto or do you mean getting your own meta? Yachto, in my opinion, and if there is somebody from Intel here probably wouldn't agree with me, Yachto is very expensive to maintain. Yeah, because I've been working on Yachto for the last six months and I wouldn't say it's that steep at learning curve. So. Yeah. Okay. So it's very expensive to maintain. That's something they are working on, but today it's a huge challenge. Go ahead. I was going to ask, what do you think if instead of the automotive industry losing their resistance to GPL3, they decide to buy commercial licenses for Qt, which is obviously great for the Qt ecosystem because it brings in money to the Qt company and we all benefit from that. On the other hand, how would the KDE software, free software, fit in if those automotive companies are using commercial licenses and still avoiding the GPL3? Okay, basically how I see it in a few words, the Qt model is, in terms of license and that could create some debate. As I see it is either you contribute back with code or you contribute back with money, right? So on the commercial side, we want Qt to be a sustainable project, right? So it makes sense that people contribute back with money. But given the amount of software and innovation that it's coming and especially will come into the automotive industry, a lot of that innovation is not going to happen inside the companies. It's going to happen in open environments where a lot of companies and volunteers share that exactly the same that happens in the enterprise world. It needs to happen like that. There are no Googles. None of them, they are turning into changing and becoming software companies but there are no Googles. So that is not going to happen in my opinion. So in those environments, the GPLB3 model is a very good one. So I see that and I see ourselves fitting in those R&D environments in the same way that companies are not shipping KDE software in their corporate desktops. We can make a very nice living without having our software shipped in our cars. And when I see our software, I mean the applications, right? But because there are a lot of software that we do in corporate desktops are there. A lot of software. It's just that it doesn't have the stamp of KDE. So the same might apply. But then we get hired by those companies. Those companies finance back their projects somehow, allow people to come to these kind of events. I mean there is a lot of value in being visible and play an active role in R&D environments and get back. Maybe, maybe our role is not to get a KDE desktop in a car. Maybe that's part of how you define success. I had a talk, a community keynote, right, in 2012 defining what is success. Maybe the success should not be to have KDE desktop in the car, maybe. I guess we can wrap this session up here. We're actually running about five minutes late for the next session, which is the last one for the day. Sorry? Yeah. Okay. Okay. Yeah. Okay. Okay. Okay. Okay.