 Hello again people. So, this is to quickly summarize what the advisory board working group has been doing over the last year. There are a couple of us, as you can see, acting as contact points to various organizations. Adriana, Lace, Cornelius, David, Ike, Kai, Lydia, myself and Tomas. Our goal as advisory board working group is to make sure we maintain good relationships with our partners and other organizations we are close with and make sure there are open channels of communication between us. We already mentioned earlier that we are now at 16 members of the advisory board. As I mistake here actually, Slimbook was already last year a part of us, Taxidon joined us as we already mentioned. What we do is that we mostly organize advisory calls. We try to do at least two calls throughout the year and make sure that all the organizations that are part of our advisory board or at least most of them join us. So, we exchange information, we update them on various fronts. They let us know any developments from their side or ask us questions. So, as we also mentioned, we act as contact members for them. They are our patrons and also other organizations and communities we are affiliated with and they are part of our board, of our advisory board. As members of the advisory board working group, we are there for them to ask any questions and if they want us to act as intermediates to introduce them to various KD projects or contributors, we are trying to help them. So, over the last year and since the previous academy, we held two calls with them in September and May. Our main topics were included updating the advisory board contacts for regarding our two major events, Academy and LANS and LANS and of course, all the other spins that took place. We gave them updates on things like the acute development and how this is going, the KD goals and the plans to do the new ones now. Everything related to the EV and our developments around hiring and our partnerships. We also discussed with them about the fundraising projects. We wanted to start helping. They gave us their feedback because as you know, most of these organizations face similar challenges with us. Many times, they solved it, sometimes with different ways than us. So, it's always good to exchange opinions and insights regarding this. We did also discuss with them our plans about the Making a Living Initiative and all the new positions we want to start. And what we tried to do this year is also to invite some groups from within KD. So, our advisory board members can learn a bit more about what they do and maybe try to interact or take advantage of them in a good way. So, this year we had KD Promo joining us and KD Eco representatives to discuss about what they are doing. In the next year, we want to at least within the year do another advisory board call by the end of the year. So, we inform our context about everything that is going on. And of course, we want to continue to maintain active channels of communication, as I mentioned with them. Try to get money signed from them. As we mentioned also earlier, our organization is growing. Several of the organizations and companies within our advisory board are maybe bigger than us or they have already been through this process. So, we try to learn things from this and other fronts. So, if you want to reach out to us, you can send an email here or, as Alice mentioned, do podcast here at the academy. We're available. And that's it from me. I think then next is David for the community working group. Questions are at the end. So, if you have for a specific working group, just wait for the end of the segment. Hello, I'm representing a community working group. Next slide. Okay, here we are with Valerie, everyone knows. Ashiba is not with us. Andy is not with us today. Me, Andy is hiding somewhere. And Thomas left, unfortunately, yesterday to pursue some other tasks. So, our role is to make sure that the community is working well together, either to help resolve conflicts or get rid of trouble for some people. Last year, about this time, we had a fairly dramatic incident and lasted quite a long time, which escalated even to a police. Fortunately, it's not been initially for a while and we don't need to worry about it. But Thomas did a lot of work here. So, at the end, give him a round of applause. Rest of the year, at the end, rest of the year has been relatively quiet. We've stepped in occasionally, but it's good that we haven't had to do too much. There are some problems that we need to focus on. The biggest problem is we don't have a good handover between people leaving. We don't have a good archive of where this has been a problem in the past and this has been repeating offenders. We also have found that people tend to go to assist admins when they want something done, because they're good at getting things done. We need to work on that relationship. We also need more members. We also need some nice younger blood, because the biggest problem we have is the fact that everyone has got new channels that we're not on because we're old people on ISV and mailing lists. That's where we're finding our problems. That's wrapped up. I'm having bad members in the other area. Go. That's what I just said. Keep going. And if you contact us at the community working group, try. Also to us at our academy whilst we're still here. Hello. I'm here for the KD3Q Foundation and the working group associated to it. Who are we and what we do? You might know what the KD3Q Foundation is and if you don't, you should look it up, because it doesn't have time in this learning talk to explain about it. But basically it's me and Olaf doing some work with counterparts from the Qt company, right? So we make sure free Qt will stay free and staffed. Then we have the working group people, which is David Redondo, Felic Latron, Chris Delo, David Edmondson, Eke Hein and Martin Donald. So that's great. One of the issues we had in the past with the free Qt Foundation, it was very sandalone and siloed work and now we have people in the working groups to help us. So this is amazing. What we do it last year, we've been doing monthly calls on MeetKD.org. That's for the working group. So that's great. I am now the chairman of the free Qt, KD3Q Foundation, which I'm not sure if it's good or not, but that's how it goes. We have worked with the Qt company in making sure everything that we used in Qt 5 was available on Qt 6. It took a bit of going back and forward, but that kind of worked very good. So that was well. As usual, the Qt company is not very awesome when they do messaging about things they are newly releasing and they want to group everything together, and this is Qt, but then they say this is not Qt. So yeah, we made some discussions with them about how they should do their messaging if they're not wanting our agreement to take effect, or if they do, that's fine. But yeah, they need to fix a bit of that. And then there was an issue with the Qt multimedia license they wanted to do for 6.4. We went a bit back and forth because they wanted to change it from LGPL to GPL, and yeah, that didn't end up working for us because there's lots of people that use it. So yeah, we told them, sorry, can't do, and they fixed it, so that was good. Thanks for that. Lessons learned, yeah, we live in a bit of a different world that the people in the Qt company that we are talking to in this level, right, there's like very high management people, so we use different words and different living scenario. So that's not always easy. We're working on it. A good thing is that I'm not, I am not the chairman, that's a success, it seems. Is it? I don't know. I mean, I now need to learn Norwegian, which is not great. Anyhow, the Qt multimedia thing was disagreed and we fixed it, so that was good, and the working group is being super helpful, so kudos for that. Right. Where do we need help? So yeah, we are, like we need to talk to the Qt company, the more backgrounds we have, the better. So if you feel that you have a different background than the people that actually are in the working group, just join us. I mean, it's one hour every month to talk to us, some months every year when we skip it, because there's not much to talk about, so it is not a lot of work, so that would be good if you join. If you can read law and Norwegian law on top of that, you'll be amazing. That's like the biggest thing you can do. We have Frederick, that he can read a bit of Norwegian, but yeah, not a lot. And yeah, just talk with the Qt company people and have established relationships with them. We have David, which is now the maintainer of the Wayland thingies, so that's great. Make sure, I mean, we always do that. We are nice people and they are to most of the degree, they are also nice people. But encourage to do that more often. So yeah, keep doing that. Key goals, so yeah. Yeah, there's, sorry, there's a missing line after Norway, that should be a new paragraph. So yeah, Lars used to live in, Lars from the Qt company, right, used to live in, well, does live in Norway. He knew a lot of Norwegian. He's not part of Qt company anymore, so he's not part of foundation anymore, so we need to figure out, yeah, the whole Norwegian thingies, right, if we need to go to the city council to do something that's going to be a very expensive flight for 30 minutes sign or something. There is a new member from the Qt company coming, because Lars left, that's still not happened, because there were like the holidays in the middle and what not. So we still need to do that. And yeah, try to help them to be understanding of what they can say it's Qt and they cannot say it's Qt. I mean, they can say Qt is whatever they want, right, it's their product, but they need to understand the consequences of saying that. And that was me talk to us. There is a very weird email address to talk to us, right, so it's KDEV3QGG. And if not, you can ping us in Matrix or IRC, or here it's, I think it's only me and David Rodondo, so I mean, we can do that. We are nice people, he's nicer than me because he's younger. So yeah, thank you, and next. Okay, so let's do the reports for the fundraising working group. What do we do? We basically do the, try to identify opportunity for fundraising, like for the current life case. We try to maintain the infrastructure, as well as the CVC-RAM infrastructure, but as well as the new donor box, a system that we are just spoiled by the board reports. And the other coordinate with the promo group to reach more people. So we are, are we? It's me, Kenny and Lise. Yeah, but if you want to join, it would be great because more people is always better, often. Yeah, what did we do last year? I mean, the board always spoiled a bit, a few stuff, but we basically, like, work it on the Canon Live in the company. We already reached 11k e-holes, so quite a lot. And in, like, only after months. Yeah, we also said that maybe the solution to CVC-RAM donor box, what we are doing with Canon Live, and we meet, like, every month, approximately, and meet to talk a bit, to see what's next. Yeah, and our point is for the near future, that's moving to the donor box, because currently, the KDE itself, the donation for KDE itself, are sealed on CVC-RAM, and we want to move that to donor box with the experiment with Canon Live works. Yeah, so for us, it's like, it's super charity because it requires paper, stripe, we don't need to maintain it ourselves, and it's like, it costs a bit of, it's not completely free, but it takes a bit of percentage of the donations, but it's like a lot less work for us. Yeah, like I said, there's a Canon Live campaign, what is the test, sort of, before we move everything from KDE to that system, and we need to do a bit more planning for the actual immigration, because we need to try to convince the people who donate to CVC-RAM to donate to us with donor box, and a few of our administrative tasks, like the KDE membership is also stored in CVC-RAM, but we want to move that to KDE-LAB anyway. And, yeah. And our next steps is like, since the KDE non-discusser act, analyze, yeah, as I already said, particularly, yeah, if you want to meet. And, yeah, if you want to reach us, we have like a public channel where we basically have all communications almost, and then there's also like a private channel where there's more specific information. But, yeah, if you want to join, there's a medicinal, I forgot to put it there, but... And if you want to have a both first day at four in the afternoon, so if you want to join us there, and talk with us, that's your opportunity. And, yeah. And if you want to email us, there's an email address. Okay, and from the CISADME working group, the CISADME working group works on all the server infrastructure for KDE. KDE mostly makes desktop applications, but we also need servers for the websites and hosting the code and all that. As an example, we had 48 terabytes of network traffic in Novost. On average, we did with 185 web requests for a second. As you can see from the email rate, running an email server ourselves is a lot of trouble, but we have to if we are going to deal with these kind of numbers. Our current members include Ben Guxy, Nicolas myself, Bushan, Kenny Coyle, he mostly works on the academy stuff, but he helps us with other services. Harold Ceter was already helping us with a few things, but this year he has formally joined the team, so that's great. And there's other people who are involved in specific services, such as Luigi Toscano with the translation management server. Yes, Bernard takes care of the 3DSD CI nodes and probably a few more that I'm not remembering now. One of the things that we completed this year was the implementation of the GitLab CI. We got all the platforms that we had on the old Jenkins system. We are still missing macOS, but that was not in Jenkins anyway, but we plan to work on that in the future. This made CI finally available for work branches and merge requests on every platform. Moving away from Jenkins also gave us more flexibility and made it easier to deploy new CI workers. That was actually a pain to do if we wanted to add new servers for Jenkins. The Windows jobs are now using Docker, which makes it easier to replicate that environment locally outside our servers and also makes it easier to add new official servers. And to replace the build.kd website where you could see the status of each build, we have a new dashboard using Grafana and Prometheus, and this should allow us to have better insights about notifications when something isn't building or seeing the history of past builds. We also got a new API documentation website with modern tooling. The old one was actually still using some tools from KDE4, which is kind of terrible. About authentication, we started with a service of our own which was made by KDE based on Blender ID. This would have been good to use, but there were some concerns about having to maintain that kind of stuff ourselves. There wasn't much activity in developing it. I would say maybe part of my responsibility that I couldn't quite get involved, but we realized that GitLab actually gives us more stuff what we needed, so it can act as an authentication provider, so why not just use that? Personally, I'm not entirely sure if this is the best way to go, but it's still a step in the right direction. If in the future we decide to go back to my KDE or something like that, it will be much easier than if we were still on the old KDE identity. Half of the work will already be done. We also upgraded some servers like KDE Identity was on an old operating system. Where we need help, well, with our goals that we'll show in a second. We got rid of build.kde.org, which was Jenkins, but we still have our other Jenkins instance, which is the binary factory. Ben already has the overall design for how this will work, especially in terms of security, because we have our code signing keys in there. We have to actually start working and implementing it. We have some servers on a really old version of Ubuntu which will reach end-of-life next year, so we need to upgrade that. There are several websites using Rupal 7, and that's also approaching end-of-life. This is in particular something that people outside the KDE, the ASCIS admin team can help us with. Finally, our form software is really old, and I also tried to get the configuration into a nice git repository so other people could contribute. When I looked at this, how everything was set up on the server, I didn't understand that rat's nest that is probably been there for years. There's plugins that I have no idea where they came from. And also the interface is a bit aged by now, so it seems to be confusing for end-users sometimes. We need to evaluate what we're going to switch to. Flarm is apparently a good option. Some people have also experimented with discourse. There were some concerns about the way discourse was deployed, but I think we can actually work with it anyway. I guess we need to think of what our needs are and compare the different options that are available for the form. And that's it, I guess. If you want to contact us, we are on the KDE CSADMIN IRC and Matrix channel, or the CSADMIN NAT KDE, or private mailing list, all of the team will get it. Thank you very much. Great to see you again from this side of the room. I am here to talk to you about the financial working group, and now I need to figure out what the right button to press is. That's the right button, great. All right, so broadly speaking, our mandate is to make sure that the financial situation of KDEV remains secure and that it is monitored and that we allocate our financial resources with some intentionality and with an understanding of the past and an awareness of the future. A big part of that is actually informing you so that you are aware of our financial situation and what we can do with our resources. Thank you for attending and listening in. We are currently relatively few in the financial working group, but the working group is, I would say, of very good health. We have regular meetings. We have a very equal distribution of work at the moment, so that has worked really well in the past year, and I would like to thank Marta until very much for the help also in putting this document together. It's a bit of a slow button, though. Fascinating. Lydia, your button is very laggy. I should. I like keyboards. It's much nicer. All right, about the past 18 months, there's actually not that much to say. It was a relatively uneventful time financially speaking, which is good because nothing scary happened. Also, we didn't have any big positive surprises, however. We still were dominated by the pandemic. We had put forward a budget plan that saw us outspend our income. We once again failed to achieve that goal because we didn't have a lot of opportunities to spend money. We did not see a return to physical events in the last year, and also our hiring was a bit slower than we had planned. Although it has recently recovered, so we will be catching up to the plan there. Overall, events were again relatively uneventful. Costs were down since events were mostly still held online, and we had already built the infrastructure in the preceding year, so we didn't have any great additional costs. We have charts and pie graphs that you are about to see, and what you will see in them is that the percentage of our personnel spending seems to have grown, and this is largely due to some changes in how we attribute these costs. In the past, we didn't actually put, for example, health insurance and other related costs into that pool, but now we do. We talked a little bit already during the report of the BART about our roster of donors and supporters. We opened up GitHub for recurring and one-time donations and have seen a great response there that has increased our donation income. We have gained a patron, we've lost a supporter, but overall that's, well, financially speaking, still a netwin, and you already heard about this in the last Academy in the early months of 2021. We had a very large one-time donation from Pine64, who remain active in the community and are also an Academy sponsor again. Now, visuals. We will see we have about 240,000 euros on the income side in 2021 and about 218,000 euro on the expense side. So once again, our reserves have grown. We now have accumulated once again very large reserves that we really need to do something about, as we cannot afford to have very large reserves as a non-profit organization. We actually should be accumulating them. As you compare these two slides and the revolution over time, we will also see that overall, the volume of money in and out, if you discount the year 2018, keeps growing slightly, so our financial footprint is increasing. And this is the split. You can see we are absolutely dominated by staff and contractors and by events, which makes sense. Infrastructure does pop up, but it's not a massive cost for us. And that's the footprint of our organization in one slide. Budget plan. So for 2022, we expect only modest growth of our income. Some of our historically always around income sources continue to decrease, in particular the partnerships that we have with Google on their programs. We have Blower Engel also again in this year, which is slightly larger footprint than in the preceding year, but largely income and expense cancelling out each other as per the plan. We are still working on dissolving the KDE League from our American satellite organization that we had, and we expect to receive some remaining funds from them that will show up in our income. The big takeaway is that this is the year that we do expect our expenses to rise sharply, as we've foreseen and in fact planned for multiple years in a row already. This is the year where we have returned to physical travel, and we also have, at the same time, hiring going on and hiring now also happening in a more successful way than we had last year. So that means all of these things are coming together in one point where we will very likely manage in this year to actually outspend our income, which is great because that's been the goal for a couple of years. And it does mean, however, that now is also the time to think about the midterm future. We need all of these activities to be sustainable. In a nutshell, don't join my working group, join the fundraising working group because they have very few members as well. And a couple of years down the road, we will need their work output more than the one of the financial working group. Project-specific fundraising can take a very large role in that and is also something that this working group plans to help with. Project-specific fundraising means that we have income that is earmarked for a particular purpose and that the spending and the use of which is regulated by a group of people outside the financial working group. And that means, first of all, that we need to mark transactions as such, that we know what the money is that is coming in for the project, but we also need to give visibility to the folks that are running that project. So what we would like to do is improve our financial dashboard infrastructure and also give other people that are running projects access and CDEPR and downcharge and see how much money they have in the KDEV bank, so to speak. All right. 2022, I already mentioned a little bit of that is also generally stable. Our sponsor response for Academy is back to pre-pandemic levels, both the number of sponsors and also the pricing. We are hiring very actively now. We have several positions to fill over the coming months and also going into 2023. We see a very slow recovery on the sprint expenses side. We've had some sprints that cost money, but not a whole lot, meaning sprints that are physical. We are very heavily encouraging a return to those, so we have a lot of opportunities to help the fundraising working group. I think it's a fun topic to work on. If you want to contact us, we also do have a mailing address. I have not included it in the slides so that you visit the wonderful KDEV website and learn about all the working groups and then also find our email address there. Thank you. Are there any questions to any of the working groups that have presented right now? I don't see any hands right now, but we have some questions in the chat over here. Could renting KDEV build infrastructure to third-party projects be done for diversified income? Not sure who the question is for specifically. Can we rent our infrastructure for income? If I understand right, the question is, can we build infrastructure on the market as a product and make it available to others? It's a very good question. I think I can at least contemplate some of the aspects that we need to look into. For example, the legalities and the non-profit offering service. There is a lot of paperwork and overhead with such a thing. And this would be a lot of paperwork and effort spent not directly on our own products and initiatives. I'm not sure if it makes sense as a priority, at least. I also think there are likely other funding sources that make more sense. Especially when it comes to our built infrastructure, what I with sort of my EV board had on would like to see is our partners, for example, hardware companies in fact helping more build the infrastructure and providing test machines. Any other questions from the room? Yep. This is for Nicolas. You mentioned about the forums that obviously are very old fashioned and we have used them quite a lot and we found them quite inadequate for all. You mentioned this course, which I know well, what was the other alternative you offered? You talked about? Yes, the other one is called Flarum. I haven't looked into it myself. Mostly, Ben Cooksley was researching it a bit. So, I'm sorry, but I don't have much answers about what it's like. But it seemed to be a good option according to his initial research. One more online question. Some companies expand their offerings by making variant of apps aimed at different users, such as Premier Elements. Could KDE EV sell commercial free open source software licensed for KDE apps aimed at professionals? So, I think this is being done in scope of one of our elected KDE goals, which is, of course, all about the apps and KDE is supporting that also by having hired Ingle recently to support getting KDE applications into app stores. I think that is definitely also aimed at professionals. I think a good example where professionals are willing to pay for it via an app store because they know it supports development of the software and they have the funds. Any other questions from the room? I don't see anyone, so thank you again for the representatives of the working groups.