 So, since last Academy, we are doing KDE EV reports as part of the main program and not only as part of the General Assembly. And this is the first one for this year, which is the report of the board of KDE EV. Since there's a bunch of new people here, if you don't notice, KDE EV is the organization that supports KDE in various matters, financial, legal, organizational, and so on. And this organization has a board. And maybe we start with you. Yes, we do have a board. As you can see, it traditionally has five members. There's only three here today. This is because Tomas Viva unfortunately had a different commitment and couldn't be here. And Andy Betz recently, for personal reasons, had to step down. At least the three of us, of course, our wonderful president, Lydia, Aleish, who has been on the board, I think nearly as long, and me, who joined two years ago as treasurer. So we are five, we want to continue being five. So this year there's two spots to fill, Tomas and Andy. So far we have four candidates, which is Eddie Ocastro, Adrienne De Groot, Kai Uwe, Ulik, and Neofitos Kologatronis. And give them a hand. Thank you. Well, the vote will happen on the AGM on Monday, so, well, think about what you're going to vote. All right. One of the things we noticed last year is that we had very few new members joining the EV, meaning two, and we decided to really do something about this. And lots of people proposed new members. And so this year we have 17 new members. Who of you here is one of them? Raise your hands. Yay! Very cool. All right. In keeping with the last slide, that means our overall member count has increased. You can also see we have a second class of members which are individual supporting members who pay for their membership, who essentially provide a recurring donation to the organization, which we are very grateful for. The number of individual supporting members has gone down in the past year. This is not a nice thing. Fortunately, I can say that I expect this count to go up in the next year. We have a web application that we use to handle the payments by supporting members, which is relate.kd.org. That web app over the last year has had a laundry list of issues. We have contracted to help us fix the issues with that website. It's an installation of CVCRM, which many nonprofit organizations use to do CRM. Progress on fixing that has been pretty good. There's still some more work to do. It's an important topic for us to expand the use of this web application and to make it more convenient to use for prospective supporting members. We want the issues to go away and the teasing issues to be ironed out, but we also want to use it to engage better with supporting members and allow them more freedom in, for example, setting their donation amount. We're working towards that. Brilliant. Works, right? Besides the individuals, meaning, well, actual people, there's some organizations that also support us. We have two programs there. There's the patrons and the supporters. As patrons, we have Blue Systems, Google, SUSE, the kit company, Canonical, Private Internet Access, and IOKA, which give them all a hand. And supporters, we have Pazisco and Gita, and we thank them all a lot. We also have an advisory board since the year before last, where organizations and companies around us can join to get closer to the KDE community and have a closer connection to the KDE community. So there are organizations like the FSF and the FSFE, the Open Source Institute, but also the City of Munich, for example, as one of the big deployments, Abril, Canonical, and IOKA as a new patron. The Document Foundation, Fast Night Jury, as well as the cute company Debian and Private Internet Access. And we have regular calls with them, and they have a dedicated contact in the community that they can talk to and that updates them on new things that might be relevant that are happening in KDE for them. And in addition to the advisory board, we also have a number of community partners. Lix is an application community that does a document publishing application that was founded by the same person who also founded KDE. So those two communities go way back and they continue to be a part of us today. Qt Project, which is the sort of open source backing project for the Qt product. And the Feinrander Meetings, which is an association based in Switzerland that has in the past organized a number of important KDE events, sort of the second largest KDE event of the year at the time. Unfortunately, in the last two years, this event has not been held in Switzerland because of problems securing the venue. They have told us they're working towards securing that again and certainly are motivated to put that event on again in the future. So we're looking forward to that. And then there's, well, even more affiliations. We have the Local Organizations program, which is only signed by KDE Spain now. But, well, if you have an organization in your country and you would like to, well, have an official relationship with the KDEV, this is something we could look into, reach out to us if you're interested. Then we have other affiliates that are organizations that are similar to ours with which we have a relationship like FSFE, OSI, and the OIN. And then we are members of OSI, OIN Oasis, which is the organization behind the ODF format, the CVCRM organization, and the Document Foundation. Also this year, which is a new thing, we did some kind of partnership with NOM to be able to organize the InnoCraft Summit and, well, make sure that nobody dies in the process. Sorry. Sure. All right. The board is, and by extension, the EV and the community is supported by Petra, who you might have seen running around here, who helps us with organizational and financial things. We have two contractors for marketing, Paul and Ivana. Are you here? Probably, yeah, Ivana. Paul. And Juan Carlos Torres is helping us with improving documentation specifically. He started out as, to get an overview of what is actually our current state of the documentation. Right. As Lydia mentioned, we currently have two marketing contractors. This slide is based on their input, so thank you very much for that. We've been working with them for several years now. Their original mandate was to sort of bring KDE Promo back to life and spur the new community around them and make KDE Promo an institution again in the KDE community that our various teams and contributors could go to to get the message out there and to improve the way we promote KDE to the wider world. They've continued to do that. The team has further consolidated. It has further grown. And it has become easier for new people to join the Promo efforts, by documenting things better, by making some decisions on how access, for example, to our various social media accounts are stalled out, and writing down guidelines on how to work with these media. In parallel to that work has continued. The KDE Promo team has assisted many different teams in the community by helping with writing work, by aiding developers in putting publications together without blog posts, without videos, and just generally any promotionally related publication that KDE does these days tends to go through the Promo group, which is great. And Promo also works together with other organs that we have in the community to get work done, for example, the fundraising working group and helps them promote fundraising campaigns and so on. The Promo team has also, this year to right or past year rather, to help us connect to some large organizations outside KDE and maintain those relationships and sort of widen the channel. And been just much more active than before on social media in particular. I mentioned this earlier today during one of the Gold Starks that engaging with the user audience around KDE more in-depth has helped that effort tremendously, and KDE Promo has certainly also been very helpful in enabling that. So thank you to our Promo team. We also had Juan Carlos hired to work on documentation. Hiring is always kind of a difficult topic, especially when we reach out into tasks that were generally done by community people, albeit we don't hire somebody who, like, to do something that is already being done in the community. But, well, it's sensitive. In this case it was for working on documentation and, well, this approach was taken by finding somebody to actually see, not to actually work on documentation directly, but seeing what actually needs doing and, well, how this should be done. Which is actually what Juan Carlos did. Actually he finished on June, like we said earlier. And at the moment, well, he's not hired anymore. The next step would be to hire somebody, be it him or somebody else. There should be possibly a job offer eventually before the end of the year. It's already budgeted, right? He looked into things like API documentation, wikis and onboarding, and defined some goals. He wrote a report, a detailed report. You can look at it on the community mailing list. I think it was, right? So, well, look at it, reach out to him if you have questions or discuss it in the community or at the academy. That's why we're here, right? But in general, the goal is let's have good documentation for everyone, right? All right. Academy 2020, getting the call for locations out for that has been... The call for locations went out on August 21st. It is out now when we created the slides, and it was before that. But yes, so it is out by now, but for various reasons, it was very much later than we would have liked to do this because there was just so much to do for this academy. So, we need to get the word out for next year's academy location everywhere now. So, if you can help us spread the word or if you're thinking about hosting academy next year, please come and talk to us. Please come and talk to the academy team. We're happy to answer any questions you have. All our social media accounts. So, if you have social media accounts, you have Twitter, Facebook, whatever, share it. Share it with all your... We don't know where this can come from. It's on Reddit. It's everywhere, okay? Yes. Please do share it and do consider gathering some people around you to host it yourself, if you could. Yeah, and in general, this year has shown us that we have to increase the number of people who are helping with tasks leading up to academy. So, if you have some spare cycles for helping with academy 2020, that would be amazing. All right. KDEV, of course, exists to help support the KDEV community in its various endeavors. One of the most important things that KDEV does is help organize and, in particular, fund various KDE development sprints and other events. This year, or rather than the last year and this year, we had quite a few sprints. We still want more sprints, but let's look at the list of things that has happened so far. We had two KDE barge sprints this year, one in January in South Korea, and then the second one co-located with the plasma sprint this June. In February, the plasma mobile team had, I think, their first sprint, if I'm not mistaken, and that team came together and did some great work there to move that forward. Then, in March, we had the first goal sprint of the year. As we talked about earlier in the day, the community elected three goals about 18 months ago, and each goal was guaranteed to have a sprint funded to advance their agenda. The privacy sprint happened in Leipzig, and Ivan talked about it in a bit more detail earlier today. Then, a staple of the KDE community is the annual PIM sprint. They, I think, without fail, done it for probably over a decade now. In April, they did it again in France, and from the blog posts I read, it was a good time and productive once again. Valencia was very interesting in June. We had three sprints co-located there. The first one was the bar sprint dimension, then leading into the plasma and the usability and productivity sprint. I was there, I was at all three, it was a wonderful time. I think co-locating the usability and productivity and plasma sprints was a great idea. We had two rooms there, we could separate or merge as needed situationally, so that was great. Then, following that in July, there was another mega sprint, I think it was called early in the day, where we had another goal sprint, the onboarding sprint, co-located with the KDE Connect sprint. In the student showcase, we had a great presentation about porting KDE Connect to Windows. KDE Connect has been a fantastically popular KDE project this year that went far beyond the immediate KDE community, so it's great to see it being spread to new platforms as well. And I think the possibly first ever Quinn sprint. That was great, that happened. It probably helped maybe get the Wayland goal elected this year, as a lot of Wayland related work needs to be done in Quinn, which is our window manager and the way we put our system on screens everywhere. So I'm sure this wasn't the last Quinn sprint and they're hopefully already planning the next one. And finally, Krita. Krita is a painting and illustration app that the KDE community has been making for a long time. Krita has seen an enormous adoption curve over the last few years. That is the fruit of very concerted and amazing labor. And I think the Krita sprint this year was by far the largest they've ever done. I think more than twice as big as the one they did in the previous year. It was very well attended, I think also by new people. And yeah, they had a good time from everything I heard. But we don't organize everything we do. We also enjoy going to other people's events and while attending and talking to people there and telling them what we do. Sometimes by giving a presentation, sometimes by having a booth, we went to Fossum, actually we generally go to Fossum every year for a, we also went to Kidwell Summit, which is Qt's commercial kind of conference, XTC, which is like Academy, but for the ex and Wayland people, ELC, which is the first time we had some kind of relationship with the Linux Foundation. That was kind of interesting. Wasn't there though, but I heard really nice things. GSog Mentor Summit, which is something somewhere we get to go because we are one of the GSog organizations. FreeNode Live, which is organized by FreeNode in the UK. And, well, I hear it's a nice big conference where to talk to about FreeNode open source projects for Asia, which is in Asia. And, well, we need to be there as well. Fossum North in Sweden and Kidcom Brazil, which is in Brazil, and they talked about Qt. We were all there with one or more people. And of course, we also organized our own conferences, which was Academy in last year and Academy. All right, Fundraising. Fundraising is a dedicated working group that the EV has. The Fundraising Working Group will give its own report in the slot following this, so I'll not preempt too much of their content. I will say that we are very glad that we got a new patron to KDEV this year, which is in Ioka, Houtaku Tour. They also joined our advisory board, as mentioned earlier. We look really forward to just deepening that very new relationship over the coming years, hopefully, and look forward to staying in close contact and learning from them. Handshake donations. In 2018, we got a very, very large donation from Handshake, which is a crypto, DNS, crypto coin kind of thing, and they gave large donations to many open source organizations. Those were $300,000 total, and about 100,000 of those were earmarked for Kaleegra. The Kaleegra community, KDEV project, KDEV team, decided to earmark 10% of that to Krita. We're still in the process of figuring out the legal sites of how to actually give that money to Krita. We've made some progress on that, and the Financial Working Group will present some more details on that later. As mentioned earlier, we've been contracting out work to fix up and improve relate.kde.org, which is how we engage with our supporting, paying supporting members to the EV. This slide goes into some more detail on the work that has been going on there. Most importantly, fixing all the teething issues with the PayPal integration after they changed their APIs so that recurring payments from PayPal work again. And we're getting close to allowing donors to set their own amounts, which other organizations have reported great success with sort of improving their overall fundraising, because a lot of people out there are fortunately very, very generous. And we aim to put more effort into that and grow that sort of pathway for fundraising. We intentionally didn't put on an end of the year campaign in 2018, and I think the decision is still out for this year. Historically, the end of the year campaign was a great income source for the KDE community, for KDEV. We've been very fortunate on patronage, on individual donations, and on large unexpected single donations from organizations like Handshake that we sort of didn't need to go to that well. We didn't need to go out there and fundraise via campaigns. Yeah. As every year, there's a KDEV community report. Promo was working on the one for this year. I don't know if we announced it yet. I don't think we did, but well, it's there. You can take a look at it. It will be announced soon in everywhere. All right, and then we spent the morning on it, basically, which is we concluded the first round of the goals with the session this morning. We had sprints, as we had promised the, how did Ivan say this this morning? What did he call it? The goal. Goalkeeper? Goalkeeper, as we promised each of the goalkeepers. And we ran an open process for proposing and selecting the new goals, and we have new goals. All right. Every board report so far has ended with a list of things we hope to accomplish in the coming year. We did that last year. It's time to follow up on whether we followed two on them. We did promise there would be an academy this year. I think all of your guys' presence is ample evidence that we've managed to achieve that. It was a bit of a struggle this year. I think part of that was coming out of Academy 2018, which was relatively speaking a breeze because we had the location in Vienna very early on, which gave us a lot of time to organize that conference. The timetable this year was considerably shorter. We got the location very late, and that made it quite difficult to put everything together in time. I think it came out well, and thanks so much everybody who contributed to that and came through to that. As said on an earlier slide, hopefully we can get the location for 2020 earlier this time and save some of that pain. All right, then in 2017 at that Academy, we came up together with the Gold System. We did the election following that Academy. We elected Golds. We promised that we would keep working on that. We would figure out the succession there, the succession plan, that is when and how to elect the new Golds, perform that election, get those Golds elected. That also happened. We're glad that it happened. Overall I think the feedback today has been that the first Golds have worked out really well, and hopefully we can apply the lessons to learn to the next round and make those even better. We realized over the past year that as in particular the Golds worked out really well and the perception around KDE has improved again that we've been approached by many new partners. You saw this at last year's Academy when quite a few hardware companies ended up coming to the conference, sponsoring the conference, and taking a more active interest in us that we've succeeded in making KDE more attractive for design wins out there. Increasingly as the board, we've been contacted by some of these partner companies and they've asked us, hey, we want to do something with KDE. We want to have KDE stuff in our product, but we need some work on that done and we're not quite sure how to go about getting that work done. Is there anybody who does KDE work for pay? And of course we do have those partners in our ecosystem. We do have wonderful consultancies and also individual consultants who are very well able to commercially support KDE technology. We wanted to sort of surface that better. So the EV worked together on setting up a consultancies program and putting that on the EV's website and formalizing a process for how companies and individuals can get on there. We plan to build on that in the future and hopefully advertise those consultancies in new places, perhaps the cute marketplace that we heard about earlier. And we want to continue working with these partners and then make sure that their needs are met and that they're happy to continue to work in our ecosystem and that KDE technologies work well for them. The advisory board mentioned earlier is an important place for that, yeah. One of the problems we've realized in the past is that HR, as in human resources, is not trivial. We wanted to work further on improving the different processes on the one hand, hiring new people, and then when they're in, keeping them around and happy and making sure that we're doing the whole paperwork around it, well, correct, because, I mean, legal things are not easy. We did a whole lot of that. Actually, Andy had a big background on HR and he was able to give us a lot of his experience. His presence there was really useful. Another point we had last year, like Lydia mentioned earlier, is that we didn't have that many new people. We had quite a lot of new people this year, so, okay. Also remember that you need to keep doing that, inviting valuable people from the community to the EV is important, but we didn't. Yeah, so that brings us to what do we need to do for the coming year, right? This is not the to-do list of the board. This is the to-do list of the EV and the community at large. And of course, yes, the board will have a significant part in that. The first thing we are gonna do is host the Academy next year with at least 150 attendees, for which the first step, as we've been saying, is finding a location. The second thing we were talking about for a while is that you and everyone else in this community is what makes this work, right? What is most important to KDE? And last year, we started investing more in our people by doing trainings at Academy. And we want to do more of that. We don't yet know how exactly, but we have to go that we find at least two ways to do that. If you have ideas, we're more than happy to hear about them. The third thing we said is that a lot of organizations around us and people get more and more concerned, rightfully, about the environment and what their role is in improving the current situation. How do we make our work more sustainable environmentally? And there has been discussions around drafting an environmental responsibility policy for the EV. We don't have an agreed upon draft yet and we want to get there and trial that for six months to see how that affects our work and how that looks in practice. And the fourth point we have is increasing the support networks, increasing the effectiveness of the board's support network. The board can't do all the work on its own and it doesn't. There are working groups and task forces around it that support the board and the EV at large in specific tasks. And those have over time grown kind of organically and it is time to revisit that and look at, okay, what is the role and the responsibilities of each of those and have conversations around, how can we improve that? And we want to sit down with each of the groups and talk about that. All right, so as you will see in a moment in the working group reports, our annual income situation has improved quite a lot. Our annual income in the past year was more than three times of what we have averaged in the years prior. We are a non-profit organization. Our mandate is to put our resources towards the goals of the organization, which is of course to support the KD community. That means we need to find ways to spend our accumulated funds. We've made some progress on that this year there's much more to do. For example, we want to help the goals spend their allocated budgets better than has happened in the first round so far. It is a bit tricky. The board can't do this all by itself for one because we don't really work top down like that. We need the help of the financial working group to help rally the community around doing that. We need your input, we need your ideas and your energy, keep being aware there are a lot of resources available, come up with new ideas, champion them, help us. A continual challenge for board work is to find enough time to document the way we do this. This is very important because if anything, the legacy that any board member will eventually leave behind is the documentation. Succession is very important for KDEV to remain a stable and well-oiled organization. So we definitely want to make it an important goal in the coming year to document at least two of our processes, ideally more. Aleish was talking about how much help we received from Andy during his presence on the board in the matter of HR. He was a professional HR person who was very knowledgeable about that and helped us improve our legal documents in the area of contracts to get us started working on an employee handbook. And we want to continue the work he has started and put some effort into that. We want to increase the way we partner with other organizations around us, both nonprofits as well as commercial entities. Aleish mentioned earlier that this year we are hosting a new conference or rather the second iteration but renamed of the Linux App Summit. Previously it was the Libre App Summit. This conference, this event is about promoting and improving the Linux application ecosystem. So we have many application developers in our community that target not just the KDE Plasma Desktop but also other open source platforms and that means that conference is for you and you should come there, you should engage there and learn from Nome and hopefully they also learn from us and everybody's happy. And this year we had already quite a lot of in-person meetings with KDE partner organizations, some that approached us, others that we approached. We expect this to continue. We will continue to have the board sprints in the next year and we will try our best to co-locate them with meetings of that sort and look very much forward to that. You can always talk to us. We are super nice people. We have a mailing list. There's an IRC channel. We are on all of the internets. Don't hesitate to reach out to us and say something. Thank you. Also here, we are at the academy for the next few days. So, yeah. Well, it kind of makes sense, right? Like you can say who, maybe I cannot go and talk to the president while you can. See? She smiles all the time. So, questions. So you said we got 70 new members for KDEV last year. So my question would be, why should anybody who's not yet in the EV join the EV? And what does one have to do to join the EV? I think that you can answer this question. I mean, if you want, we can do it, but you're also a KDEV member. Well, am I answering that? Shit. All right. Well, the KDEV is very important because it's the organization that holds all of the servers that host all our code and our communication. So without the servers for starters, there's, well, no software for us to do or ways for us to communicate in. And what in general, it's about communication and about having a legal entity that we're able to back the work that we're doing as contributors, as software developers and otherwise. The way to, do you want to explain? Well, I'm going to channel Mirko here who said something very salient to me at some point. I think it was in 2017 when we decided on the whole gold system. His point was that you always have governance in a community like ours. If you don't define it, if you don't engage with it, then governance still happens just very randomly and uncontrolled and not very efficiently. We try to do it better than that. And KDEV is to some extent the organ we have for that. The gold system realizing it was substantially done by KDEV members and by the KDEV part. So if you want to improve the community and want to improve how KDE does things, then joining the EV is the right place to be. It's where a lot of important work gets organized. It's where some important decisions get made. Occasionally, very important votes happen. For these things to happen in a healthy manner, the membership of the EV needs to be a healthy, representative sampling of the community it aims to support. So if you care about KDEV and if you care about KDEV making good decisions for you, then you should be in the membership of KDEV. And the second part of the question which is how to become a member, you need to find a KDEV member and tell him, propose me, or, and then he will give you a set of questions that you will answer and he will send them to the membership. The membership will decide if it makes sense for you to be or if they want you to be a member, which I mean, usually it makes sense. Like it's not about, we are very angry people. But you need to be committed and part of the community before becoming a member. Once the membership process is done, then you become a member. It's for free, there's no fee or anything. So, do it. Did I say it wrong? Well, I'm sorry. And we'll have one more question that's coming from up here. The KDEV India group has been inactive since a year or two and there hasn't been any con.kd.ins in the past two years, including this year. So, how can we improve the conditions for this? I mean, what are we looking at for KDE India Future? So, mostly we have been trying to organize confidant from like last one or two years. So, mostly it's been about finding a right venue and right time. So, I mean like I tried finding two venues and once it was because university exams, which we could not schedule it properly and the second time it was kind of quite too late to finish all the process and organize events. So, it's mostly about if you know the location, just feel free to reach out to me or someone from the KDE India community.