 All right, it is 2130 in UTC plus 2 1930 in UTC. It's 2020 and we've just finished the 6th day of Academy. I'm Adrian and I'd like to tell you invite you to the boff wrap up. Julian is already complaining that it might not be 2020. So, hey, times and dates are an opinion and certainly if you've ever read the K calendar core unit tests, you know that times and dates are very opinionated. I have three things that need to go in the announcements today. One is that there's one last escape room one last chance to murder your fellow Academy peoples or maybe discover the murderer. And you can do that at 2030 UTC that's in one. I was going to say one hour it's in 59 minutes. You'll still need to register if that's of interest. Tomorrow there's a pub quiz. You don't need to sign up for the pub quiz. That's when Paul and I are going to try to be funny to all of you. And I'm sure Adam will and John will be there to heckle us. I'd like to remind everyone as well that we ask you not to record the boff sessions. Please don't record them. We that because that puts a lot of load on the server and we don't like it. I'm so glad that we're also arguing about French abbreviations for UTC. But in the meantime, I'd like to invite the people from this morning's boff, the licensing boff, Andreas Korot Landwehr was running the show. Hi. We had a really good boff this morning. We talked about how to better present licenses of our applications and libraries to the user. The main outcome is that we will try to create one or two websites that's not clearly decided yet. Mostly inspired by what the creative comments people are doing. It's a clear message what are the benefits and what are the expectations when people are using our applications and libraries, split it by what are the target groups. And that we want to use as a central information page used from several locations. And there is a new licensing team on the GitLab instance where we're starting to organize it. Okay. Thanks Andreas. It's good to see the licensing stuff moving forward. Lots of new information there. Nicolas, I would like to invite you to tell us about Android things. So we talked about one of our favorite Linux based mobile operating systems, not the favorite. In particular, we talked about our tooling that runs the binary factory and can also help a lot when developing apps yourself, how we can improve it, how we can improve the workflow of developing with it, and where we need more documentation. And on the code side, we talked about moving forward with some ongoing work that is right now living in several different repos and where we would like to move them to a more canonical place in frameworks. Alright, thanks Nicolas. Moving on from the second most favorite Linux based mobile operating system to the most favorite, the Plasma Mobile BoF. Was it 11 this morning? Someone from the Plasma Mobile team. Hi again. We talked about our favorite mobile operating system. In particular, first of all, we talked about our bi-weekly blog posts that have sadly been anything but bi-weekly and how we can convince ourselves to push them more regularly. So we agreed to do them monthly now and we talked about some aspects of the presentation of the release and how we're going to work on them. On the technical side, we talked a bit about performance. Unfortunately, on the current neon images we have since like two weeks ago, pretty severe performance regression. We talked about some aspects of that and also some general notes on how we could potentially improve the performance of the whole system. Then we took a look at some of the larger outstanding tasks and talked about how to move forward with them. We also took a look at the tasks on our 1.0 work board. Close some of them because they were actually done and for the others, yeah, discussed on how to proceed there. Thanks, Nicholas, for summing up all of our favorite mobile operating systems. After the break, things continued in sort of a hardware vein with the KDE hardware collaboration BoF. Alesh, you ran that show? Yeah, he's in there. So we need someone else to do it. I can do it. Albert, please. So yeah, there was a bit of a summary of what our current collaborations are. Basically, Slimbook and the Pine people. And then we kind of went into a tangent from hardware to software in the fact that to be able to talk to hardware companies, you need to be able to provide the full software stack yourself. And we aren't doing that or we are depending how you consider neon to be or not a software distribution. So we had some discussions about that. Also, there was some discussions about how the world's moving a bit away from x86 to ARM. And we should try to figure out if and how we support ARM a bit better. Yeah, that's what I remember. That would be it. All right, thanks Albert. Then we had the ocular BoF, which was run by Albert. Hey, welcome back. Hello. So yeah, the ocular BoF we had discussed. So there have been some patches that we introduced in the previous release and they have some nice effects, but then they also caused some progressions. There was some discussions about what to do with them if you just revert them or not. We would come up with a list of things we want to fix it before saying we're going to revert them. So we are giving ourselves some time before the branching for 2012 to fix those. And if not, we will have to sadly revert the changes, but we're hoping we're going to fix them. So I hope there. We wanted to talk about the website, but then we collided with the website both. So nobody from the website team was there. So we basically did not talk about it. There were some considerations about when we're moving to Qt6 and Framework 6. Yeah, we will need to probably drop some backends, but it's not very used backends. So hopefully it won't hurt us very much. Yeah, we decided to stop using the versioning we used. The ocular is a version 1.something, nobody knows or something, but we're going to go just to the 20.08.1 or 20.12 that everybody uses. That's going to be simpler. Cornelius joined a bit to talk about the Blue Angel thing that it seems it's going to be using ocular as one of the main points to test how good we are with the environment and whatnot. Yeah, there's a few more things. I will send the full report to the mailing list. All in all, it was a very good buff, I think. All right, thanks, Albert. It's really good when buff managers send a summary to the mailing list, because that means that everyone who's also not here can read up on it afterwards. I see Kairu mentioning a dedicated Blue Angel buff on Friday. Things have been rescheduled. Anyway, ocular got cruelly cut off by much more important things like Python. So, Christian, tell us about the Python. I don't know if it's more important, but it's important, I will say. So yeah, we talked many things. First, I gave an overview of all these things about PyQ, PySide and everything, so just to clarify some misunderstanding. And then we started to roll some ideas. There are many cool opportunities to maybe try to make some of the KDE applications scriptable, kind of implementing some plug-in system and so on and so forth, but we needed some action points. So the first thing that we want to try, if someone here is interested in this, is that we want to provide Kirigami for PyQ and PySide users so everyone can use this delightful QML framework to build their own desktop applications even. And so this will be kind of the first step. And the second and third and so on and so forth will be to see more or less what else will be worth doing, maybe trying to improve PyKDE5 effort that is already there in FabricatoralRead and other crazy ideas about maybe having some binding generated things system-wide so other people can create bindings for our second favorite language, Python. All right, thank you, Christian. That wraps it up for Room 1 today. We'll move on to Room 2. Thanks, Allison, for setting up the slides with the schedule here for me. That helps a lot. And I'd like to thank Kenny and Kenny also for running the whole show in the background and Mamalok for doing the Infodesk stuff. Without you, the conference would be much less. Thank you. In Room 2, we had some of our newest kinds of contributors. Season of KDE and Google Summer of Code, BoF, run by Kaio. Kaio, are you here? I don't see Kaio. Anyone else from the GSOC BoF available to tell us about it? I see lots of people typing, so I'm going to give it a minute. It seems that the GSOC BoF doesn't have someone here right now at the BoF wrap-up available to talk about it. So let's move on to the KDE Web stuff. Karl Schwann, please tell us. Yes, so we had a Web site BoF, and we talked about the task on the fabricator board. Mainly the remaining website to update and to move forward with, for example, the Okula Web site and a few others. We still need to find more contributors because it's a considerable amount of work. And that's it. All right, thanks Karl. Moving on in Room 2, we had two hours worth of consistency talk. Consistency is one of the three KDE goals voted in by the members of KDEV and members of the KDE community. So it's really good to see the goals or the consistency goals group sitting down together. Nicolo or Claudius? Yes, we talked about many topics such as the icon sizes in the panel, the window decoration and in some ways in which we could improve them, the web style, the course on and the fund managers. Again, regarding this, we saw a presentation by Claudius regarding consistency from a user point of view. And then we talked about QML and QV just starting problems. All right. Thanks Nicolo. That wraps it up for Room 2 today. So moving on to Room 4, there we go. Boff Room 3. With this is admin Boff, Nicolas. Okay. First, before the Boff, we had a brief talk with Volker about some new setup where he's planning to do for vector maps for marble and for catingery. Then in the actual Boff, we didn't take proper notes and now that I was checking the details, we covered quite a few topics. We talked about how people can contribute without having actual access to the servers, which should make it easier both for people who are already in the community and for brand new people to KDE to help. But we would like to know what people are interested in contributing to so that we prioritize making it easier for those particular websites to be run locally. We talked briefly about the new c-summing documentation and getting some feedback from people who have maybe more experience on documenting that kind of stuff. We discussed how we might do the migration from KDE identity to the new MyKDE. Then we also discussed MirrorBrain, which is used for our download mirror network. It's currently unmanned and we are looking for replacement and we should probably talk to other communities like GNOME or Linux distributions who probably have similar needs and problems as us. Finally, there was some discussion about whether we should have a strict requirement of only running free software on our servers. If it's really that important, there are some cases where there are licenses that aren't strictly free software but don't really have any practical legal issues. After all, most of us went to Carl's web both. That's all I guess. Okay, thanks Nicolas. I'm sure that will be a spirited discussion about free software or not on our servers. Moving on, we have the J'ai compris meeting which was run by Timothée. Hi, sorry my webcam again doesn't work so I'll just do audio. So we had a great meeting for J'ai compris today. We covered a lot of interesting topics from the future migration to Qt-Qt Controls 2 which we really want to do but we will have particularly issues with the calendar module which is missing so we need to see how to proceed. We discussed about how to improve the time to switch the activities categories because in the latest version that increased a bit, we need to see how to improve that. We discussed of course the release plan for 1.0, the string freeze next week and how we will work with the promo team to advertise the release. We discussed about the plans for the future admin feature. We basically made a plan how to proceed. And we discussed about the future localized dataset feature which actually we need the first that we have the admin part so users from around the world can create their own dataset and share it so we can integrate some of those. We discussed about the user manual that we are going to generate and we need to improve a bit that generation and we need more feedback from translators to see where strings need context and more feedback from teachers for activities and other stuff. That's it. Alright, thank you Timothy. That wraps it up for Room 3 today. Moving on to Room 4, we have José van den Oever. Joss and Meven, they talked about rust. Rust never sleeps, so here's Joss. Joss, you are on mute. Let me fix that. Yes, so we had a very nice above. We started off with a poll among the 20 participants and asked them, do you know about rust? Have you read about it in a blog or have you actually ever written some rust? Well, most people just heard about it and wanted to know more. So we started off with an introduction about what is rust? What are the advantages? How does it work? And that was very nice. Meven and I switched in introducing various parts of the language which we live coded in a rust playground. And then we got to talking, how can we combine cute and rust? We demoed a couple of applications, such as a middle client that I wrote in Rust and cute. In the last part, we talked about how KDE can benefit from rust. So we came to the conclusion that C++ applications, libraries, frameworks, they can actually use rust inside of them, but we shouldn't try to wrap KDE inside of rust crates. So rust can really be like a strong dependable engine inside of our software. And maybe at some point we can also publish pure rust code, but we shouldn't expect to put KDE code inside of rust, but the other way around, rust can go inside of KDE applications. A couple of suggestions were to use rust for CSS, SVG functionality where there are some very nice libraries at the moment, or we could use it to make Baloo more stable and secure or Kaio. Those are two parts of KDE that are really nicely separated, which could be swapped out or maybe slowly moved into a different programming language. Then we ended up by opening communication channels, and we are still there now discussing how to work on this. All right, thanks Jules. I realize now that I should have made a mutable joke at the start of this. Moving on, we have one boff session left before this wrap-up is wrapped up. The KDEV fundraising working group sat down with Aleish. Aleish is still at dinner. So if someone else from the fundraising group wants to say something about it, no one is jumping at the opportunity to talk about the fundraising working group. I thought we were going to have someone else join. So yeah, we discussed some of the problems we've been having over the last year, in particular trying to unify the way that we just communicate together. So we're moving our main communication channel off of a hybrid of a mailing list and a telegram group to a slightly more free approach, which is the same mailing list, but the same mailing list and matrix. We also discussed some plans around our technology platforms and also our messaging. So we're going to try to spend a bit of work into our long-term messaging. We're also trying to work on CIFI CRM. We know CIFI CRM has been a long-running problem for the community for quite some time. So this year is a year that we're really hoping to crack it. And as always, if anyone is watching us live or seeing the video, or is interested in joining the fundraising working group, you're more than welcome to just get in touch. All right, thanks Kenny. We're just about done. I just wanted to share my screen to show you off the pub quiz. The pub quiz is tomorrow. You don't have to sign up. You can just show up. And Paul, that's the one with the magnificent beard. And I will try to entertain you. We'll see you tomorrow. Have a lovely evening. Hit the hallway tracks and do good stuff with good free software. Cheers.