 All right, with the first people already here, maybe we can start a bit early because there's a lot of content to get through. All right, so welcome everyone to the report of the working groups. The working groups are a really important part of KDE EV and they help the EV do work on really important topics. We have several of those working groups and they will now talk a bit about their work over the last year. And we will start with Thomas who will talk about the community working group. Hello, hello. Yes, thank you very much. So basically the community working group is the people that we will try to talk to if something wrong is happening or if somebody is annoying you or if there is any kind of firefighter, if people are not actually following the code of conduct or if you basically just want a shoulder to cry on for a bit, we are good shoulders, we can listen. But 2020 was really tough on a lot of people and sometimes it was because of KDE, sometimes it was because of the word sucks, sometimes it was because corona and sometimes just happens. And when you can't really be around people, things will get better. We are beings, we are social beings. We like to use social networks, we like to use Twitter and we are social. The problems we couldn't be as social as we wanted on this year. So a lot of people started to misbehave and because of that we had to actually remove, and this was one of the first instances that we actually had to remove a blog from the planet because of misbehavior. The second blog that we removed from the planet was not because of misbehavior, but because of the person's request so that does not really count. The same blog that we removed from the KDE planet we had to also remove, we asked them to remove from the Free Desktop Foundation. I don't remember the name of the planet, just Free Desktop something because of the same violations. And we had a severe case of incidents on Telegram because of a rogue administration. Someone was not feeling well and he had a problem and the problem was really intense for him and he started to lash out on people. The problem is that because Telegram is Telegram we could not do anything, we could not remove ownership, we could not even talk to Telegram. They basically ignore and this went on for more than three months with threats, real threats. In the end he moved on. Our work in the past year was, a lot of people started to commit to Master without using merger requests. Please don't do that. This is not nice for your fellow developer. And when that happened, code was started to be reverted without approval or reviews. Also please don't do that. Talk to people, communicate. It will be better if people communicate. And code being refused for QT4 compatibility. People QT4 it's 10 years old and we don't have any kind of update from the QT company. Let QT4 die please. It's time to let the past go. Lesson learned. We can count on the communities, even non-KD communities. We can count on GNOME, we can count on the free desktop and they will help us. I had a few meetings with GNOME talking about the code of conducts, talk about how to deal with communities. This also happened with the free desktop. But we also realized that we can't count on Telegram's management. We basically ignored everything that we tried to talk to them. And we cannot ignore red flags. If we see a red flag talk to us, because red flags tends to grow. Please, next. And we have two new members. One was just recently and I haven't updated the community working groups' slides. So we have Bevisia, who is now a proud community working group member and she already started on handle cases. And we also have David Edmondson, who is now also a proud community working group member and he already didn't start on handle cases because we haven't got a case for him yet, which is awesome. Next. And we are Bevisia, Tomas. Valoiri, that's a typo there because I always must type her name and she says that she likes it, so I kept it. And David Edmondson, so far. We still need more people that can handle stress, but I think four people is good enough for the moments. And we are the community working group. Please talk to us if you need a shoulder or if you just want to talk or if you have a complaint. This is our email. Thank you, Tomas, and thank you community working group. And with that, I hand over to Olaf. Yeah, hello. I'm presenting about the KDE Frequent Foundation. The KDE Frequent Foundation is a legal construct created by KDE Entraltech. And so it has been around many, many years now. It ensures that Qt will always be available as free software. KDE has two representatives in the foundation and since last Academy, the two representatives are supported by a working group. During the past year, the main topic was the decision of the Qt company to limit long-term support releases to paying customers. The legal agreements that we have require that the Qt company open source all Qt releases after one year. So for KDE, of course, the main question was what do we do in the meantime for supporting Qt 5? We decided to tackle this question not through the foundation itself because it's not mainly a legal question and started with mainly the KDE v-board working on it together with volunteers from the Frequent Working Group. And now I hand over to Fredrik Glatham who will now talk about this working group a bit more. Thanks, yeah. So thank you, Olaf. It's awesome all the work you've been putting in together with Martin. Maybe we just go to the next slide. I just want to say who we are, not talk too much about things happening in the background. Yeah, we have Martin Konold and Olaf who just presented the Frequent Foundation. And of course they are part of the working group because we are there to support them. And then there's Albert, Chris, David, Ike and me. Yeah, hopefully you know some of us. We have been around for a while and we of course do care about Qt and KDE. So we are there to support the Frequent Foundation. We discuss various issues. Our interest is not always 100% aligned with what the Qt company does. We try to find good solutions. We look at technical things like, what is actually changing Qt 5 to 6? Do we have to be aware of changes? Is there something missing or so? And yeah, that's basically it. We tried to inform the KDE membership a bit and Olaf took the last two points here. So I think we can just move on. Yeah, thank you very much. Thank you, Frederik, Olaf and everyone else who is helping us ensure that Qt stays free software and available to KDE. And then let's go to Bushan and the assessment working group. Hello. So next slide please. So we are basically looking after the servers and the services of KDE. So we have some of the data points. So in this one, when this presentation was written, it was April month. So there are 40 terabytes of data in April month. 190 web requests per second on average and some of our front-end servers like CDN 17, 7, and cluster handles some of more requests. And we have almost 500,000 emails per week. So we have four members right now, Ben, Nicholas, myself, and Candy. And there are some members who are who are involved in handling some specific servers and systems. Next slide. So we have one of the very major thing we did this year was a deployment of my KDE. So it's a complete replacement. Well, not complete yet, just yet, but it is internet to be replacement of our KDE identity, which is like it's a major pain point right now. And so, yeah, that is based on O2 and newer my KDE already handles logging for server services like VKs, academic sites, and things like that. Next slide. We also improved several services like we changed our mirror management software. That brought some more improvements because the mirror brain was pretty much outdated slash out of support. And at the same time, we also deployed directs for match.kde.org. Thank you, Walker, for help on this. And yeah, so this also makes it possible to use higher quality vector based maps on clients like marble or KDE identity. Next slide. We also tried to basically get rid of some of the services and tried to consolidate these things. So we basically put some of the server, some of the Python entropy applications on the single server. We also got rid of Ketolite instance, which was basically only for KDE neon depositories and also parted our Kthooks to Python 3 because why not? Who uses Python 2 anymore? Next. We also operated several of systems. The upgrade happens by having a totally new server and basically setting it up instead of just operating servers in place. And some of the servers are replaced this way. The more details of this are in the reports, written reports we have sent on KDE membership mailing list. Next slide, please. So there are some topics that we need help. They are on the next slide. So, yeah. So one of the key goals we want to achieve next year is introduction of GitLab CI to replace both KDE.KDE.org and binary factory and also sort out our saturation regarding collaborative editors to KDE.org because it is using LDAC as a backend right now and its performance is pretty brutal. So we need to figure out replacement and sort out situation and this also involves that we need to upgrade our next cloud which requires a newer server because, for example, next cloud wants newer libraries so we want something like open to 24 servers. So there are three topics right now but surely we do have more topics. You can reach us in KDE's admin channel or you can also ping us in private if you have any questions. Yeah, that's it. Thank you, Bushan. That's a ton of stuff. Really cool. Thank you for doing all of that. And then I hand over to Neofitos for the advisory board working group. Thank you, Lydia. Can I go to the next slide, please? Thank you. So the library goal has the goal of ensuring good relationships between KDE and all our important partners and we also represent the collaboration in general with this organization and other communities are part of our board. Next slide, please. So as you can see, there are many people of us. There's board people like Adrian, Leish, Lydia, myself and Nike but we also have on board Cornelius, David, Kai and Thomas who are our contacts to many of the organizations that are part of the board. Next slide. What our tasks are. First of all, we organize advisory board calls to make sure all organizations stay close to us. They are updated about what's currently happening within our community and our products and that we have a chance to communicate with each other both the KDE and the partners but also the partners between them so they can discuss on topics and exchange knowledge. We also act as contact persons for the members of the KDE advisory board. These include our KDE patrons and also all the allied communities and NGOs in our ecosystem that can be part of our advisory board. We are available for all the advisory board members for any input and questions from these organizations in regard to KDE and we're also responsible for getting them in touch with the KDE projects or contributors that might help them on specific topics or have specific questions that they need answers to. So to share some updates that happen since the previous academy, we held one advisory board call in January earlier this year. Our many topics included the outcome of our two major events, Academy and Lands, that this year they were taking place for the first time online. So we had our whole experience and lessons learned from these events to share. We had all the updates on the QTS that the KDE focused on the board already mentioned at the working group. We had the updates from our goal. We have many developments in KDEV and also we had many new partners to share. So we discussed a bit on all those topics. We also brought up the discussion about making a living out of KDEV. This is something that other organizations in our network are doing but in parallel so there was a lot of discussion there, knowledge to be exchanged and we're still trying to figure out things on our end with the help of our partners. So in terms of our plans for 2021 we also discussed all the new events that we have coming up. The Academy that is happening now last that took place a couple of weeks ago and of course the KDEV that we want to celebrate in a very major way. I think it's in October. Another update is that we welcome a new advisory board member which is Prime 64 which is now a KDEV patron and also very recently it's one of the slides. Slimbook also joined us as a patron so we're very happy to have these two new hardware partners which also showcases our commitment to increase those kind of partnerships. Our key goals going forward for the next year we want to at least hold one more call by the end of the year. This plan of our plan to hold at least two calls every year so we can stay in touch with our partners. Ideally maybe we can hold another one by the end of the year so we can make it three this year. That would be great. What we also want to do is start poking on our contacts more frequently because we have many issues coming up as we've mentioned our organization is growing and we believe we have lots of things to learn from partners that are already at other stages of their growth so we have experiences to share on policies and best practices on how to handle or hiring how to manage our staff and contractors and all those kind of topics where we can draw information and knowledge from what our partners are doing. So if you want to join us or ask us something feel free to reach out at the advisory board contacts at KDEV.org and we'll be happy to respond. I think that's all from us. Thank you. Thank you Nia Pridus. Carl is unfortunately just now having computer problems so we will skip ahead to the financial working group with ICA and get back to the fundraising working group after that. ICA. Yeah, hello. We actually have a couple of new faces in the financial working group and we are immediately throwing them into the cold water and giving the first or the second slide after the title to Till Adam. Still time to turn on your camera I think. I'm showing. Can you hear me at least? Yes, we can hear you. Okay, very well. Lovely. Now you should be able to see me also Hi there. Hi everyone, I'm Till. I started contributing to KDE 19 years ago so I'm looking forward to my 20-year anniversary. I used to contribute to KDE PIM and lately I do SOOT staff so I didn't get to go. All right, the financial working group. Basically what we do is we try and support the membership, the community and the board with financial stuff because we have the misfortune of working in that kind of space trying to contribute our experience there so we help the treasurer. We help make decisions and suggestions to the board. Anything around numbers, commercial money we try to communicate to the community and to the outside around financial stuff. We help with the reports obviously that the treasurer does and we maybe crucially help with the budget which we will be talking about a little bit. Please slide, please. We've had a complete turnover in the membership of this working group. I think I was in the working group before so I'm kind of returning. Myself and Marta are completely new. Aiko of course is still the treasurer so he's part of the working group as part of that. New Futures is still around but not in the working group anymore and I think David is still around for the purposes of this report but we'll then be phasing out. Okay, Aiko. Before I take that slide let me tell you thank you to everyone who was in the financial working group up until now. Daniela, David, New Futures all did great work and helped very much. I think has decided unfortunately to move on to the community working group to spread his awesomeness there I will very much miss his colorful presentations of our colorful charts but we get them one last time for now this year so I look forward to that already. But yeah, 2020 we had quite a year didn't we? We originally had the budget plan then we decided to kind of start over we're getting real, we decided that we couldn't decide a lot so we decided to get more conservative as a result and maybe not take as many risks as we otherwise might have. Overall though we came through it really, really well if anything the pandemic largely simplified doing our finances because one of our largest financial activities is generally organizing and funding events and subsidizing travel towards them that really didn't happen in 2020 so overall there was much less to do. Our income sources remain stable or in fact improved our one-time donations from just regular individuals and other large contributors increased by around 40% so people felt really generous I cannot explain why really it's quite fascinating either we did just amazing work and people were more excited about KDE as a result or people really wondered who might be hurting during the pandemic who could I be helping and decided KDE was worth their attention and love in any case thank you very much to all of our donors we also received on top of that a very large one-time donation by the Handshake Foundation again thank you to them as well what did decrease unfortunately in membership programs that is some of code and code in that we've done together with Google for many years this is not unexpected we've seen that trending down year over year in terms of enthusiasm, our participation and I think that is also even going beyond KDE towards other organizations to participate in these programs as well overall our financial assets once again have improved in 2020 we have more cash than ever and you need to start spending it and now a bit of a zoom in on the details charts so everything's generally been quite consistent except for 2018 which was mental in this current year we've somewhat regressed back to your mean if you don't include a big large one-time donation we actually did slightly worse in our previous years it's partly because we normally get a little bit more with Academy which was a bit different last year but because we got that additional one-time donation we're still slightly up from the previous years except for 2018 which was mental next slide expenses we have massive reserves and every year we say we're trying to spend more and we earn because we're a non-profit we shouldn't be earning a profit and every year we fail again this was partly because of Academy not really going exactly as intended so we spent even less than we planned to and less than previous years because of it and as I mentioned we got more profit by accident and if we look in detail try and break it down income mostly came from these individual donations and that massive one-time handshake donation all our other funding are trending down from previous years expenses primarily staff and contractors and we'll see this is going to be taking up a large part of our expenditures moving forwards alright so as for the plan we will of course try to yet again do a better job of spending money hopefully more successfully this time the income is expected to remain stable it has actually already been stable through Q1 and the way of spending more money is to contract more we can go into some detail about what that is as you can see on the slide it's Blauer Engel, it's Krita and other things that is in the process of happening so we're pretty confident that we can in fact spend that money this year and overall of course we as mentioned have to spend money because we are a non-profit and we can't be sitting on a money so we are yet again expecting basically a stable situation with higher spending let's see on that place yep so how's it been going so far this year it's always nice to do an academy in the middle of the year because then we can not just look back at 2020 but also some of the current year so far things have been going really well as mentioned already in the board report we gained two new payments this year market companies that's quite interesting like also mentioned previously we see that kind of relationship growing and expanding and happening more often in recent years also for example this year's academy we have remarkable as a new sponsor for the first time we'll also make an exciting Linux based device so devices and embedded stuff around KDE keeps happening that's quite exciting that further grows there in the future we also got a very large one-time donation by Pine64 in relation to their release of the PinePhone KDE Community Edition thank you very much for that in general donation income remains stable and also turns up we've seen about a 10% improvement across almost every type of donation in the first quarter we have received most of the outstanding payments related to 2020 activities if you look very closely into the fine print of those charts that you just saw one of the reasons why the income bar for 2020 was a little bit down versus 2019 is that some payments were late that had to do with when the invoice done partially if you had added that outstanding income on top you would have actually been slightly above the 2019 bar unfortunately we've received most of them by now for example the sponsorship proceeds from the Nox apps from that year so that's good travel expenditure has continued to be zero we've not had any physical events but we may see that towards the end of the year at least we're prepared for it so if any physical events do happen this year still then we might see some expenditure there hiring for the new contractor positions that I have mentioned has progressed so far as plans we made a plan to create these positions all throughout the year we have contracted two new folks to work on technical documentation and documentation infrastructure in support of the KDE community already and we will be proceeding with the other hiring in the coming month 2022 is going to get interesting because we expect at least a substantial return to physical travel and physical events and we will have all of these new contractors and so we will see the combined effects of that and the combined effect on our expenses specifically which will be very high so 2022 will also be the year where we have to reevaluate our fundraising and we have to make sure that what we are doing can become sustainable for a longer time future so we have a lot to do in the financial working group next year and in the community as a whole but overall it's a really exciting place to be we've finally grown our resources to the point where we can dispatch and actually implement some of these new activities and these are good problems to have so looking forward to doing the work next year all right and if you have any questions I don't think you have time for that but do ask them in the chat we can as a group respond as well, thank you. Please do ask questions in the chat and now we can go back to Carl for the fundraising working group to tell us how people can actually help us make all this planning that the financial working group has done work Carl we can't hear you yet Carl it seems the computer gods do not like Carl today it seems Carl it seems that your mic is connected to the blue button so it might be a system issue choose another mic or something No, did it work? Yeah Okay, perfect so this is a report from the fundraising working group the fundraising working group tried to fund fundraising opportunities to and also maintains the technical infrastructure around the donation systems like for example CVCAM and the donation buttons around the websites and we tried to coordinate with the pro team and for our fundraising campaign so we with Kenny Nate Scarlett Nicolo and Andy what we did last year we working with the CVCAM protectors new protectors and try to improve the infrastructures around Relay.key.org we also move it over to communication from telegram to matrix that makes me really happy we had multiple meetings at onmit.key.org we tried to make it one month a month but we didn't achieve it every month we also refreshed the visual design of Relay.key.org and the donation page n.key.org with a new cool design and we also tried to make it easier to work on CVCAM with a docker setup and just complete CVCAM setup ready open for the future we tried to do the thing that we promised to do last three years that means like seeing the non-disclosure act because we are handling sensitive information like the contact of the donateors and it's a nice argument around that and we also tried to support the fundraising effort for our Linux absolute graphic goodies for people who donate for KD in campaigns and also improve the working group communication to the outside we also researched CVCAM Attractives because we have some problems with CVCAM it's hard to maintain and it's very slow and we will try to work with the KD EV board to try to find the viables Attractives and if you have suggestions please contact us we will quickly get that and if you are contacting us we will also try to make it easier for people to join us and move to a public channel for the communication for most of the communication and have CVAT matrix channel and live for CVAT sensitive information and we also try to keep doing everything every first Sunday of the month through PPM or ATC please contact us please email us and we will hopefully have soon a matrix room where you can join us ok thanks thank you Carl alright you were all amazing and are done much quicker than I was expecting that is very cool which means we have a tiny bit of time for Q&A if there are any questions Adam? Yes there are and I just saw that Ike has already responded to one in the chat Ike do you want to reiterate that question and answer here live or skip to the next one I can definitely do that if you want so the question was one that I went out to all working groups which is what is the thing that everyone can do to help the working groups be more effective for the financial working group the main thing is we continue to do awesome work in your catering projects anything that makes the public excited it helps with fundraising which makes our work I would say more stress free and more enjoyable and as you heard spending money is not easy if you have it actually it's quite difficult but it's so much better than being stressed for it that really helps the most the other thing is just we deal with a lot of the KDEV's financial documents and bookkeeping so anything that makes that easy and saves a bit of time if you use reimbursements.k.org and we are really timely I'm good there on finding all your info and all your receipts that helps if you send KDEV money we have money transfer writing a good memo so it's easy to see what the transfer is about these types of things it makes some of the tedious work a little bit more enjoyable so a bit faster that helps ok thanks that question was to all working groups again and then you can jump in as you want so what's a thing that the board membership or wider community can do to help your work or improve your effectiveness I think for the precute support working group we mostly would benefit from somebody that can push us a bit to have regular meetings we are all super busy and it's very easy to forget about the stuff when life gets busy so having somebody that feels like they can just make sure that once a month we meet that would be awesome we are mostly looking at people inside the KDEV since we do handle some sensitive information and we don't want to drag stuff out public unnecessarily when negotiations are ongoing I think everybody understands that should I just pass on who wants to be next Karl? or the KDE precute working group given the wider picture I think it's very very helpful but so many KDE people are also involved in Qt project and generally being visible about that you know Qt is free software and contributing to Qt and using Qt with a commercial contract are not exclusive to each other make that visible that it can really be a great cooperation where everyone finishes where everyone benefits from our side the advisory board if you are in close contact with a first organization that could join and add value to our advisory board please pick up this contact with them see how it can cooperate if you are close to maybe a corporation get them to be patron they do lots of help to the fundraising working group and the financial working group and then they can join in our advisory board and have all that knowledge in the board as well so from the CIS admin side I think it's mostly on the technical side as I mentioned like in the last slide of our presentation we outlined some of the issues we also have a Qt lab part where you can find over some of our tasks and so you can jump on those tasks and help us from the fundraising group it's mostly about trying to find and so either I just solve the CIS admin problems or I just found the other alternatives to the CIS admin I really starting to get a list of requirements alternatives that we could use and we need to then decide what to do next if that was everyone then I think it's time to switch over to the next one thank you very much all for joining answering these questions and presenting the working groups reports for this year