and I think for our part of preserver and you're making, or you're helping make it happen that way. Both Goodfing and Qt, they will have boots because they are top tier. Well, reach out and ask what they do. I'm sure that they will appreciate it. Also, thank you very much to the University of Macedonia for hosting us here. This also makes it happen in a very, very logistical and practical matter. Thank you very much, University. On a more pragmatic note, we're gonna have a coffee breaks. They're for free. They're between 10.50 and 11.15. It's on your badge. You will see, well, join, bring the coffee and talk to the people like I was mentioning before. There's gonna be lunch. Lunch, you had to register for it though. If you forgot to register for some reason, well, go find the people in the registration booth and tell them, or you can find lunch anywhere in the city because here there's plenty of food. Over here, it's all great, so that's also fine too. There's places that you can order water. I was asked to say, don't drink from the toilet or the bathrooms. Yeah. Sure. Well, as the registration and the Academy team, they will tell us all about the water. We have a great code of conduct that you must abide for. You have the contacts on your badge in case that you have a problem which you shouldn't have, but, well, no, it's there for you in case you might. Remember to wear your badges, unlike I'm doing myself right now. Also, it's gonna be needed for the social events.  Note that there's colors also respect other people's lanyards if somebody doesn't want pictures taken off them. Well, don't take pictures off them, right? That's this hard. We have hashtag, hashtag Academy 2023. If you do things on social media, use it and that will help, well, the world will notice what we're doing. So that's kind of what I wanted to say to get started. I'll leave you with the keynote very soon, if that's the time. They'll tell us all about space and preserver. Thank you. And thanks for joining. So maybe we can do a Academy t-shirt in them for you. So I'm wearing my last year's Academy t-shirt, it's 2022 and I can see one there, Albert, good to see you here, Marco. We have a 2021 Academy t-shirts in the room. So we've got one, two, three, all right. 2021 is presents. 2020 had that amazing color scheme, yes. Excellent. Two was Milan, wasn't it? Was great. We have the 2019s in the room. That was Alalia with the, you're right. That was an amazing t-shirt. Any pink shirts? So before that was Alalia with the orange, not bringing your old Academy t-shirts. What's going on here? Okay, that was 2012, oh, there's a 50, yeah, Berlin. Okay, we got a ton of that. And everyone else who's wearing safe shirts at home, we've got it there. Yeah. And we've got one old guy up here. And now, the space is easy. It's not. So, hi, I'm Alferios Cosmas. You can call me Alcos, it's usually hard to pronounce my name. So, I'm representing Libra Space Foundation, I'm its vice chairman. And I'm gonna talk about how open source actually empowers getting the space, the Libra way. So, before starting, I just have to say that I'm really, really happy to be here. I've been a KD user for the last 23 years or so. So, yeah, since KD2 came out. So, I'm really happy to be with you. I've never actually expected to be here with you. So, how all this started? The thing is that, as most interesting stuff, starts with a small group of people, friends, whatever you like, that met the local hacker space in Athens, Greece, which is focused on open source technologies. That started around 2011. At 2014, during the Space and Challenge hackathon, we started the satellite ground station network. Same year, we won the Hackaday prize. Approximately 200K thousands.  It was a lot during the worst economic crisis in our country. So, we say, hey, let's make a nonprofit foundation. So, use all that resources in something we love and share back with the community. So, 2017, we actually had in orbit our first satellite, UPiSAT, which we did for the University of Patras. And 2022, our first open source satellite deployer. That's the second one. So, all these, this work is powered by vision, by open source and openness in general, open governance, open hardware, open data. And what we seek to do is to make space accessible to all. To do so, we develop stuff from ground stations to satellite missions, and we adhere to a set of values. We have our own manifesto, if you'd like. Mostly inspired by the Mozilla manifesto and the Outer Space Treaty. And the whole idea is that we use ZPL version six, say, ZPL, LZPL, CERN licenses, open source data, and we adhere to trying to document everything, all our processes, all our governance, the way we do stuff on our documentation efforts and our representatives. For an organization that works in space, that's a little bit weird. Most such organizations, especially the ones not funded by governments, don't do so because most of them are, I hope, for profit companies or they are just commonly not very open. You see, what we do, actually, being an open source organization allowed us to create some interesting projects like satnax, like UPSAT, you can actually see, in orbit, it was launched by the International Space Station, so you get a nice picture from a astronaut. And we've finally tried to do a lot of hardware development, mostly, nowadays, and a lot of software development that will create more open source data for space. Why do we do so? And why do we believe that's the way forward? Well, first and foremost, open source allows for rapid prototyping and rapid iterations. For example, the satnax communication system. The little module we created, it's on over there, which is designed for UPSAT analysis, signal analysis and communications. It's actually also forked by the good people from the Aristotelian University of Soloniki next door from here, and they use it, they forked it. They managed to use our design on their own future UPSAT and that's really interesting, because that's not the norm in space. We've seen that this design can also be used for ionospheric disturbance analysis, which for us, it's interesting because we didn't thought about it. Some other people thought about it, and because it's open source, we can actually see how it works. They can say, you know something, you can also do that with that hardware. We never thought about that. It also allows for global collaboration, meaning that the satnax network now has more than 400 ground stations in 50 countries all over the world. You can actually get data from Taiwan, from Russia, from the United States of America, from the Azora Islands in the middle of the freaking ocean, which is really interesting, in my humble opinion, because that's something usually only large superpowers could do a few years ago. Nowadays, with open source and a huge community, you can actually do stuff and lower the barriers of entry because, for example, for a team or a person to participate in satnax, you can actually need Raspberry Pi, pure antennas, a simple RTOSDR, and you're good to go. I mean, I have one of these things on my rooftop, and it's simple, and it's a way to give back to the community and a way to participate in a space project, and also it's a way to participate in projects that you have really interesting. So what we must understand is that using open source in space is not just developing open source. We prefer to dog food open source, if you like, meaning that you have to use open source solutions all over your stock. You have to use open source solutions for daily operations, for community operations, for development needs. It's not only something, I'm gonna create an open source community and use everything closer. That doesn't go a long way. You use, sometimes you have to actually assist the development and actually lead the way to get the features you need, and have daily interaction with open source project use in order to get some of their good practices and good ideas, and I'm not meaning only about code, I'm not meaning about, ah, yes, they did a really nice thing in that community, so I'm gonna get that. There are good practices and good community management ideas or good implementations of things, among several projects, and having interactions with other projects, I can't read. You can actually get what other people are doing try to copy the right stuff or the stuff that suits you. And let's be honest, using open source solutions can allow for interoperability within the organization, especially an organization that's mostly remote and distributed around the world, and with external entities. For example, we are working with the European Space Agency, we are working with Harvard, we are working with several spaces across the world. Having open source tools allows us for better communication with our partners. And there are some of the open source projects we use, of course we use the Linux, apparently, but the thing is that we try to use as much as possible across the board, but there are challenges. And being an open source organization in space creates some difficulties, maybe, because let's face it, space is hard, it can be really hard. Orbital hardware has a few ways to be fixed. As it's long, you can't do anything about it.  Well, but like, but open source can provide a solution for more robust systems. There are several regulations, several standards you have to follow, but following standards. There are some ways, so you can actually create framework on them, you can work with the standard and actually start to implement ways, to find ways to implement the standards as long as they are not locked in the proprietary way. We are seeing these coming, diamond time again, there are regulatory issues, and what we believe is that as long as you try to be open and try to implement stuff openly, you will provide solutions for all, and that's key. To be honest, space used to be the domain of superpowers, of large corporations, of people with resources. Miniaturization allowed lowering the bars of entry. Lowering the bars of entry, open source in your hands can be a catalyst in lowering the bars of entry. Now you can build your own CubeSat in your local Hikerspace, and you can actually go in Athens and see people building satellites in the local Hikerspace, it's a little bit crazy. Because you can actually see people working on a space-rated hardware, while other people are hacking something really silly, which is really nice in my opinion. The industry, this industry at least, it's not the only one, is full proprietary solutions and secrecy. Secrecy has been a staple for space, many, many years now. And nowadays we see that the impact to innovation is so huge that traditional entities, private public entities, are keen on checking out open space, they've not yet gone full open source, not all of them at least, but you can see that the European Space Agency, that's to promote open source, NASA has open source repositories, there are processes, there's work to be done, and we're trying to pressure things going forward in the open source way. But let's face it, space is also a very capital intensive industry, it's a huge amount of money to put hardware in order, ridiculous amount sometimes. So that impacts innovation and impacts open source too, because we are used to open source creators, to create something and have it on our hands, able to use it without any intermediates, without having to invest huge amounts of money to have it even work on its own. This is not the case in space, but the case is that because it's so capital intensive, and there are opportunities to actually be able to fund open source development, we are actually an organization that's sustainable, has around 15 to 20 employees, and it's very, very, 15 to 20 employees, most of them are engineers, I think I'm the less engineering one, and the thing is that what we see is that we are able to sustain our organization for the last eight and last years. We believe that certain, the same thing, state is KD, isn't indicative of the common grounds open source organizations like KD, Server's Liberal Space Foundation, both foster communities, both try to democratize, if you like, access technology, and they're thriving through community. We couldn't build stuff without our community. We couldn't build stuff without open source tools, like kitlab, like a big, blue button. We couldn't be the way we are without being collaborative and transparent in what we do. What you're trying to achieve, what you're trying to build, is similar to an extent, in what any open source organization does, being open, promoting open source culture, openness in general, and creating a set of open tools for people to use. Of course there are differences, because let's face it, as I said before, and I'll say it again, and I'll reiterate it continuously, space is hard. There are domain-specific challenges. There are tests you have to do, there are regulations you have to fill out, after, nice. And while working with that kind of environment, you may feel a little bit changed in how things work. You may think that I can't do the things I would like to do because I want to break some stuff. You can't, it's space that won't let you break stuff in orbit, and in general, they don't let you break stuff around in space, in space agencies, I don't know why. Most of our work is purpose-driven. That's not really similar to what KD does, because KD, actually, in my humble opinion, please, correct me if I'm wrong, KD actually provides a generic computing experience. You can use KD for whatever you'd like. That's a strong selling point of KD. I'm a KD user, but my, use scenarios were different across the many years I've used it. I used to use KD to just browse. I used KD to develop stuff, and it wasn't nice for anyone involved. And now I use KD for developing open-source hardware in space. Well, the thing is that what KD and projects like KD do is provide a very important common ground for us, a very important infrastructure to work with. We can actually use stuff around. And especially, the way we see it is that the way I'm seeing it, at least, is that KD is flexible enough to adjust to my special user needs as they change. This is really important in the way I see it. As I was saying, though, we need to engage the community in different ways than KD, meaning that as we work with a very specialized bunch of people, scientists, space engineers, space agencies, they need that engagement in a different way of things. You need more formal engagement sometimes, you need to be a little bit more in the box, if you like. But that thing also changes in the space industry, because the space industry has learned that you can innovate always in the box. The other thing with liberal space is that our deadlines are very hard, because honestly, you can't say to the launch provider, you know something, guys? Can we postpone launching that big rocket of yours because my hardware is not ready yet? Can we? No, I can't say that. I can't say I haven't passed the QA measures. They needed for their hardware, their software, because this has to be done. I can't say I didn't do environmental testing because I have to do it. I have to vibrate the thing before it goes on a rocket. And the thing is that, in contrast with HIDI, we do have a hardware committee. We do develop hardware. Developing hardware can be, well, funky hard, but also creates a focus on a singular platform. This isn't the case for KD, because KD has to be used on any of these things, or hopefully in the future, it could be used on our phones, or in any device we use. This is different, but also really interesting in the way such a community must interact. KD has to work with a million devices and a million of systems doing different user scenarios which can be really complicated or really extreme. Yes, there are 10 users out there that use this weird driver, and you have to figure out a way to use that on your system and create a UI around it and have an experience similar to other KD users' experience. For me, it's crazy. I don't know how you people do it. So, me. But also, it's something that, it's out of our world. We can't believe that it's done, but it's done. We've seen it. We've seen it on our own machines, to be honest. And the other difference is that when you people work and develop KDE, developing KDE is more or less instant.  I do stuff, I sweep them away, I beg the gods or whatever to not skip the launch day because, you know, the weather is bad. Oh, poor you. Next month. And the other thing is that you stay in the unknown. You don't know how stuff will happen. Sometimes, without your own, I don't know, input, without your own, without you messing around stuff, you have that. That wasn't pretty.  Some people here, I can see, that have seen and worked on the code of this thing. There used to be Picobas, a particular launcher there, and two really small satellites of Libra Space Foundation, and four Spanish satellites on the Picobas because we decided to assist our friends in Spain. So we got the thing in the launch pod. It started flying and kaboom. After one minute of showing the flight, rockets started wobbling and they pressed the button. People worked on this. Worked hard and this thing worked and didn't. And that's a challenge faced by such organizations that are focused in Spain. You might work a lot and things will fail. And failure is an option. Well, if they didn't press the button, it would be a worst failure, so I understand that. So, what we learned so far on our journey in space in the last eight years, no, longer than a soundtrack set of seasons. So, first and foremost, we learned that sky is not the limit for open source. Open source can be everywhere. It can be in orbit. It can be in Mars as APL showed on their little helicopter. Challenges can foster innovation. The challenges and the regulations and all that regulatory framework we have to work might allow you to change your mind, to make it more flexible than others and try to implement stuff in a better way. The way we see it, I think one of the most important things we have taken into account is community participation. We couldn't be here. We couldn't build a seismic schedule which is the biggest satellite ground station globally. Without a community, without people building their own ground stations, without people suggesting, ah, you know something, guys. You have to do that because that would be more efficient for that driver over there.  I couldn't have thought that. And it also allows for input in domains that you are not used to work with. I am not a space engineer. I'm trained in healthcare. I'm a nurse, actually. So, I used to be a nurse. And having people with domain-specific knowledge or even more. No domain-specific knowledge, but knowledge in certain characteristics of physics or stuff like that can allow for innovative solutions and can allow for a community to go further. In my humble opinion, ah, that collaboration sounds like a collaboration. Collaboration can have a geometric impact, of course. Meaning that you can actually see that it's not linear. After, ah, we've seen that when there's an amount of people in the project that starts getting a little bit more crowded, has more committees from other people outside the regular, things change and go faster and faster. Sometimes it's difficult to keep up, but they're faster and faster and you see that the project started going slow, mostly working, goes crazy fast because the community is pushing the project forward without you even expecting it to go as fast as it goes. Ah, and we actually learn that we have to learn from our peers, learn from other open-source organizations, learn from other space organizations, get the knowledge, an experience and wisdom, if you like, of the open-source community. We've seen it with other organizations too. I think we've seen it with KD. You people have experienced stuff we haven't. You've seen how difficult it is to migrate to a new environment. We've lived that with KD3 to 4 and we survived it. But the idea is that you learn and the right things your peers do and the wrong things your peers do are actually a way to learn stuff. And we believe that an open-source organization like ours or like you has to learn from the mistakes and the right choices of their peers because we have a great thing meaning that what you do and what Mozilla does and what Debby and I is actually a learning process for all of us. You can't implement the same things always because we are not the same organization, certainly, but you can actually learn stuff from each other. And you can also collaborate either directly or through umbrella organizations going forward. We have, in my humble opinion, and I think that's shared with many people in the KD community, and other open-source communities, we have to collaborate on common challenges. We have to collaborate on challenges such as policy coming in our countries in the United States of America and have to learn to figure out how to protect our users and protect open-source. I'm open for your questions. Really would like to open a dialogue and start chatting because, okay, doing a presentation is cool but chatting is better. Of course, you can always send me an email at Delcos at LibreSpace to just say hello or chat and discuss whatever issues you may have. But I'm open for your questions, if you like. Certainly. Let me see. Yes, that one. So, it has the Kaikai logo on it and the question is how much of that is going on? How much do you have to design? How much hardware do you have to design and make yourself? Or can most of the hardware that goes into the satellite come off the shelf? Well, here's the thing. We don't actually design ICs yet, I would say. There's always interest and if my engineers would have their own thing, I'm pretty sure they would design their own ICs instead of the kind of stuff. But bear that, all the design is custom. Excluding components like that SNA thing or that screw over there or, you know, resistance and stuff like that. The design, the PCBs, the metallic designs, everything is custom and it's open source. Designed with KitKat and FreeKat on an open source repository you can actually download and build it yourself, put it on your own rocket and call it a day. It's a really interesting project. I... Yeah, that's a... That's a really interesting one actually. That's SIDLOC. SIDLOC is a satellite identification and location protocol. We designed this for the European Space Agency and the thing is that it actually emits a beacon that allows for... It's not a satellite, it's spacecraft action, spacecraft identification and location. So why this thing is interesting? Well, it emits a beacon, a certain kind of signal which allows for identifying a satellite or a spacecraft easily and allows it to be located easily using Mach machine. So the thing is... The interesting thing is that having an open source protocol is cool. Having a protocol that is actually implemented in an open source way is way cooler and that's the way we should work because if we went out there and built a proprietary solution which could... What's the meaning? Why? Why should anybody adopt such a thing?  It's five by five centimetres. It's huge. And this design, this actual design will go in Ariane 6. It's a inaugural flight and will actually allow us to track Ariane 6 using satellite. And yes, you have to use kick-out on that and yes, you have to use free-cut on that and you have to do everything open source if you are willing to do something that's impactful for the space industry. If you are just trying to make a buck, then, yeah, go full proprietary. I don't care. I'm trying to create something that will have an impact to people, to universities, to universities, to even corporations. Someone trying to build their own satellite because they're making something. Yeah, you have to go fully open and let them do their commits and let them do their forks and go on. Other questions? Yes, please. You mentioned ground stations a couple of times. What is a ground station and is that something that we, as people living on Earth, would want to set up in our backyards and what does it do that will help people? Yes. So a ground station can be... That's a little bit over there. Something like that. I have to admit that there is also a bigger ground station in the network. The Dwingelio Telescope in the Netherlands is actually a southern ground station which is a little big for my backyard. I don't have such a big backyard. It's a little bit bigger than my house, actually. So the thing is that people create southern ground stations or actually make their own or use all their type of hardware used by radio amateurs to build one because they like to share data with their community. Some people find that interesting because it can actually be an easy weekend project for them. It wasn't easy for me, but I'm not good with black and white characters at all. So... But the thing is that people like to assist other communities and other university teams. Most satellites... A ground station actually receives data from a satellite with orbits, lower orbit. So it only has around five, ten minutes per day to actually track the satellite. So if there is a university team like the university team at next door that needs data they can use my own ground station they can use my friend's ground station in the United States or they can use a ground station in China in Taiwan. They have a book in Connecticut or in Russia. And actually do stuff. So in that case they mostly like to assist other communities. So... Regarding HRAD, as far as I know most of the stuff that is designed to go to space have to be subjected to very rigorous testing. And the testing equipment to do that is very expensive and also proprietary. Under even the specifications most of the times from my experience even the specifications like dimensions of a vacuum chamber for example are under NDA2. Do you have any solutions you are doing yourself in order to reach the same standard that is required? That's a great... almost insider... you... So... He is literally from the university next door. I know... I know him, okay? I know people. So... Yes, we are trying to have our own designs. We are trying to build our own vacuum chamber. We are trying to build our own clean rooms. And we want this all to be open source documented. Right now what we do is go to the University of Catalonia and do stuff. There. And we pay stuff to do stuff there. We have to pay stuff to the environmental testing. We have to pay stuff to do vibration checks. And in the future what we will be able to have our own stack and the stack available to open source projects in general. And the infrastructure, the physical infrastructure that is an open source project can send their own a hardware to be tested. Hopefully with the person together to monitor the procedure because I am not... Yeah. Other questions? So I have another similar question I suppose of the collaboration with different projects and being open source is amazing and kind of have you been able to have any success with getting some of these proprietary companies to open source their stuff so kind of like coming from the other direction? No. This is it. Especially in space. Space, as I said before is a very, very complicated thing I think. And people tend to be very protective of their version of things. Usually not something very interesting. Sometimes you've seen devices in hardware that are used around and sell them by big companies. They sell so much money for it, right? Why? It's so simple. On the other hand yes, but that has orbital pedigree as I said because it's been there for so many times whatever hell we want for that. But the thing is that these companies most of these companies see that there might be another way to do this. Interestingly the space agencies say that there is another way to do stuff because the space agencies want to protect their own interests and their interests of what people there represent. So maybe the space agencies say yes, I need that open sense. And usually that's where we come and say okay let's work together with the community let's work together with large integrators maybe even I won't say names yet because I haven't found them yet. But so start to see people start looking about open source and space. They see that it might make sense it's not a good feat for our business plan but yeah maybe some other time we will see that he's changed. The guys that are at next door they've seen it already they've seen it they already used some of our hardware right? Then they already thought it and they already put it on their own way and they see that they might even go forward in making their own open stuff because they are cool but how many people are there? I've seen it all recently I think it was quite bizarre a tube set from the quad or I think I'm not sure that recently got released as an open source project and it's truck which I've actually seen a really nice graphic display of working in a space it's really cool and the thing I see is that we might see change from university things first pushing the envelope forward making open source solutions because they need them to work better and because let's be honest about it the guys next door might not always be next door they might go to the industry they might go somewhere else they might change career and become artists but the thing is that the source code has to remain there they're a public funded university they need to use their creation for the betterment of everyone else all the questions thank you we're sort of out of time so I'm going to use my session chair position to ask the last question oh you've gone to space with open source where are you going to go next wow still we are going to space but the thing is that we only reached lower orbit right of space beyond low earth orbit thank you for everyone who is not going to space today you may want to go to the coffee break which is right now I'd like to point out that your printed badges contain a schedule and that schedule is wrong please use the website polls presented moderated by Lydia and talked about by Carl Nate and Joseph before we get on with that I'd like to remind you there is a program in your badge the program is wrong use the website but your badge is useful for other things it tells us the people around you who you are and if you look on the inside it will also tell you things like bus schedules and the wifi password so examine your badge it's full of good stuff and an incorrect program that said I would like to hand off to Lydia who is going to run the KDE goals panel thingy thingy take it away has become to look at what has been happening around the goals that we voted on thank you and that's what we are going to do now and we are going to start with Nate to talk about the automation and systemization goal so please welcome Nate hello everybody welcome to the panel so today I'm going to talk about the automation and systemization goal this is a goal that was chosen last year so this is going to be kind of a mid cycle update so let's get into it first let's start with a little bit of background about KDE and why the structure of KDE makes this goal important all of us in KDE are aware that KDE is a multi-generational organization and KDE's contributors have a defined life cycle as well as different stages that we often move through at the beginning we have people who start out as students or young hackers in university these people in this group are marked by having lots of time, lots of passion lots and lots of contributions to KDE then time marches on as it always does people become young single professionals and their KDE time becomes hobby time at this point in time people have jobs and jobs take up more time and as a result KDE contributions tend to fall off a little bit then time continues its vicious cycle and people become professionals established in their careers they have families and KDE time often drops off quite a bit and then finally if all goes well people retire they become financially successful they have time for KDE again but one thing you can see with all of these different groups that people can fall into is that the amount of time that we have for KDE changes that means there's a lot of turnover in KDE one thing we're really good at is making sure that people cycle in and out and learn from each other but it's really important that we keep the knowledge that people bring to KDE and it must stay in KDE people bring knowledge all the time they work on cool stuff some of that knowledge gets passed on to other people and then we learn from each other I think all of us have had that experience some of that becomes embedded in technical processes that we work on and that we contribute to and unfortunately some of that knowledge just gets lost when people leave KDE and that's the thing that we really want to try to avoid and that's the thrust of this goal is how can we minimize that knowledge leakage when people inevitably leave KDE either temporarily because they've moved on to a new phase of their life or permanently for whatever reason which is fine because people come and go but we want to make sure that their knowledge stays within KDE there are many different types of knowledge that gets lost so let's go over that a little bit the first type of leaky knowledge is processes that are done by hand and generally not documented these are things we really want to avoid the next is when people have personal tools that they write for themselves to take care of certain things but then they don't share them publicly when those people go away the personal tools are essentially lost as well next we have public tools which is better public tools are better than private tools public tools have to be documented or else nobody knows how to use them when people go away and then they get rewritten because it's easier to rewrite than to understand and also these public tools sometimes are not run automatically for automatic periodic processes and that's important too to make sure that people retain knowledge of how to use them finally we have, not finally second to finally we have knowledge that is gained alone we learn something but we don't talk to other people about it talking to other people is really important and documentation also has to be kept up to date when it's not kept up to date it's not useful all of this leads to the very familiar feeling of if I stop doing this it won't get done and then you feel like you have to keep doing it and if you don't everything you're working on will end up as an agent ruin like this so that's not a good thing we want to avoid that feeling the basic problem here is that working alone sucks because you end up doing the same work that other people have done before you end up fixing the bugs that other people have fixed in the past you end up getting your merge request nitpicked to death with style comments because people have different opinions on what should or shouldn't be there you end up talking to users about the exact same problems that you fixed over and over and over and over again you end up triaging the same bugs over and over again and eventually when you decide to go on vacation nobody takes over what you were working on and so it eventually gets dropped on the floor these are things that are very unpleasant they tend to lead to people burning out leaving KDE not having an enjoyable time and we want for those things not to happen you don't turn into this guy and destroy your computer because then you really can't work on KDE stuff so the solution is to externalize your knowledge to get it out of your own head it's really important for the thrust of this goal that we be scripting our tasks and that we have those scripts especially if they're for periodic tasks that they get run automatically rather than manually they need to be documented on them too so that if one person is gone then another person can take over without missing a beat we want to make sure that if people are doing similar tasks that we consolidate the tooling that they're using so that each person isn't having say personal scripts that they're running that only works for them and then it only works for their process and another person does a different thing not great we need to collaborate on that we need to make sure that we're keeping up to date on test cases because we want to make sure that our code is well commented we want the comments to be good we want the comments to explain the why not the what the what is usually pretty obvious the why often is not obvious get history I will mention real fast is not a substitute for code comments because you don't see the get history at the moment when you are reading the code you don't see the get history you don't see the get history when you are reading the code depends on your client right depends on your tools so if you're using Kate which all of you should then Kate has an amazing plugin that can show you the very last comment the very last commit that touched a particular line but all of that is a more indirect process than just seeing a comment right there in the code that explains what's going on it can even reference the get history but it is not a substitute because otherwise some well-meaning do-gooder who does not have an editor set up the way yours is will look at this code and they'll say why did somebody write it this way I'll just rewrite it and then a whole rabbit hole gets gone down and it wastes everybody's time we should also be making sure that stylistic stuff is done with auto tests and with CI so that we're not endlessly arguing over whether there should be a lot of code and we should also be making sure that our documentation remains up to date because we're actually using it that's the best way to make sure it happens if we're not reading our documentation we won't notice problems and we won't be able to use it and we'll be able to use it and we'll be able to use it and we'll be able to use it and we'll be able to use it and we won't notice problems and we won't see that it needs to be fixed so when it comes to what's happened over the last year a lot of really cool things have gotten done we've had 12 months that's pretty good I want to go over real fast some of the things that we've managed to accomplish we've added tons more auto tests everywhere personally I'm involved in the plasma project I've seen a lot there there are a number of apps where people have added auto tests this is a really useful thing we've gotten a whole new testing framework using a system called Selenium that allows us to do user interface testing Selenium is really cool because it also goes through the accessibility API so in order to make it work in the first place you have to have adequate accessibility support in your software so this gets to two goals at once because at the same time that you improve accessibility you make your software more testable you're making sure that the accessibility code is being exercised and that it doesn't fit right over time because if it does, you'll notice it and that's really great we have for the KDESRC build script that many of us use for compiling software we now have a dependency regeneration tool that automatically makes sure that the dependencies for HKE repo are up to date, that's really great we have tooling for updating apps on the Microsoft Store which has been written last year, that's some really amazing stuff we have an increasingly large set of changes to make tests mandatory to pass on your software so that you can't press the merge button if the tests are failing, this is excellent we're not 100% there yet but anything is better than the 0% we had a couple of years ago we have a bugzilla bot now and the bugzilla bot takes care of various bug triage tasks, simple things at the moment, saying things like a software that's too old report it to your distro things like that we have updated a ton of updated documentation over time to make it useful so that people can actually start using it we also have continuous integration jobs to build flat pack bundles for many apps which makes them easier to test and also allows us to see when that process breaks, so now it doesn't break as often which is great we have CI jobs to enforce code formatting in C++ in some projects this is something that we have in some repos and not all repos, but it's really cool stuff and it has saved us from a ton of arguing over code style and merge requests which saves everybody's time for more useful things we also have a CI job to validate JSON files now that everything has been ported to JSON which is used to auto generate desktop files so now you don't have the experience of accidentally breaking your JSON file right after you hit the merge button which is no fun and waste everybody's time so you can see a theme here which is let's not waste everybody's time finally we also have a hook script to prevent you from changing translated text in Git now that translations live in Git repos we were seeing a bunch of people saying ooh this is great, this means I can now do translation work in Git, can't do it so now we have a thing that tells you so that we don't have people explaining that over and over again which was no fun there are many ways if any of this sounds interesting that you folks can help to do this the biggest ones is to write more selenium UI tests for apps that have the framework set up this directly benefits multiple goals as I mentioned earlier it also helps to test the accessibility stuff and if your app does not currently have selenium set up set it up, it's really cool there is a wiki page that explains how to do that some of this is linked to in the goals wiki page which I'll get to at the very end another thing you can do is a very in some cases it's sort of a low-hanging fruit is to make tests mandatory to pass before merging if your project is in the fortunate state that all of its auto tests already pass fantastic immediately go turn on the thing that says that they have to keep passing so then they won't just start failing at some point in the future because that will happen we also want to make sure that we are adopting much more widely the code formatting stuff we don't have as much arguing and merge requests about that, that's another small thing that is relatively easy to do from a technical standpoint from a sociological standpoint it's harder but you can say, Nate told you to just do it and then people yell at me and not you and that'll be easier we have this KDESRC depregeneration script that I mentioned earlier that's something that could be automated so that it runs periodically and then Nicholas over there doesn't need to manually run it once a week which I assume is a waste of his time we also have the bugzilla bot the bugzilla bot is written in Ruby it's rather approachable we can make this smarter so that it's doing more of our work for us and we have less bug triage to do but basically be lazier I want all of you to go out and be much lazier so you have less busy work to do because in the process of being lazier you're also helping to take the amazing knowledge that's in all of your heads and put it into KDE where it can benefit from everybody because all of that won't be lost there are also some even bigger ideas that I've got for this goal that have been worked on a little bit here and there but really need the helping hand of technical experts to make this stuff possible basically everybody I look at in this room is much smarter than me so I'm looking at a whole room full of technical experts I think that any of you folks if you want to work on any of these things this would be a fantastic way to help the goal we've got tasks like consolidating release tooling I think it's not lost on everybody that we have many different release vehicles we have gear, we have frameworks, we have plasma we have individual things with extra gear if there would be a way for us to consolidate our release tooling so that it's something that can be run automatically and it's something that can work for all different release vehicles that would be fantastic because it would make it much easier for people to be release managers and not so much of the work would have to be born on one particular person so that that person feels stressed out if they happen to be on vacation when release day arrives etc there's also this other moonshot idea of using AI to triage bug reports people keep asking can you integrate chatGPT and KDE can you integrate chatGPT and KDE and this is how we do it in my opinion we have a robot triage bug reports because this is something that robots can potentially be good at if they like to do so let's do that if possible this is something the next thing is something that also helps for onboarding if we could have KDE SRC build automatically install third-party projects needed to build KDE stuff instead of making people go and do that themselves that would be a huge help that would cut down on an enormous amount of common chatter that people end up having to handle in the same vein so if we could integrate the AI to triage bug reports we could have a chatbot answer common help questions things like NVIDIA drivers and why does this update not work in Discover because my distros update policy is completely broken things like that I'm sure all of us are very tired of answering these types of questions I know I am and if there's any way we can have a system do that that would be much better there are also ideas for how we can make our icon design pipeline much easier it relies on information that is stuck in the heads of several people some of whom I see in this room and I think if there's a way that we could make this a more programmatic process by say having icons get generated by combining symbols together in a code pipeline rather than making everything manually get done in Inkscape that would be fantastic we could automatically generate AppStream release notes from the commit message tags and from GitLab tags we have all the plumbing needed to make this work we even have support in AppStream itself which has recently gained support for fetching remote release notes which is the big blocker last time it's just a matter of wiring it up then we don't have to spend so much time manually writing release notes for every single release this could be a big benefit I think and then there's also that this week in KDE blog that some guy named Nate writes which for some strange reason is not on KDE infrastructure yet so maybe he could finally get off his butt and do something like that I think that would be good for this goal as well if any of this sounds interesting you can get involved in a couple ways I'm the goal champion you can always contact me I'm Nate at KDE.org I'm around all the time I think you probably know how to contact me otherwise there is this KDE.org slash Goals link where you can find information about all the goals including the automation goal we also have a team on Sprint that you can join there's not much activity there in that particular space right now so you can help change that we have a buff session at noon on Tuesday that you can go to if this sounds like an interesting topic and we also have a Sprint planned for some time next year so keep your eyes and ears peeled for that and with that I would like to say thank you all for listening and we can move on to the next one I'm Nate and we move on to accessibility with Carl tell us about accessibility Carl Hello everyone I will talk about the second goals about accessibility as we are called KDE for all because we are in community we want to have software to work for everyone even people with disabilities who need to use the screen reader or who can't use the mouse as this code from Tim Bernali who says the power of the web is the universality and accessibility is an essential aspect and I think that also applies for KDE like why is that important it's good for us to reach more people we do that as well by putting our software to windows or to make or to hungry we don't want to only target Linux users but we also should not only target people who are experts with computers and we can't see the software and it also benefits everyone like even for normal users being able to use the software with the keyboards like for private users it's quite important like they can be faster to use the software like for example another aspect is changing the fonts like to increase the size of the fonts as well like useful for everyone and not only people with a reduced visions I mean like accessibility as well including the usability generally like of the software in general and another aspect is that accessibility is a requirement for public sector organizations and if you want to be able to use the software we should try to ensure what case software follows the requirements follows the accessibility requirements so what did we do like last year since last year I mean like we started testing the software with a screen reader or with a keyboard only to see what can be used or what can be like just like by listening to the orca see what or we can use the software currently and that allowed to like find a lot of cases where it was not that great like often there was tabbing back loops where you just type and you switch the cycle between elements but you don't go like over on the apps which is an issue because then the screen reader user or just the keyboard user won't be able to navigate the entire applications just with the tabs or the keyboard navigations and we started writing automated tests like I already said which is like really cool framework to work test and also like ensure what your software is accessible I mean it doesn't ensure it like you need to work on testing with like a screen reader but at least it helps a lot and yeah we had like multiple season of Calibre projects on that topic as I meant to rate Ritchie for Tocodon and Joseph did like work on Gekampi with Senon we also had like some blind users coming to the KDSS beauty channel and testing the software for us which was quite great like to have like because like when you can see what the software is it's a bit harder to imagine what the difficulties are but when someone comes and tell you yeah that buttons here I don't know what to do and then oh actually there's a Kigami server handle to yeah that's how you detect malfunctions yeah I really like after our testing we started like improving the software there was like many patches for plasma credits and as well as the applications like a good example is Clopatra Ingo as a talk I think later today in the room we hopefully like will give you a bit of technical details and we met Clopatra good for accessibility we use the Kali frameworks because like if you ensure that the Kali frameworks are accessible it's easier to build applications that are also accessible if you use common shape components we also need some improvement upstream and cute we send the multiple patches to cute to improve the accessibility for for the buttons for the press action something or the name was missing by default it was easy to fix like what we get like by testing the software we find easy things to fix and there's like a lot of areas where small improvements already make a lot of difference and we also send a few patches to the screen reader for Linux the GNOME project so it's good to see the software collaboration on stuff like that yeah so what did you learn yeah I mean like having the community vote on the goal doesn't make it magically happens like we still need to have more people working on the accessibility there's also like not that much documentation from the QT side about accessibility and what's something that we should try to improve on the upstream I mean there's like documentation for the QT class but there's not a lot of documentation or to use that, best way to use that or to make sure your application is good with accessibility and there's a lot of definitions and blog posts about the web accessibility but for QT there's not that much yeah so future yeah I mean like we should continue working on accessibility it would be great like if you're more people like we wanted to organize a sprint next year with the other goals and like for me personally like what I want to do more is what more blog posts like more community to make more people aware of the community how to improve accessibility like other documentation and stuff like that but it didn't really have a lot of time like it's always like I have many projects aside from accessibility and so it's great like if more people would join and help with that um no ah it's a bit suspicious let me go back how can you add like test applications like install an orca and try to use the application with orca and see how well it works yeah, working documentation is important to like document the best practices for kids for getting software general for the world like if someone could help me like what blog posts and stuff like that protect the current forest and the community would be really helpful and like as a tooling like think Volca work it a few years ago on gamma ray accessibility inspector it would be great to provide this effort to be able to inspect the accessibility state in gamma ray as well as overstate the visual state and everything yeah, like if you want to join there's a caddysvt channel on matics, I also have a label on ESC and we have a buff both on first day at noon and yeah, join us twins yeah, about it thank you Carl brings us to the third and final goal of sustainability with Joseph let's see presentation there you go apologies for breaking the aesthetics I tried to convert the template to la tech but it wasn't successful I'm actually Cornelius Schumacher he's the champion of this goal I'm here pretending to be him so the usual disclaimer applies any errors are my own yeah, I'm going to present about the sustainable software goal which is part of this sort of larger Katie eco initiative which started a couple years ago if you would like the slides are available to download at the sustainable software gold repository on invent I'll come back to this at the end if you want or if you have time now to scan it and I'm going to go over just a couple of the things that have happened since the goal has been adopted and voted for in October last year one of the things is the publication of the Katie eco handbook this was the culmination of the work done in the Blower Angle for Floss project which ended in March but it also coincides with the sustainable software goal and a lot of the topics addressed here are directly relevant for what the goal has so the handbook if you haven't seen it yet is broken up into three parts currently the first part is meant for a general audience about why is this important how does software influence resource and energy consumption the second part is about the Blue Angel eco certification criteria and how they align with free and open source software and the third part is how do you fulfill the criteria with detailed instructions about measuring software following the guidelines in the Blue Angel criteria and then fulfilling the other criteria in it that's the first iteration we want to continue expanding it and I'll talk a little bit about that in just a minute the as many of you I'm sure no ocular was eco certified last year with the Blue Angel currently it's the only software that's certified as resource and energy efficient that eco certification has opened up many new channels to KDE to present the work that we are doing one of them for example is in December at the open UK awards in the House of Lords in London this was an event organized by the open UK advocacy group which advocates for open tech the host of the event was Francis Maud who's a member of the House of Lords and he's the minister who a decade ago created the gov.uk website which provides information about open data open formats and policies regarding that a co-host was KDE's own Jonathan Riddell and he was there to also present what KDE is doing in the KDE eco project so yeah really big channels have opened up to us in this regard another one was Cornelius who presented at the Green Party event on green digitization which is a project by design this was an event that featured many prominent people like Kari Doctorow gave a speech the Germany's vice chancellor Robert Habek and Cornelius participated as an expert given the blue angel certification of Ocular in the right to repair workshop that was organized and this event and this post was a very popular post that featured in the Hacker news and there's a huge spike in the views in the KDE eco project website after this so it garnered a lot of attention and another project or several projects not just from KDE eco but from the season of KDE in general was reported on in Heissa DE which was a big publication for tech news in Germany it featured all of the season of KDE projects but the eco ones were particularly prominent this year we had three projects working on sustainability issues one was this tool that was designed by Emmanuel Charu I'm not sure if I'm pronouncing that correctly called KDE eco test and this tool is designed to make usage scenario scripting easy and robust so the existing tools that there are have various issues and this is trying to make it so that the process is simple like some of the tools but more robust because it's not based on pixel locations for the emulation but rather working on command line triggering of actions when you're trying to emulate user behavior this tool is quite limited and it's now been expanded to have many more features from Mohammed Ibrahim we had another project which was looking at the documentation for ocular trying to extend it to Kate in particular and that was from Rudox Carp and then as has been mentioned now by both the other goals the selenium testing so just a small correction I wasn't actually working on the G-Compre testing Ibrahim who did excellent work using selenium to emulate user behavior for G-Compre and as Emmanuel wrote in a blog post this is a project that actually hits all three goals Nate has already talked about automation Carl has already talked about accessibility it's also used for usage scenario scripting to emulate user behavior so that we can reproduceable energy consumption results for software right now there's a project going on in Google Summer of Code which is trying to make the lab that we set up last year in KDAB Berlin to measure the energy consumption of software accessible remotely so all this outreach is great but the actual reason we're doing this is because we want to measure energy consumption of software and drive it down when we can and this remotely accessible lab will make that much more easy to do so the idea here in the lab is that the lab is set up with dedicated hardware for measuring the energy consumption of software a power meter, an external power meter that's just measuring all of the energy draw when using the computer and then it's then aggregated onto another computer to collect the results and then you can analyze them and the idea is to set up a interface through the GitLab CI so that you can upload your code and then tell it you want to do this test it will then send the commands to the lab in KDAB Berlin run your scripts give you the results in a usable format and then give it back to you so that you can see the energy consumption of your software and if you're interested in eco-certifying it, this would also be one of the criteria for eco-certification so we're trying to make this automated and easy and accessible to everyone this is just a bit more details about it so the software will be installed as a flat pack bundle and then that's then run on the software the hardware at the lab and then this is then analyzed just another thing that we're working on is an awesome list for sustainable software this is again the sustainable software repository there's a great list of resources related to general green coding best practices as well as how do you measure software, what tools exist etc so check that out if you have some resources that you want to contribute to it please do so there's several talks that are taking place today tomorrow and next week related to the sustainable software goal so one is right after this Fulker is going to present about measuring the energy consumption of software tomorrow Harold is going to present Selenium GUI testing which is relevant for all of the goals and Monday we're going to have a buff for measuring software so come by if you're interested in the process of how to measure your software there are other many related talks this is just a couple that stood out for me so on Saturday there's the flat pack and KDE from Albert as you saw flat pack is part of the remote eco lab process documentation that's also come up several times and this is maybe not obvious how it relates to sustainability maybe it is I'm not sure if we want to achieve a sustainable circular economy for software and also hardware we need documentation for repair and reuse of software right this is the sustainable angle on that we can't use the software long term if we don't have the documentation for how to use it and repair it and etc another topic that I just thought might be interesting to think about in terms of sustainability the KDE embedded embedded systems are not the systems that were targeted by the blue angel certification the blue angel is trying to address the issue but the hardware is getting more and more powerful and software is becoming less and less efficient because of it it lets us get lazy embedded systems are the exact opposite you have a limited amount of computing power and you have to optimize to fit that and it has I'm sure many overlapping topics of the sustainability efficiency side in terms of optimization so I just thought I'd point that out and then there's another talk about technology information from solar panels directly into KDE plasma which is all happening in the next two days so one of the things that we have on our to-do list so as part of the Selenium season of KDE project Nitin wrote a guide which you want to add to the KDE go handbook as the next chapter we need people to test the guide to see what needs to be removed or what's accurate or inaccurate so if you have a chance and you're interested in checking out Selenium GUI testing maybe check out the guide and see how it works for you and give us some feedback on it another idea we've had for a while now is this idea of a KDEco badge so eco-certification is nice it's third party, independent of KDE but we can also do something that's internal and define certain criteria which is important for KDE software and if you fulfill these criteria you get a little badge that says you're fulfilling the sustainable software goals of KDE if you're interested in working on this please be in touch we've already started taking some steps towards an eco tab that would be included in KDE software so you have the about contributors tabs and then we'd add an eco tab which would then highlight aspects that are which are sustainable from things like eco-certification but also links to documentation source code if there are measurement data that aren't part of a certification process you can still link to it and that's relevant for sustainability issues if you're interested in working on that please be in touch if you have other ideas you're more than welcome to join we have monthly meetups every month and there is a matrix room and several other things which I forgot to put in the slides and you can find that information at eco.KDE.org it's quite easy to find and then regarding the sort of general unifying aspect of having goals one of the ideas that came up when discussing the presentations here was having maybe crossover presentations in the different groups that are working on automation to come into our meetup and maybe discuss ways that it overlaps with what we're doing in the sustainability so if you're interested in that or if the champions are interested in that maybe that's something we can talk about there's already mentioned a joint sprint next year any other ideas we can discuss in the panel and I believe that's it thank you thank you very much and now we have quite some time for questions about the goals or the goal process as a whole and I believe aid will be the mic runner we will run around questions I don't know if this is too detailed or not able to be answered but how hard was to get ocular to get the certification did something need to be changed many changes how was that experience to get to that level so the most labor intensive aspect of it is the usage scenario scripting and the measurement process which if you're going to start adopting Selenium you're already taking care of a big chunk of that work and as well as accessibility and automation so we can incorporate maybe some of this that work into the general development process and then the measurement is just a matter of having the access to a suitable lab for fulfillment everything else is just documentation free and open source software is recognized as being a more sustainable approach to digitization given various aspects of the way it allows users to have more autonomy about how the software is used which can influence energy consumption removing vendor dependencies so that you can continue to support hardware over a longer time etc etc these are all things I think we take for granted and this is obvious but this is putting it in terms of a sustainability angle and that part of the criteria are actually just documentation and understanding how you fulfill these criteria so thank you this is a hybrid conference we have questions from online and Nelfitos is going to be the voice of online here you go actually there was Alan asking a question about the lab and how do we make sure to be able to compare over time the power consumption of our software if the material use their changes and I see Cornelius stepped up and he's understanding it so I don't know if Joseph you want to add anything to that so the question was how do we make the results usable over time so that we can compare as the hardware changes what do you do to give it up to date to give the measurements up to date so right now in the lab we have a few different computers one of which is the recommended hardware for the blue angel certification and we have some others one of the goals, the moonshot goals is to have several options of hardware where you can say I want to test it on this hardware which might be a little bit older or I want to test it on more recent hardware but I think the answer to that is documentation of which hardware was used so that you have a maximally similar environment if you were to retest and want to compare the results directly with the test that you did previously great thinking Joseph and then there's another one for Nate it says wasn't there a prior effort at an icon design pipeline called Icona what happened to that that's a good question Icona was a standalone app that would have definitely helped for the icon design pipeline proposal this was an app that would be used to preview an icon that had already been made in various environments against various backgrounds the idea that I was bringing up on that slide was more to aid the process of creating the icons in the first place which right now is quite an error prone process and requires understanding of the details of how XML inside SVG files works so I think there's definitely some work that can be done at the end to verify the end result but I also think it's important that we make the process of getting there so that there is an end result a little bit easier hi I have a question about the KDEco for the measurement process of the application I can imagine that you somehow need to make sure that no other software installed on the test device interferes with the actual measurement of the application that you're testing how do you approach this so right now it's just very simply turning off anything that could interfere when you're measuring we have discussed ways to have a record a state that the software was in when you start the first measurement and then putting it back to that state for each measurement so that you have a maximally similar environment also as each measurement goes you're going to be changing the system a little bit right now the way we're dealing with that is just removing the configuration files that might have been changed in any files that may have been produced during the measurement so that it gets back to a maximally similar state but that is an area that we certainly could look at later once we get everything set up and the first step is achieved and then we can start thinking about how we can improve that process so I have one more question regarding the measurement lab like do you have plan to add to support for mobile devices because like plasmobile is the one of the things we support and like that's where actually the energy efficiency is more useful because like you don't want your mobile devices battery to drain completely so do you have plan to support mobile devices short answer no I mean so right now it's not what we're working on right now but the blue angel certification is extending their criteria to include mobile apps and client server systems and they might have some some tooling there that could be useful for measuring mobile apps at the moment I don't know how we would do that in our lab with the setup that we have so okay thank you I have one question for Carl you mentioned that accessibility is also very important if you want public institutions to select your software do they have some requirements like you have to have a certificate maybe or do they do their own testing or is it just we tell them we made sure our software is accessible I think it depends I mean like for the web there is like the standard VCRG standard there is like multiple levels and usually institutions want to level RR at least and then there is some companies who will do certification for that I was involved in the past with Nest cloud I mean it's usually a certification like you need to I have a question to Carl how's the the status of the accessibility in the way landing by a month I'm using the Wayland full time we could use Okia it's working but I think we still have a few stuff that would be better to improve but I'm not familiar with that area we've sort of got an answer here so there are definitely some things that don't quite work properly accessibility wise in a Wayland session a lot of the keyboard related accessibility features like sticky keys, slow keys that kind of stuff that used to be implemented by the X server but on Wayland that's not a thing anymore so we get to implement that ourselves in Quinn and a lot of that is missing I've recently worked on some of that but it will take a few more patches to get it on parity with X there I like this setup where we get answers from the audience so maybe the panel has a question for do any of you have ideas how to measure mobile systems in a lab we got an answer yeah we build a custom so we hacked an Android device so that we removed the battery we basically build a fake battery which is connected to the power and that's how we actually using the power consumption so like it's on battery because of course most of the Android device cheat when they're on battery they remove some power features or add them we had the issue for example for VLC where we were higher priority when we were plugged on an actual network so that's how we did it and so these devices then we have a RS232 to just read the timings it's a mess let's talk anyway at some point to add to that answer ARM incorporated has these giant labs of hooked up devices with relays to reset them there's hardware setups for that so any questions or answers so I'm not directly involved but collaborer runs a lava lab to do a bunch of the tests for Chromebooks and Android so they may have some there's definitely some ways to use lava to do that kind of thing let's talk so next up we want so again from the internet regarding any cost certification there's a question is there an ongoing measurement that is taken each time the software is released to ensure there are no minimal regressions in power usage over time let me just make sure I understood so is there an ongoing measurement process so that we can then see if it's improving or getting the way I understood it after you get the certificate is there something ongoing for the certification you need to measure it regularly the exact details of that are a bit in a gray area but yes you're supposed to measure it regularly and right now our approach is that we want to measure major releases but first we want to get the lab set up for easy accessibility so once we have that then the idea would be then for major releases to have regular measurements and that's required for the certification as well thanks and maybe sorry just one more thing to add to that the eco certification requires that it doesn't increase the energy consumption doesn't increase by over 10% during the time of certification from when it was certified so there are requirements on staying within a limit so that means we could lose the certification at some point right okay so we need to be careful yes so we got 10% worseness to play with make the world a better place with your question it's just a small follow up question like do we need to redo the entire certification process in case we lose it or do we just go under the threshold of 10% certification again good question I don't know hopefully we don't find out but you're going to motivate me to find out so I'll see I can find that information so my question would be do you do tests on a certain device whether using plasma and KD software extends the life cycle of for example for an organization is are there some tests to show how much e-waste can you not have if you use plasma then if you use Apple devices or Windows devices no the requirements of the certification you have to state the minimum system requirements and demonstrate that it can run on hardware which I think is way too low one of the things that I have in mind that I would like to work on at some point is a campaign on e-waste reduction with free software and I think gathering data about hardware that is no longer supported by the two major vendors and can still run free software and getting some documentation of that would give us at least some idea of which devices if not the numbers of how many which devices would otherwise end up in the landfill but can remain in use because of free software so if I could add something to that answer something a little bit more on the concrete side in the town where my parents live my mother is involved in a community organization that is actually doing exactly that right now they currently have 80 desktop computers that are over 15 years old and are based recently and are instead being loaded with Kubuntu and used to teach computer classes and given away to low-income students so there's a specific example of how using eco-friendly software can directly prevent e-waste mine was instead to jump again on the accessibility topic I just remembered another partial answer to how is the accessibility status on Wayland another thing specifically to Orca the actual screen reader part just works for the most part one thing of Orca that doesn't work at the moment I think unless it was fixed recently but I don't think is that it has a feature that can do something like putting a rectangle over the button that is now reading that at the moment cannot work on Wayland for the absolute positioning stuff and there isn't a clear solution yet I guess the final solution will involve somehow as usual a new protocol as every Wayland problem but that will need to be thinking about having the same issue with the ASSER which is like the software where you can analyze the state of the accessibility of the e-program and you can actually choose a rectangle and that doesn't work on Wayland thank you we've got time for one more question you've already asked one, you're new I think we even can do two we can do two so this one's kind of for all of them, although it sounds like the eco-guys are already doing it as an app developer is there plans to create check lists of stuff that I can be doing to help to meet the accessibility goal to meet the automation goal sounds like the eco-guys are doing it with the handbook already that's also the idea of the badge which is something we really should consider setting up a sort of if you fulfill these things you reach a recognized within the community a certain sustainability goal yeah but not yet, that's definitely something we should do I think it's a good idea too all of the goals can probably benefit from this there's a lot of overlap if you do the Selenium GUI testing you're basically doing all three at once from the automation perspective there's the obvious stuff like have a continuous integration system do testing, make sure that your tests are passing things like that for the accessibility it's the same thing maybe like a check list yeah and the very last question thank you I heard you mentioned before that you have an energy budget of 10% you could lose the certification if you go over it you're not sure is it possible that these measurements and this process to certify this it's scalable to be automated so that when you merge or when you do a new release it's like part of GitLab and how scalable it is for it to be part of the release process both of Ocular and other plasma applications so how can we integrate into the development process so that's the idea of this CI runner that we can have then if we want to measure the amount of time you can then simply make your merge and then test in the lab that's sort of the goal with that do you think that it's something that is going to I'm going to merge something and is it going to I'm going to with like 5 hours to get the answer like how's the if yes but we can probably talk about that but we can certainly design it to fit our needs if you want to do eco-certification you need a certain number of measurement runs to have a statistically relevant measurement but if it's just for a quick thumbs up, thumbs down kind of measurement I'm sure there are ways to shorten that process so we can talk about how to design it so that it fits our needs then thank you very much if you have more questions during lunch can I get a radio for you? thank you so much but it's not lunchtime yet we're splitting into two rooms Volker I think is in here Volker is here but Volker is also here in the next slot there's Ingo I think on the other side and I would like to remind everyone that if you are interested Qt is hiring you can talk to them at their stand outside everyone who successfully arrived at the conference did so thanks to KITinerary which is not the topic of this talk so we're going to talk about energy consumption instead Volker so yes following a bit on the previous session how can we actually measure the energy consumption of the stuff we built to get started why do we care about this yes there are multiple reasons there is for example the battery use and battery power devices the mobile case that we discussed earlier so if you use less energy there the battery lasts longer clear tangible benefit for the user another thing is performance all the electrical energy we put into a device comes out as heat again and quickly enough the device water is down so if you put less energy in that happens less often we get more performance out and then of course the climate impact of energy use on that subject I can recommend you to watch some of Joseph talks if you haven't done so already here are some actual numbers in there I think the IT impact in the same order of magnitude as transportation and aviation combined so that is a lot and worse it's rapidly growing there is definitely something we need to do about that how does software impact the actual energy use so how can we change this the obvious thing every instruction the software sends to hardware requires energy to be executed on any kind of hardware but there is also less obvious things beyond that for example power management settings there is hardware that you currently don't use that can be switched off a lot of this is transparent to all level of software that happens somewhere on the driver level but in some cases that also benefits massively from more context say for example you can switch off the display backlight much more aggressively on the lock screen while compared to when you are watching a video then you probably shouldn't do it at all so we can also provide useful impact on that level somewhat related to that the idle behavior of software actually do when it's supposed to do nothing more often than not it's actually not doing nothing but it's continuously looking if there is more stuff to do and that means the hardware actually wakes up checks if there is stuff to do and that means we don't get to the highest power save states and again waste energy there realistically we are going to talk about very small quantities here so is this even worse the effort but even small quantities matter here if you reduce the idle consumption by half a watt on a modern laptop that can translate to 10% more battery which might be another extra so that matters and there is more effects that support this the some of the effects in there aren't linear especially towards the extreme in the high performance part as well as in the idle area even smaller changes can have a disproportionate impact and then there is the scaling effect that's again something you might know from Joseph's talks here some actual numbers in there because this is not a one-time local optimization it multiplies over time and multiplies by number of users and I'm not sure if I remember the numbers correctly but I think within reasonable like our level of distribution and scale I think you got up to the energy use of a small city within a year that is actually a sizable quantity and that is our level of scale if we think about browser engines that is a completely different level the flip side of that however is if we make mistakes they are also going to be quite costly this is important this matters we can make a difference how are we going to or how are we actually going to optimize our software and like with any other optimization as well the first step is we actually need to understand what this software does because what this software is supposed to be doing, what we think it does and what it actually does more often than not are three different things so we actually need to have a look on what's going on on Linux our go-to tool for that is the perf profiler and so we run perf record with the application that we want to measure perform some usual operations in that we get the profile file out, open that in hotspot and look at the details we're going to see a few screenshots in a minute that works for looking at the specific application for the idle behavior we want to see the full system view the specialized tool something like power talk that gives us the overview for that and this is the result we get in this case so this is a flame graph view on the horizontal axis we have cost or in this case like time spent on CPU and vertically we have the call graph so you can dive into various parts of the application and see what's going on there now seeing stuff in there doesn't automatically imply that it's bad this is something that you look for things that shouldn't be there things that are surprisingly more expensive than what you would expect that is the interesting things to look at another useful view in there is the timeline view so each row in there is one one thread horizontally is the time every orange marker in there is activity on that thread over time and as we would expect during startup you see quite some activity and then towards the end the application sits idle and we would expect to not see any activity but there's at least two threads where there's still something going on and again that would be something to look at because we expect the application to not do anything at that point in time so what's going on there in hotspot you can basically select that area of interest and filter on that and then you get the flame graph for just that particular area and then again maybe it turns out that is necessary or it turns out that this is something that shouldn't be there this is the output of power top that is just a table the terminal list of processes sorted by the amount of wakeups paid for per second same thing here this will never be empty and zero there's always activity going on it's about finding that activity that is avoidable unnecessarily or could be done cheaper so you will see Quinn updating the screen because the output you are looking at so that require the screen output one example that we have recently in there was a cave background window showing up with 30 wakeups per second that turned out to be an animation timer that wasn't switched off while being in the background so that is the start to look for so once we have identified things that we can optimize how are we going to do that if you are lucky you find something where you can just do less that is always strictly better but those cases tend to be rare usually it's more about making a different type of trade-off let's take an example you have some expensive presentation you do this twice and only use the result of the second run you just don't do the first one easy so let's assume you use the result in both times then one possible optimization would be you just store the result somewhere so if the result is an 8-byte number that is most likely always going to be a good trade-off if storing the result means 100 megabyte of I.O then not so sure anymore so we need a way to to qualify those trade-offs so is that really better and this is somewhat complicated because it can also quite easily depend on the specific hardware so if you optimize for making the software faster we usually do this by measuring the time it takes until it's done so if we optimize for energy that's the point where we then actually need to really measure the energy and that is really the only viable approach there a lot of this stuff as I said earlier doesn't really behave linearly so don't really trust your intuition measure this and then decide which one is better so how do we actually measure this then I'll focus here on stuff that you can practically do at home so anything that requires special equipment or equipment with price on request price tags that is out of scope so if you are coming from an electrical engineering background some of this might look weird but that's the stuff we found for home use so in terms of where can we actually measure the first option is basically the AC side so the power plug that has the advantage that you really capture everything that goes in you don't miss anything it is a bit of a problem for battery powered devices so when we talk about measuring a mobile because you might also see the battery charging or the battery might hide some of the use by buffering that away so yeah ideally you just manage to remove the battery entirely and then there is the small problem with safety AC power is deadly so if we can avoid that let's look for other options the secondary side so basically the other end of your power supply with the rise of USB-C unfortunately that is usually not practical anymore because you need specialized equipment to measure on USB-C and on your workstation it's even worse you know this giant power cable that comes out of the power supply in theory possible but not practical or at least not practical for what we are looking at here which leaves then the third option and that is built-in sensors those are particularly widespread on I think standard Intel hardware and some of the AMD hardware as well so pretty much anything sold in the last decade will have some built-in sensors on battery management systems you usually also have them but they might be tricky to get access to if you have them they might actually be a very viable option to measure on mobile because the big downside of those sensors is they only capture a partial view so if you have a sensor only measuring the CPU consumption anything else happening on the system will be missed for the battery management sensors that is less of a problem because that really captures most of what's going on those sensors also tend to be extremely precise to the point of being like a viable side-channel attack factor and on the other hand you're kind of measuring your measurement with this right so if you have like a compute heavy workload the measurement might ground the cost but if you're measuring an idle scenario the measurement itself might be the most costly thing running at that point in time so that is something to keep in mind so I think that part we have to skip because that slot turned out to be only 30 minutes instead of 40 minutes so let's get to some practical devices you can use for this we start with stuff I wouldn't recommend you get but stuff you might find around and that is still better than nothing maybe so the thing on the left is usually something you find in a hardware store sold for as an energy monitor or something like that for relatively cheap those devices aren't machine compatible which means they give you an update rate of more towards a minute and a second which is way way way too long but if you manage to stretch your measurement sufficiently long that might still be good enough to verify the power management setting actually have an effect the other type of device is like server management power strips remote switchable sockets those sometimes also have power management sensors and they are internet connected so machine readable update once a second so that's already much better just the price point is usually unreasonable for what you can get out of those devices if you have that it gets a drop down more attractive is something like this this is like a very cheap wifi power plug sold in a smart home context those also have power sensor built in and there is a free software firmware called TASMOTA that works on those devices so you can get rid of all the cloud nonsense and get high resolution access to the sensors it's however not really built for our purpose but we managed to get like five samples a second all of this with some MQTT polling hacks if there was somebody interested in like C microcontroller programming I'm pretty sure the hardware is capable of much more and we could get much better results if we wouldn't have to abuse some MQTT protocol stuff for this but got a steady stream with proper time stamps of the sensor values cheap and hackable very compact that is probably as good as it gets slightly more expensive but actually built for the purpose we actually want to do here so really just for measurement we have this the RQM PowerSpy 2 that's something the Mozilla people pointed us to one downside of that thing is it comes with an ancient window software and we have only reverse engineered half of the protocol so far so for life measurements we can use it but we don't get to all of the other features of that yet significantly more expensive than the other one also interesting we got to work with during one of the sprints is a development board for the actual sensor chips the sensor chips itself are super cheap a few dollars a single piece price so if you're into electrical engineering and building boards around that this is great and this had like a 1 kHz sampling rate over USB so much much more towards what we actually need and want however this is basically an open PCB running AC powered with so okish in a lab if you know what you're doing certainly not something you want at home on your desk there's more kids around so this is something we could get out of I think this was done with one of those so it's basically a plot over time for the energy use you can see that this is rather noisy that's not the fault of the sensor the reason for that is in the slides I had to skip it's massive under sampling on the high frequency of a switch mode power supply that's why I'm so obsessed with higher sampling rates but you still see some some some changes in that signal right so in the middle section between 100 and 150 you see that the signal overall is slightly elevated there is of course the clear peak in the middle and what was done there is that in that middle part the mouse cursor was moved and during that peak it hovered over the taskbar and showed a twitter that is not meant to say that mouse moving is bad but it shows how sensitive those sensors are we really see operations on that level in there which is extremely useful if we want to verify if our changes had any any effect then for the built-in sensors as I mentioned the most common one is I think the one from Intel Rapper running average power or something the way to access them on Linux is also via Perth with PerthList you can check which one of those are available on your system if you have an Intel laptop you most likely will find a few of those there is usually cores which is the compute part of the CPU package which is the whole CPU carrier with L3 caches and the IO controllers and whatever else is on there sometimes you'll also find memory and GPU with separate sensors those can be read out with Perth.org with the Pinpoint tool I like the letter because it gives a continuous dump on the measurements which you then can feed into the laptop or anything else to visualize this both tools however make it kind of look like you're measuring the energy consumption of a specific AdBo workload that is not exactly what's happening there but you can always measure the entire energy use of the system so you can put in sleep 1000 as the workload and do something else and you will measure that something else which is a creative just need to know about that and this is barely visible and you can see that the CPU load is piped into the laptop on the lower half on the upper half is the CPU load you can see that this is somewhat correlating so if the CPU load goes up the energy consumption goes up as we would expect but you can also see the peak in the middle where the energy consumption some peaks where the like the energy used by the memory goes up disproportionately and that is of course then the interesting bits because there's something that behaves contrary to expectations or intuition so again this is mainly meant to show you the level of detail you can get all of this with the sensors and right then if you have access to neither of those we can also measure in the cloud the sum of code project from Kevin Jott that Joseph had spoken about in more detail earlier so the basic idea is the ECI builds you the flat pack of your software test driver a Selenium test driver for this we run this via GitLab on the new angel certification setup it's run there several times to counter the noise and other stuff interfering and then it applies some statistical magic to get a bit of this rate and then it produces a report there's the results and plots and whatnot and then you can see this takes a long to run it after every commit but it's something you would run after major changes or before release to verify that you don't have the questions right yeah so how do we put all of this together right so the the first step is just doing general profiling and optimization you'd be surprised by what you find in there it helps with making the software faster for the user and it helps usually at the same time also with reducing the energy use if you are looking specifically for the energy use the biggest impact of course is on long running processes and there's two things in there that are interesting right so there is continuous or frequent workloads so for example media playback probably has a higher impact than say opening the configuration dialog and keep it just because one usually runs over hours and the other one you do a few times a month and then the idle behavior is the other thing to look at system wide because every single wake up comes so whatever we can get rid of there is overall helping and the other thing you probably saw from all this repurposed random other devices and weird command line hexes the tooling is extremely basic this is nowhere near what we are used to for profiling for other functions there is no you basically end up doing some manual calling on that device and piping that in a CSV file and opening that in as a life source and then trying to put things together there is a huge amount of stuff that could be could be done better and could be just also become more accessible for us as the users of it by not having to figure out each time how you put this again together as Joseph mentioned we have a bot on this on Monday 10 o'clock anything related to the sustainability goal I would say but I have some of the measurement devices with me so we can share one with those or you can try them if you want to that's it we have about 5 minutes for questions so questions answers is this more of a comment than a question it's a question in power top do you happen to know what that tick underscore timer entry that's always at the top actually means I think that's some kernel thing but I don't know more detail about there are things that you take kind of for granted if you're developing like say moving things from CPU to GPU is always a good thing because it's good for better feeling is it still true for power that's good or bad that's a very good question I think it's on the slide but I didn't talk about it solving the same problem with a different kind of hardware that is exactly the point where you need to measure because there is no documented best practice it very much depends on the hardware usually and it's often contrary to the introduction right there is some documented research from the HPC people because for them this works at a completely different scale and I think there GPU usually outperforms CPU but for our use cases I think it's always measured it's simply not known what is better for very specific workloads okay so I have a question do you have any ideas about the real time measurements like for example you have an android you can see the power consumption of different applications and do you know what do they do and how you can use this maybe on desktop that is a good question I don't know exactly how they do that I mean this whole topic of attributing energy processes I know that there is some research we have been at some meetings with people looking into that a lot of that is just proportional use of the CPU and then more or less guessing there is to my knowledge no way of measuring this with any kind of certainty it's just on average probably it correlates with amount of time spent on the CPU and I think this is what android does it's probably close enough just because of the big differences in there and it doesn't really matter if it's a few percent off but proper strict attribution I don't think there is the means for that Hi Valker here two questions from our remote participants one is are cheap wall outlet meters do you have certifications safe to not burn down your house I mean those are sold as consumer devices with all the necessary certification so they are generally safe I would say and we don't modify them those all are the reason why also the more professional device has a Bluetooth interface because it makes the safety easier if you don't have a low voltage signal cable coming out of something that runs AC power then you solve a whole lot of safety problems so yeah I mean all of those have the CE certificates or whatever you need in your country I don't want to take any guarantees on this is 100 cent safe but this is like off the shelf standard hardware made for home use so I would say yes as safe as it gets Thanks and the second one do we have a general guide with Katie to know how to do a general profiling that is a good question I don't think we have a like single place go to thing for like a profiling tutorial but I think there is a lot of material out there and there is a lot of discussions talks and other tutorials on that general subject it might help if we collect that and point people there at least that part is missing yes and last question I think welcome from Heinz hi so this was a lot of talk about measuring usage on the CPU or usage on the GPU from the built-in sensors if you have an Intel CPU with GPU built-in that will also show up as a sensor I think the one of the lines in here the blue one is actually GPU I'm not sure if you get the same level or dedicated graphics cards so that depends on whether they give you access to the sensors they have I'm not sure if we have that but for the built-in embedded Intel GPUs we get that yes alright thank you Volker people asking questions thanks for the online participants for the real life participants here it is lunchtime get out into the hall you can talk to the cute stand they're hiring and you can talk to the sandwich people they're feeding chooses EV board reports the audience chooses nothing you are required to be here it's great there is a million reasons to choose the board there is you can vote for us so welcome back from lunch this is going to be the report of the board and I'm going to give this mic away to Ingo so that I can take a seat there maybe you want to keep it and then we have four microphones let's share as if we were friends feelings nothing more than no not today so let's do this yeah well thanks for joining now we're going to do the KTV board report this is something that we used to do within the HM but then we realized that it was a good idea that everybody who also is not part of the KTV could join and sit so that's why we're doing it here on the main program of Academy for those of you who are EV members there will also be a version of this in the HM for like I don't know all of the information before we get started let's do a super short introduction of ourselves we can do it with the first slide if you want so you can see our names I'm going to start myself, my name is Alish I am the my name is Alish I am from Barcelona and I am the KTV president nowadays Hi, I'm Adrian I'm a roving board member I guess that's all Lydia Hi, I'm Nate Graham I'm another roving board member I'm from the USA, I was just elected last year and I'm happy to see all of you on the board for quite some time currently vice president and we also would have IK here but for personal reasons he unfortunately can't be here so we will do this with the four of us Hi IK if you're watching us he knows everything we're going to say anyway so in this AGM there's three of our roles and this year it's going to be Lydia's, IK as well and mine the three of us have announced that we're running again but if any of you wants to join and fight us in a voting battle of democracy you can do that it will be very interesting and fun for all of us I'm sure cages will be provided if you want it to be a cage match bludgeoning weapons only yeah more on the practical matters of the EV this year we have six new members we have one new member less than last year but a good bunch of new members less than a couple of years ago well if you know somebody who is doing good kitty work and think it would be a good fit remember to invite them it's always a good idea but for now let's thank Raju, Neil, Gumpa, Justin Felix, Natalie and Simon thanks for joining the kitty V this year oh yeah about something I wanted to mention also a big thanks to Adrian who has been a big topic in the past and we hope that with the new work now it's going to be amazing thank you the button got pressed spoilers no the button got stuck well it's the next button it has like two buttons this time okay yeah that's good so one of the big tasks we do besides of you even members is having like individual supporting members who part of what they do is donating there's been like big changes on how donations happen the individual supporting members are still on the previous system and they're being migrated into new fun ways of doing their stuff but we also started using over the recent years and more recently even Donor Box and that's also ways that what people are starting to work to this individual supporting process yeah just the one, yes so those were the individual being like individual people who do it for their own sake these are organizations that participate obviously in a kind of different amount we've had a good number of new ones for the last year and thank you very much to the three of them being Coupon to Focus, Titan, and Ambition but not to the mini-survives the systems Google, SUSE, the Keep Company Canonical, Slimbo, and Tuxedo all of them are KD Patrons being organizations that are part of the KDV and they take part on other spaces like the advisory board for most of them who will get there also we got a new supporter it's one of the minus two they moved from Patron to Supporter the advisory board so the advisory board is a way for organizations to have a say with KDE, not a say in KDE they're not steering but it's good to have that conversation in somewhat private to help those organizations understand where we are going and those organizations can say something about where they would like us to go what their interests are the advisory board consists of both sponsors, patrons such as Blue Systems and Canonical organizations that make heavy use of KDE software the City of Munich and other interested organizations so these are people that we talk with with some regularity and the advisory board calls where we can hear each other out on what is interesting so we'd like to thank Blue Systems, Canonical, the City of Munich, Debian, Fonsnade the Free Software Foundation the Free Software Foundation Europe Open UK, you saw PictureSexito and our new advisory board members Kubutu Focus, G10 Goat and Ambition so that's the advisory board besides the advisory board being the place where we can talk to our supporting organizations we also have other friends partners and affiliations this is ongoing collaboration because it's technical sometimes because we've shared an office or we just feel like doing cool stuff together so Lix and the Qt Project and the Vanda meetings are our friends that do cool stuff KDE Spain is the local organization in Catalonia and Spain and they have a Academy ES a similar kind of event as to what we're having here we're partners with GNOME of course to organize the Linux application summit that's once a year get together to talk about applications going out there the Chaos we are part of the application ecosystem working group, Neofotosis and one of our friends there affiliated with the Free Software Foundation Europe and the Open Invention Network those are free software promoting organizations and the Open UK that do things like patent protection licensing innovation KDE is as an organization also a member of a number of things the OSI, the OIN, OASIS and the Document Foundation that means that we have our little say in how standards are built we have a little say in patent protection for the Linux ecosystem and that's all very useful so that's the way we're involved in the larger ecosystem around us let's switch to a smaller view KDE is no longer a purely volunteer organization we're really happy to have a bunch of contractors and employees that help us achieve the goals of the EV and the goals of the EV are to support you, all of you in getting cool KDE stuff done so first and foremost we should mention Petra who does all the things we will go through these in more detail briefly but I'd also like to mention Joseph, Annika, Paul, Adam, Dina, Diago, Ingle, Natalie and Nicholas and I will tell you all about them in the next slide so Petra I'm sure many of you have come across she's incredible support for the board maintaining our office making sure that you get your reimbursements that our paperwork is in order all these things really important for the EV to run similarly Dina you might have come across her amazing help in making sure this academy runs together with the local team and the rest of the academy team as well as the Linux app summit we couldn't do this without her support then we have Adam who is supporting everything around the goals making sure that the gold champions have what they need that they can meet every now and then and discuss and the same thing with the academy team supporting meetings and so on if you at some point meet project coordination support let me know and we can figure it out which brings I'm sorry which brings us to Lada and Joseph who have joined us for the KDEco program they have done amazing work in making sure that KDE is taking part in the project that all the paperwork gets done that all the community outreach gets done that we get the eco certificate and so on the funding for doubt has by now ended and we are looking for new funding Lana unfortunately left us due to the end of the project but we hope to work with her again and I think that Joseph has been focusing more on community topics which he will talk about in a talk later today or tomorrow I'm not sure you should turn it I think we skipped one yes we did yes next up on our list of contractors we have Paul and Anika our marketing team Paul and Anika have been responsible for helping to improve KDE's presence around the world make sure everybody knows about us this year has been quite a busy year they have been doing a lot of work around the fundraisers and communications regarding that the KDE network is a topic that has seen a lot of work as well to make sure that people are organized around the world they have also helped a lot creating content for external events and helping to promote those they have been updating KDE's presence they have made the jump over to free alternatives know about us and are able to hear about KDE news and they have also helped to create the four kids and four activists and all sorts of other people pages that you can find on kde.org these are really cool pages and finally they also help out with release notes and release announcements for our big releases KDE gear so a lot of work and next up we have our newest contractor Natalie who is our hardware integrator she has started just very recently she has been working to improve the user experience in plasma on devices like the types that are shipped by many of our partners we have a lot of partners and supporters these days who actually sell hardware which is a really exciting topic to my heart it's something that I like to see and so Natalie is helping to make sure that this hardware works better with our software she started with PowerDevil and general power management topics which are always very important especially for devices with batteries this also is a part of the KDE Ego initiative so there is some cross-pollination going on there and we are going to be seeing a lot more from Natalie soon Ingo we did announce last year the first of the make-a-living positions we created including Natalie and then Niko that we are going to talk about later and well Tiago I think that we also put in the back at some point Ingo has been working on bringing or making it easier for all of you to achieve your applications in different platforms there's been good progress on Windows Store and Android so far we're starting to see how to finalize that we're going to have a puff right Ingo over the week actually yeah, right Ingo because it's on the slides well be there if you have an application that you want to see shipped and reach out to Ingo if there's something that you think that could be done at like a KDE level to help you do that but it's very important for us that your applications get out there and hopefully like help fundraise somehow and become part of this well healthy cycle of or have your users making KDE bigger right and Nicolas he started he started this year around February and we've been working so the idea for this position is to be working on the different aspects of our software that are shared and help all of you to work and create your KDE software at the moment this has mostly meant to help with the port and everything to the sixes, the kid six and primary six plasma six and everything in the six now so that's what we've been doing so far yeah, six six six that's what we've been doing so far I will see what the future is going to bring us in and the last of our make a living contractors is Tiago Tiago picked up the long running documentation improvement project we spent some time a long time ago examining what does our documentation need to be really world class Tiago has been picking up individual topics each the last month or two to improve so he's improved the Kirigami documentation has been annoyed at Kconfig haven't we all so he's he's available for writing and general documentation review feel free to reach out to him if you have documentation needs that's it for the contractors and we will move on to events because KDE supports well contractors pays for contractors to improve the KDE software but also with events because events are great because it means you can actually look people in the eye and make funny gestures at them yell at them in person to fix your bugs yeah yeah see where else would you give Kevin to stick out his tongue at you so we're really glad to have all of you here at Academy, Academy is our yearly our biggest our farthest flung event big thank you to the sponsors who have been here one of the topics each year at Academy is where's the next one going to be so if you feel the urge to organize it in R&M then do so anywhere else in the world given the temperatures here right now I think we want the next one to be in Norway in November but that's up to you feel free to organize a new one we don't just do the big events we also do sprints sprints are far more focused small events that pick one special software topic or organizational topic you see that we have EV board sprints that means that we get together either in real life or online and spend a weekend working on administration there's been a KDE Plasma sprint there's PIM which traditionally tries out the cake in Toulouse there's the KDE Eco Sprint we've had a we've had a handful of sprints but not nearly as much as we'd really like and so I'd like to repeat the call to everyone in the KDE community sprints are for you and we're here to make to help you make those happen so if you've got a topic reach out to us, reach out to Adam and we'll make it happen next to our own conferences and our sprints we also of course show up in lots of other places so for example so far we were at Foslum this year KDE Eco was present at LAS and Bundestag we went to something very new the All-American High School Film Festival to get a bit out of our bubble to talk to other people about cool stuff like KDE in life Latine Wear Qt World Summit Qt Comprazil Megacon another one of those things to get us out of the bubble if you want to represent KDE at events you should totally talk to the promo team the board to get help for that if you need it on the side of conferences of our own the last year we had the Academy last year the Linux Upsubmit this year Academy ES and of course this Academy where you are and to make all this happen we need money which fundraising gives us there are quite a few things happening about fundraising as we already talked about we've got new patrons with Kobuntu Focus G10 Code and Ambition together with the fundraising working group we refocused our donations on the new platform Donorbox we ran an end of the year campaign we ran a fundraiser for KDE in life both of which were very successful we have started thinking about how to rate partnership prices starting in 2025 because membership or partnership in KDE EV is comparatively cheap you can still get in before 2025 in the cheap prices tell your boss grants have been successful in that we got the KDE eco grant so far we've unfortunately not been successful in getting a follow up grant if anyone can help with that please come talk to us and Joseph and last but not least we're thinking more about how to actually get paid apps into the proprietary app stores as a sort of revenue for KDE EV and of course as the saying goes do good things and do good things so we're thinking about what to do with them so we also have to tell the world about what we do as the EV and we published a report for 2022 just the other day it's a long and beautiful document with a lot of behind the scenes looks at what's happening in KDE EV and KDE so I already mentioned the fundraiser for KDE life and at last academy we talked about how we want to work with the KDE life team as part of this whole make a living discussion that we try to find dedicated funds for them to improve KDE life as a kind of test balloon to see if that is something that works for KDE EV and the team that wants to do dedicated fundraising the fundraising side of that has proven fairly successful and we're quite happy with that and we're quite happy with the effort that both the KDE life team and the promo team but also the fundraising team have put into this to make it a success because it was quite a bit of work now we have the money and now we need to spend it on improvements to KDE life which is one of the next things that will come up and I'm sure you will hear more about it tomorrow in their keynote so overall this trial dedicated individual project funding continues but things are looking pretty optimistic right now so now is the time when we talk about some of our favorite things the highlights of the year everything that you all accomplished with our help with some really great things we talked a little bit earlier about sprints we were very happy to see that sprints started happening again after the isolation of the COVID pandemic which was no fun we definitely want to see more sprints this is something of our bread and butter so let's see if we can do some more of those we also concluded the Blower Angle project the funding has run out but it has essentially been successful we got an app certified and we've created a lot of interest and momentum behind it I think you saw a lot of engagement about KDE EV and the goal topic before it now continues as a community goal so that's really great we also have our fundraising platform Lydia just spoke on that a little bit but moving to donor box has been really hugely impactful for us and getting a modernized fundraising platform gives us many good options going forward for the future we also have acute six sporting which is going on this is something that's been happening in the background for a while and now starting a few months ago it's happening in the foreground so we're really very happy for all the work that people have done on here I want to call out Nico in particular who has put really a lot of effort into this and the net result is that many people in the audience here myself included are able to actually live on plasma six get master right now okay I'll shut up now it's pretty great and we're also in general seeing more interest in our hardware among our hardware and software partners and one of the things that I missed something that was behind the microphone we filled all the make a living positions this was a multi year effort to start hiring more people and we have now done it so we did a lot of the things we said we were going to do and it's pretty great next slide so what we said we would do number one was reassess our financial situation we definitely wanted to move towards more sustainable funding models and we also wanted to make sure that we were able to keep out of legal hot water we have now succeeded in doing that we have also modernized our donations platform so on the fundraising side in general what we set out to do has been a success we trial project fundraising as Lydia mentioned a little bit ago this has also been a success we're going to be using this experience going forward to do some more things that's very exciting we also wanted to make sure that our infrastructure was able to get lab what has been proceeding everybody is using it now and in the near future we're going to finally 100% move into that cutting off fabricator so that is going to happen as well the next thing is to support the new KDE goals this is something that's been happening over the year speaking personally as a gold champion I feel very well supported I can't speak for everybody else but that's at least one out of three there's going to be time next year possibly the spring, summer keep an eye out if that's something you'd be interested in attending there's going to be more information about that soon in general we would like to see a little bit more community involvement involved in the goals these are definitely community goals as nice as it is to have gold champions with lots and lots of time to work on it sometimes that isn't always possible and so it's great when people take the initiative too so that's something that we would like to see in the coming year we also want to learn a little bit more about our changing ecosystem with regards to how software is distributed and what our position is in the greater free software world this is something you're probably going to hear about in many other forms over the coming conference and we're going to continue to keep an eye on that and finally a big topic this year was to get us all back together in person now we can pretty much all say that the global pandemic is finally over and it is very nice that we're all able to sit here in a conference and enjoy each other's presence so that's pretty great and I'm happy that we've been successful in that so a topic for next year you will see that there's stuff that continues over the years since last year it's not because we think that it wasn't successful but a lot of topics like span over a good amount of time like Nade was saying, kitty goals are working very well but we do miss people joining them it would be interesting to understand what would be the correct dynamic for that to happen because like Nade I was a kitty goal leader for a while and it could feel lonely at times it's a very social issue but I think that from the kitty view we can have that happen and that's been finding the right way to help the goals it's going to be a good source for success for the goals which are in the end a success for kitty itself the financial situation that we keep talking about we had big injections in the past that we had to learn to manage we've done the make a living program that has increased our spending considerably through donations through everything and that's what we're doing and well there's no pandemic anyways but we do believe that meeting is part of the goals for the kitty view turning the kitty from something that is virtual and theoretical into something practical where people get to work together is a big part of what the kitty view does and we need to make sure that our goals as Adrienne mentioned before it's about the conferences but it's also about the the sprints of different meetings that we can have well whichever is the right ways that we have to coordinate among ourselves in any case on the last few years we're talking about the make a living positions about how do we do this we're moving into a mindset of okay we're now spending that money we need to make sure that we're delivering there not to put pressure into all of you working on that on there but actually it's on all of us right like we need to make sure that these positions deliver as well as not us being contracted but us as like whoever benefits from these positions so because all of them I think that we all agree bring important things to the community but nobody can change the world on our own we need to work together so for us making sure that the make a living positions are successful is very important because it's what it's going to bring we believe the story of the next few years of the kitty view in general one trend that we've also been seeing and it's not entirely unrelated to what I was just talking about is getting our products closer to our users we've been very distant to our end users a little bit in this theoretical virtual kind of product that maybe we've been and while that works and it's super fun well it makes us a little bit less relevant finding ways to like touch on what everybody cares about and being able to act on this is something important now you could think this is something more related to what the kitty community does and the different developers but our experience or my experience is that as a kitty we have a lot of possibilities to have there and if there's ways we can do that we will continue doing so like we are already doing now I think that you all agree so this have been the key topics that we see for the kitty view for this year obviously everything is discussable be it at the HM, be it on the health hallways, on the chat rooms online or we're going to have an office hour during the buff days where we can talk about whatever you want to talk about we don't really have a list of topics so feel free to join like I said earlier also if you're thinking about either joining the KTV or joining the KTV board you can reach out to us and we can talk about it like you're welcome to do either of those things it's all fine and fun I would say it's a good thing to do so that's what we wanted to talk about I think that we have some time for questions if any of you have them I just have two questions so I was thinking do you think that decisions for make a living at KDE could also provide some kind of reporting on their activities for the last year a lot of us actually don't get to see much of that work and I'm kind of disconnected as I would love to know and then the other one is that I don't know if you would consider finding help there too but when it comes to design integration I feel like sometimes like some of us designers just have a big bridge to cross when it comes to realizing some of the work we want to do and unless we go and rally some developers that might like what we're doing we have most of the times no chance of making a certain change happen in the system and so I just wanted to suggest that and ask that question to find some kind of UI integrator or something like that maybe it's easier if you do the questions one by one on the reporting something we've told our contractors always maybe it's more relevant for the make a living bu