 Working group reports, yeah. We will do working group reports in four minutes and if you have more questions that we couldn't answer now You know where to put us Bullet points, and we're not hiding either. Just grab us Hi everyone So yeah, very quickly for those that do not know of us the community working home takes care of the community actually So in then what you're asked to do is to enable Discussions to flow in a healthy way within the community maintain good relationships between Between our people and whenever we're asked to we step in to resolve some conflicts of situations We are three members what are currently active and we're all here today and during Academy It's David at Muslim at the beds over there and myself who I joined last year So I've been around for one year and We've we had two members stepping down since last year Bhavisha and Valerie who Didn't have the time to help more So very quickly to go over our work over the past year What we tried to do and with the help of CIS admin we achieved is to create this private space a private team on Invented kitty the dog as you understand lots of times the work the community work in group is asked to do is a bit It's a bit on the edge of it. We should it be public or not Sometimes we have to handle more indicates situations So it's good to have a private space where we can talk between us and that time times also with the board in order to coordinate and how we act on this and Of course, it's a way for us now to document all the work we've been doing So we can track previous discussions. We can track previous complaints See how we handle those in the past or as new members come in they can go back and see so that's a very We think it's an important next step for us in terms of the even We Realized that the website on the On the way web page is kind of outdated. Let's say it's been around for a lot of time now The working group has been around for I think 15 years now and lots of the formation there is not up to date. So we want to We already started working on update it update in it But we need to continue on that and make sure it represents where we're currently standing and where we want to go In terms of actual, let's say Request that came in since our last AGM. We had a total of four requests These were about two community members Specifically and actually three of those requests were about one specific Individual and as you see one was a misunderstanding that is the other two we had to step up and try to take action Just so you know what kind of types of requests we usually get you will see that a sample from the last year at least It's a small one, but it's I think indicative enough One of them was about major request the process. So we had a person and Let's say doing some things and not in the standardized way merging Some code and then we had complaints about the process that that was happening and the other was about in problem behavior or people reacting to Two things in let's say not good ways Now in terms of the lessons we learned You can understand as I mentioned that many times We have to stab in and discuss things that are not always right or wrong or yes or no very clear answers So the important thing here is for us three different individuals to try and discuss and you know try to establish an action plan when we have a complaint and Set the expectations of what we expect from the Person in question or the people involved. So it's the let's say the hard work We need to put in is usually when we discussed about a specific case to try and understand take as much information in from the people that are involved try to make the Try to for us to have a good understanding of what is happening and then we need to reach a consensus Or we'll try to reach a consensus of how we act because we we want to give clear guidelines on what the next step is to the people involved and not you know Having them confused or not not giving clear answers Which usually doesn't help if you leave out things in the open when you're doing this kind of work You it can easily go either way One lesson we learned in that we should probably try to be responding faster to me to people Making requests both once they do the complaint. So yeah, you had a complaint It's good for you to know that we are on it So that's the first step and then once we have taken action It's good to go back and follow up to that person to say hey This is what we do if it's still a problem and do this and that so this is something we can and definitely improve Another thing we learned I already mentioned it earlier. It's about documenting our discussion. This is something we're doing now It helps a lot going back having a history of how we what the complaints where that came in What what was our discussion? How did it evolve and what was then the result? And so we can use that in order to be faster maybe in responding to future requests or you know as a reference when we're doing that and Another thing that we saw that will probably be useful that sometimes you have this like repeating let's say Problems so it would be good for us from time to time when we're talking to people to have a place The way you have your code of contact where you point people at it would be good to have Let's say some type of wiki or page where we can point people to To see what's been asked for them and how they were expected They are expected to act in specific situations Of course as we all you saw were three persons where we could use all the help we can get In order to achieve what I already mentioned try to be faster and when looking into new requests Sometimes these things take time. You need to take a step back discuss take action talk to people gather data information make sure everybody understands the what what the position there then discuss it internally then go out And give some you know guidelines on what should happen Maybe sometimes you need to coordinate it with the board. You need to coordinate it. We see that to me So it takes time and it will have more persons. Maybe we can push that forward faster and then We want to try it if we have the help us of course to expand our role a bit more and be more proactive because usually the way We act is when we're being called upon when there's a complaint when there's a request So we need we're more reactive and if we have more people and more resources We can be more proactive to quickly Conclude our key goals for the coming year is that we want to start having regular meetings Which we haven't had so far. We can use this as working sessions as well to start talking About how we want to evolve if no request comes up for a Big amount of time. That's a good thing. I guess for our community Hopefully things are not happening or learning about them. But at the same time, it's good for us to stay connected and have something to Commonplace where we can work and progress As I mentioned already the websites and the wiki that we want to maybe start working on it And then a bit more is about our own identity as a community working group From my time at least in the board as well. I know that sometimes the community had a specific you know perspective on how the community working group should act and There are things I think we can improve on top of that We now have Joseph was working more on community topics. We think we can work together with him much more We are already trying to be at places like the forum that discuss the TV and things like that So we can act as moderators as well We'll have direct access to these kind of discussions and then in general try to do more community building work Unless let's say policing and supporting people when they there are conflicts As I mentioned all three of us are here. You can talk to us, but also if you prefer to do it online You can email us at this address. Thank you Financial working group our job is to help the treasurer with Money related issues and the whole board in general with money related things and helping the community come up with a budget and stick to your budget The people on the financial working group are Ika, Marta and Sil. I am none of those people I'm filling in because unfortunately They couldn't make it So message these people Overview of this year. We finally outspent our income. We've had a lot of income We've got a lot of reserves aboard. We're talking about it a lot and we deliberately outspent our income and it's important to stress that And this is partly because Pandemic is over COVID doesn't exist anymore and we've made an effort to hire more people But that doesn't mean our income was bad in 2022. In fact, it increased From all our previous years. It would be exciting grass later, but it's increasing more unjust inflation But I've mentioned deliberately it increased expenses multi-personnel and Planning a spot on we were within 1.5% of planned budget so graphs General trend upwards 2018 was an exception where magic stuff happened where we've got loads of money But we're still improving nonetheless and expenses going up Because we've got money to spend So this year we outspent our income, which is what we wanted to do graphs 2023 The budget plan made staying on course. We're still trying to burn through some of those reserves Responsibly not just spending it all on biscuits for a board And but because we're outspending our income, we do need to make sure our fundraising coming up next It's staying on top to keep up with our new expenses that we want to keep on doing forever and ever So how's 2023 looking on track? We've got three new patrons Yay, and we're pleased with Academy sponsorships and everything's going well It's also a new tool written by Icahine Which is going to allow a financial working group to get real-time feedback on what's happening with the money rather than doing this Long manual work once a year. So that hopefully would mean more time for doing more productive tasks And here's some screenshots of it with graphs And it's going to be amazing Thank you, and we're continuing with the money with the fundraising working group Okay, so after the finisher is a fundraising every get the money So what we are doing is like we're trying to identify a fundraising opportunities like I'm putting it with The food as an execution of the food in campaigns Investions try to Convince the food team to collect the materials Like the end of the year campaign and We also like working on the infrastructure For the donations So what we are, so it's me Lace, Lace, Nate, and also Lydia with Epin So this year we like did the kind of fundraising campaign which was like First the notebooks based campaign we did and it was like a huge success And he has a number that he was like a lot of people donated We got some monthly and annual as a requirement donations, which is even better than one-time donations Yeah, we also did like an end of the year campaign It was also like a huge success Like we plan to the goal was 20,000 and we got more which is always good Also like a lot of stats, so I think there's a documents online somewhere Yeah, so someone someone to see this is the key one of the sets later Yeah, so pretty for the next two is a fairly moving away from CVCM We are not really happy with CVCM. We talked about moving from CVCM since yes, and now we are doing it and we really like Nation campaigns about based on the notebooks and we are hoping to Shut down the CVCM essence soon Yeah, and big thanks to the promo team who was really helpful with the fundraising campaigns Thanks Oh, we're moving on to the non-money parts of it to the legal pieces So this is the report of the KDE Frigid Working Group and also bit also of the foundation Our members in the foundation of KDE are Albert and Olaf Albert has a talk in the other room So I'm doing the report And the other members are me Chris, Iker, Federeck, Martin and the newest member Victoria Since last year's Academy actually So what we did we usually meet monthly and discuss any topics that come up in the foundation to support our members And all we also have a chat channel on matrix to discuss any issues that pop up and Instant action or discussion or like other our opinions on matters And the foundation itself had one virtual meeting because nobody wants to travel to Finland or Norway all the time The cute company has a new member you are Pekan Amy and who's replacing last knoll Who was also the chairman in the past and the foundation thanks him for all the work he has done there so What we achieved last year? Was many managed to get the accounting on time submitted to the authorities, which was a Bit stressful because the accountants actually Wanted to have Albert signature like few days before they need to be sent to the authorities in Norway Was a bit short on time The Relations with the cute company members are good as we are told also with the new member and and the Foundation turned 25 years old and cute is still free software. So that's an achievement that we have What we need to do where we need your help is The cute company asked us if we could have a meeting with KDE people to discuss things about cute It was not quite clear to us what they really expected from us, but if you Think of something or know something who would be useful to meet with the cute company talk to us And in general be in good relations with the cute company and the fruit project and Work with them collaborate with them. We nice to them thank you thank you so much and that brings us to the last one which is About all the infrastructure we run on from this is a mess Okay, so this report is prepared by Ben, but Yeah, so we basically make sure that our servers continue to run and our services continue to run and so So data points that are interesting are like we handle 47 terabytes of data in June month and That completely excludes what CDN and cloud where already like handles for us and we And we saw average 170 we have request for second and this excludes the good lab because good lab is like other much larger thing So these are our members and Also, like we have got support from other community members on very specific services. For example, the Sanctuary or things like that I think this is like a recurring item because every time the Essentially server run Always running on the server runs out of like support and we need to like rebuild our servers so we We rebuild the server that push our website and Also, we took over the Discuss instance of the Discourse instance of the creta and Like due to website work done by our web team the also eliminated Capacity a framework like it was it was powering our old websites Also the due to like open street map and all that requirements We we were running out of the space or on the our CDN server so we also had to rebuild and expand it and Also the Alex are which we use for hosting the various Like hosting the allowing the developers to source our code so that also we move to different server and Also, some of the improvements is like the big blue button What was previously happening was that it was on the smaller server So if you wanted to push some Sprint or if you wanted to push some meeting you had to call like you had to create a sysad mitigate You had to ask us like please increase it for this period and we had to then increase it and then we had to decrease it and so it was bit of a Bit of manual work that we had to do But now we put it in like already much larger servers So like we don't need to do that scale up and down dance essentially so that also like one of the thing is like we moved away from the digital ocean to Hasner because digital ocean essentially had a Cloud-based CPU so it was not so performing and now this is like a native hardware and Yeah, I mentioned the creature artist or two RG, which is like this course forum that we took over hosting also GitLab continues to be like GitLab migration continues to be like Going ahead. So we have Quite bit of updates happening to GitLab regularly, they basically release every month more or less and We also did some of the CI work So basically when we started GitLab migration our plan was to basically do it in the three different steps. So one was like Hushed in the code then Having the normal CI and then binary factory. So we also have like proof of concept builds for This binary factory There is a buff about it that we have to also We can we have to discuss it and we have to finalize it Also Docker Hub basically made it made it commercial So we had to push the Docker registry for our self because Like if you had to go through like Docker up then it You can only pull pull in Docker images for some Limited time and that was not really scalable for our CI Okay, so where we need help So we there are there are like our egos. So GitLab signing service I think as I mentioned there is a buff about it we also have to migrate our tasks because That is the only thing that is keeping the fabricator alive so we have to like Other create like we have to create archive and we also have to move those tasks to GitLab and Yeah, so we have to rebuild our mail system which includes the migration to mailman 3 and Retirement of my kitty and kitty identity. I think like right now There is only one or two services which are actually using carry identity and rest of the things have been migrated to GitLab as a like authentication server So yeah any questions or maybe we don't have time for it. I don't know We have plenty of time for questions, but it can be questions versus admin it can be questions to any of the other working groups Well, if you all get on stage Can you touch your nose? Do we have any sensible questions from the audience for any of our working groups? May ask Carl to remind me at least what What's the percentage that donor box keeps when we get a donation as I think it was five percent But I'm not competition. I can say again Other questions from the audience or you've been so tremendously informative and clear That we have no questions and that we can go for coffee early