 Hey! Recently I've done this video which talks about the goals and I talk about how we were going to choose them by voting and we've done that. I'm currently at Barcelona for the KD Academy, largest KD conference that happens every year and there has been the voting for the goals and we have the new goals which are sustainable software, atomize everything and KD for all. I'm going to go through them but before that a couple of quick you know explanation on how the goals work they are selected in theory every couple of years. In this case we actually got three because you know the pandemic didn't allow us to do enough. So we previously had three goals already. I was one of the gold champions which are the people that actually bring forward the goals and what happens to the old goals that's a question I so the goals that we currently have so consistency Wayland and KD is all about the apps will continue to live because as soon as a community actually starts working on these kind of things you never quite stop. Simply we go ahead, we go through them and we take new goals to actually address, we create infrastructure for them. We also allocate actually some money for the goals if they need it till now they never needed it. Second question that you might have okay when is this going to happen again and this is actually going to happen every two years in theory or three if we get yet another let's hope not. Who voted? The KD developers. So actually who is a KD developer and who isn't? Isn't that clear and at the end it was mostly decided by Adam which is okay who is Adam that's another good question. Adam is the coordinator for these these kind of things is a community manager and he actually organizes the voting and everything so he decides all KD developers with a developer account get to vote and if somebody is involved in KDE but does not have a developer account he should ask Adam and he still gets to vote. How many people voted? Well for the past previous two times 600 people voted this time only 400 so there is a bit of an issue there maybe it's something to look after in the future making sure that not too many people lose interest in this. How does the voting work? Well all KD developers actually choose all goals from their top favorite to the least favorite and then there is a little script which has been written by Kevin and well at the beginning it was a temporary script written in PHP but since we used it every time now it's been standardized and it is the script to actually read the votes and decide which one are selected. So which one were selected again KD for all which is about accessibility, automatize everything and sustainable software. Let's quickly go through them to see what do they bring with them. Okay so the first one is KD for all which is about accessibility this goal has been proposed by Karl Schwann quick info about who is Karl Schwann and that is important because he's going to be the gold champion and the gold champion is the person that actually brings the goal forward. Karl joined KD in 2018 so around when I joined two and he has done a lot of work both on the website and also on some curriculum application as an example he contributed a lot I think he created a calendar but also Neochat and Tokodon which are pretty big applications. He proposed the accessibility goal this is because well he says we can create amazing software but not everyone can use it and that's an issue which is fair enough. He talks about how some things like the lack of keyboard navigation can be an issue for some people with disabilities and how we also need to improve in camps like special input methods voice braille and also UI elements that need to zoom in to actually see them so magnification these kind of things are necessary for a good accessible software. This goal is particularly important because if you do want to if you do want KD Plasma to be used in the corporate world or even in the public world for you know states well you need to comply with some accessibility standards that KD Plasma currently does not comply to which is a big issue so accessibility is very important. So let's look at the plan that Karl wrote. He talks about how we should start by looking at the state of art when using Wayland and Flatpaks as an example how containers actually change the situation. There's particular emphasis on screen readers and then he talks about how we need to fix the software one by one which is surely is going to be a complex thing to do that will require the effort of all people in the KD community but also documentation about the best practices because to be honest many developers me included me first maybe do not quite understand everything about accessibility. Personally I totally need a guide that tells me how to do good accessibility accessible software. He also talks about blogging about it which is something that I highly highly recommend. I've been a blog champion a goal champion and I think that blogging about the goals is the best thing you can do to get you know people to actually work on them and then also talks about reaching out to the communities who will benefit from this work and asking for feedback makes complete sense. Secondly we have to automatize everything by Nate but before we get into that one quick thing that's nothing so this goal has been proposed by Nate Graham again he joined in 2018 2020 so similarly to me and Karl and he was actually one of the a goal champion of the very first edition of the KD goals with the goal usability and productivity which you might know because he did blog posts about them they're very famous these week in KD blog posts were originally named this week in or not not even usability and accessibility productivity sorry for KD so that's where it came from. The blog series is still present which really shows how a goal never ends even if you select new ones. He also is a QA manager in the blue systems I've talked about blue systems yesterday and it generally works on Eliza and Patron Plasma I meant Plasma. Regarding this goal he actually talks about how KD is a community where people keep on entering and on exiting so the personal knowledge of all the people actually comes and goes so he talks about how we should make sure that there's internal processes and systems that take that knowledge and make it available for all of the people even if the regional creator of those technologies went outside of the community. We do already have some team-based workflows and documentation this is very new we recently moved to GitLab which allowed us to do many new things before that we were on Fabricator which was not as awesome and he actually proposes a very long list of things so I am going to go through a couple of points that I think are particularly cool he talks about making a template merge request so when you create a new merge request you actually get all the information that you should supply when doing one. He talks about adding a QML linter what's that QML is a programming language that's used to do the UI of Plasma and many applications and a linter is a program that makes sure that the syntax is correct or should I say like pretty like done correctly I mean not that it doesn't work but that it's correctly written in the code you know you know what a linter is don't make me explain he also talks about making sure that you either delete or fix all the tests that are filling and that everybody is ignoring and stuff like automatic spell checking and making sure that all strings actually are translated out of the box we can actually automatize these kind of things then he talks about creating a document that tells you all the steps you need to do to perform Q&A on the software on KD create and document again have enough boarding process because whenever somebody actually needs to get out of KD for whatever reason it happens we need actually system in place to make sure that everything he was maintaining as an example doesn't go rotten and that his knowledge more in general can be preserved within the community it talks about making sure that K user feedback actually makes sense that he is actually sending more data of course with the consent of the user only if the user turns it on as it is currently but the kind of data that would actually help the visual design group to make good decisions on the software he also talks about improving our release toolings and something that I see him talking a lot did a lot these days because you know is actually here with me I talk to him these days and he talks about actually releasing making making doorlies of plasma frameworks have more sense because right now I've done a video about that it is not aligned with plasma and there's a reason for that but as an effect sometimes you do have bugs that you can just not work around it also talks about in the goal to encourage apps to join the KD gear if you don't know what's the KD gear is the release casual for the majority of KD applications and also make ups adopt its version in schema so they don't have to be self-released and then he talks about the improving the developer internal process documentation having better garden gardening theme having having better QA team this kind of things then there is sustainable software which has been proposed by Cornelius I actually don't know Cornelius and luckily he's not at this KD academy so I can't go ahead and talk to him he got into topic he says in the 2019 chaos communication congress about how climate friendly software is and they talked about the sustainability criteria for resource and energy efficient software for blue angle or angel I don't know which is not blue system different thing so he actually went ahead and had the mission to make sure that KD software was sustainable according to blue angel which nowadays his actually ocular is the first application to actually have reached that goal and here at academy we actually had a cake with the KD logo need to the KD echo logo need to you know have a party thanks to ocular this one as a goal is the actually longest if you want to read through it you can see it here I do suggest you to give it a look it talks about you know the fact that our planet is at stake which is very much true so we need to find and implement more sustainable way to live and this also passes through software yes even KD software it talks about how we have been driven by sustainable principles since our inception and how software freedom is at the core of ethical use of software giving it giving people control to take responsible decisions as an example KD runs on software sorry on run sorry sorry on hardware that companies might have given up for years so you have some super old computer you can still run KD software on it to extend its life cycle and of course that avoids more pollution and then it talks about what the blue angel or angle certification is it's issued from the german government all of these things are particularly interesting so I suggest that you go to the link that is in the video description if I didn't forget to link it if I did so sorry tell me I'll add it and thanks everybody for watching I hope to bring more exciting news for KD Academy