 So I don't know if you know but we are currently in a very defining moment for the future of KD. So KD decides what to focus on in the future using goals and every couple or three years we actually vote to select some goals. The very first ones were about onboarding people or focusing on privacy and then they were changed with goals like consistency which is actually the one that I led for three years and now it's the end of those goals and we are currently voting for a new round of goals that will actually define what the community will focus the most for the next couple of years at least the goals will then live on but we vote for new ones. So this is the page with the goals that will be voted so let's actually go through them so you can see what we are currently voting on and if I recall correctly all of KD developers vote and you can actually see the goals and know in case which goals are selected what will happen. So first one is probably my favorite is automate and systematize internal processes which when it was first proposed was actually called professionalize KD but apparently that wasn't a good enough for a name and what this talks about is I think really focusing on increasing the quality the end quality of the KD product as a whole by making sure that to make some examples that we have a QA team that actually reviews every merge request and make sure that there are no bugs and also having tests having a lot of tests and making sure that merge requests cannot get in if all the tests are not passing or are passing stuff like this making sure that you have the CI in GitLab these kind of things. Also the first proposal of this the first version of this proposal also talked about actually having developers to work on KD stuff internally currently KD does not quite hire developers for KDE related like very KD projects there are some developers that are hired for as an example work on hardware that runs on KDE and stuff like that also people that work on promotion but this actually said okay now let's actually hire people to work on KDE products that the end user will use I think it was removed from the proposal as it's more of a KDEv thing which is the organization that legally represents KDE and not as a whole from the organization but we do still have let's actually zoom in some nice proposals like having linters automatic fuzzing also coding and documenting the steps required for QA and one thing that I really like which I cannot see right now in this list is when like a developer wants to actually step back from the KD community sometime it happens for personal reasons or whatever to actually make a process so that you can follow to make sure that all of the things he was working on keep on being maintained and everything so I think this is a very nice goal you can read it it's publicly available just like all goals the next one is making flatbacks a first class delivery method for KDE apps this was actually worked a lot already for the KDE is all about the apps goal that we had in the past version and what is this about well you guessed it making sure that all KDE apps are on flat up and making sure that they work very nice that we have a process to easily actually you know port new apps for being on the flat up store and this kind of stuff and it's especially important I really like that the author actually pointed this out because of stuff like the steam deck where KDE Plasma is pre-installed and the flatback is the only application installation method so if you want to install anything on this thing that you have to use flatbacks so all apps all KDE apps that are not available as a flatback won't be able to be installed if you don't know what flatback is go check it out I use it a lot actually but I'm not very expert next one is the totally offline productivity and privacy pcpda workflow and I'm gonna say I'm biased on this one because personally personally I do not like this goal I think it goes very against what KDE should be but it's only my opinion and we'll actually vote on this to make sure if to see if it's the opinion of others or if I'm in the minority we'll see so what this talks about is making sure that offline news is primary first class for KDE products and to be clear all KDE Plasma KDE products as a whole if they should work without internet they do work without internet they are already very adapted to being offline KDE Plasma is that I stop perfectly works offline obviously and if you actually see the motivation I don't quite agree with the motivation it talks about the fact that computers should not be communication mediums and it talks about this a lot so go check it out if you want to know more about this maybe you disagree with me and personally I found that very wrong like I think that computer are very much meant to communicate with other people or I don't know what you do videos have like that that is communicating right now I'm communicating to you and that is very much a primary idea of how computers should work and if we do go check out how this should work what things we should do to actually implement this goal there's a couple of ideas here I'm not sold on the ideas either sadly so as an example KDE Marble which is currently the application of KDE that shows maps should include offline routing which is easily exportable to a pocket device and to be clear KDE Marble as far as I know doesn't quite have routing at all currently maybe I'm wrong but that's what I recall so the idea of having offline routing we should have routing in the first place to have that I mean we could work specifically to have offline routing I guess but osman google maps do have offline routing already and frankly they are better than KDE Marble and work already on a pocket device so you don't even even have to export so I don't see the point also a plasma mobile optimized version that allows for import of city specific channel transfer again as far as I know we don't have that stuff maybe I'm completely wrong so it's not about making sure that it works offline it's having that in the first place I don't know another example is complex analysis of music preferences which are blah blah blah that were ans a feature of america one dot four bring that sort of local preference learning back we don't even have online preference learning so I don't understand I'm sorry I just don't get this goal so you can actually go through this read this all and make your own opinion next one is KD for all boosting accessibility I don't have a much to say about this except that I will surely vote for this goal because I do think this is something that should be worked on in the KDE community really it's really important however I'm completely ignorant about this matter so I can try my best but I need to learn I want to vote this goal because hopefully it will also teach me as part of the goal how to actually improve these kind of things it talks about what you could guess like having magnification also color contrast focus handling making sure that all of these components of KDE are available through keyboard usage these kind of things so KDE for all boosting accessibility then we have sustainable software a very interesting one which talks specifically about sustainability in terms of pollution and using energy and the idea is that the influence of software and sustainability is not well understood yet and KDE does actually work a lot already already to make sure that you can like measure how energy efficient their programs are and we do have a certification by blue and girl blue angel I don't know about this given to ocular the pdf application which is very interesting and these goals elaborate on it say what we should do the next steps to make sure that KDE software is as energy efficient but also that KDE connect as an organization to it says use its visibility to contribute to sustainability these kind of things so very interesting very eco then there is human centered KDE which was this close to being thrown away simply because the person that actually proposed this goal kind of left the KDE community so if you don't have a champion for the goal you can't like vote the goal because nobody would actually take a delete but since I really like this goal I actually stood up and said okay no I really like this so I will propose myself as the champion of this goal which I didn't write just because I want it for at least to be voted because I think this is a really nice goal so currently this is the goal that I'm proposing me even though I did not plan on proposing any goal but again I just wanted this one to be at least voted and it's about making sure that KDE is designed for users and it's really easy for developers and I'm putting myself into that a lot to say okay I know what KDE should look like should behave like and know how you I know what's best for users there's a lot of that and although we are often right how developers are often right about what users expect from the product this talks about well things like usability research which we don't do at all currently in KDE so that could be something really nice and also stuff like QX testing these kind of things are discussed in this goal you can read all of it it's very interesting I didn't write it but I thought it was worth a shot and finally this is a goal that sadly didn't make it for a very similar reason the person that originally proposed the goal went inactive and nobody actually stood up for this one if I could have proposed two goals then I would have also tried to be champion this one because I think this one also deserves voting but I cannot and I prefer to be here so this one probably won't get voted nonetheless it's a very interesting goal and the idea is making sure that our documentation to actually develop things in KDE is very nice and this is very important for onboarding because new developers need a good documentation to understand what's going on but even for developers like me which already have been on board I do need some documentation that I can understand sometimes that would make my life easier sadly again didn't make it maybe next time I don't know but KDE does make an effort to make sure that the documentation is nice KDE actually hired the KDE EV hired a person to do a review of what's wrong with our current documentation I didn't see what happened with that but there is an effort in this sense the fact that it's not a goal doesn't mean that it won't happen at all and that was it for this voting what would you personally vote and if you are a KDE developer remember to vote these goals the email to vote should go out very soon maybe even before this video is published I don't know and thank you a lot to the patreons and the donations and always remember that this sidebar here is always like one or two days behind because I'm recording these videos in advance when I can so if your donation isn't in the list don't worry just give it a couple of days but thank you really a lot to everybody it's good to be welcome back and already having some new patreons I'm really happy so see you tomorrow with another video