 Alright, welcome all my friends to the Academy Boff Wrap Up for Thursday. Because of the day trip we had yesterday, I'm going to be calling on the Wednesday Boffs first, just so that we can have complete coverage. And then we'll do Thursday after that. Looking at the schedule for Wednesday, we had not so much key signing as signing our artifacts. Remember that, Harald? Yeah, we talked about signing and it's super important and we've come up with a plan on how to atomize things a bit more, which should make things even greater. That's about it. Much greater! The next Wednesday morning Boff was Weyland user feedback. Got problems with Weyland? Yes! So it was Weyland user feedback, but also Quinn in the beginning. First we talked about, in the Quinn Boff, about the plasma Weyland start, just in general, like how to start it, and also then how to debug it, so there are multiple possibilities, how to start and how to debug it, and so we showed some possibilities. And then we talked about the current progress on issues. We need to tackle and issues which are still open. For example, some people from Krita were there and they said that they need pen support, but also color management. So this is something which is good to know, or we knew it already, but seeing that they are interested in it, it motivates us to go further. And going further, Weyland is now one of the official goals, and we talked about how to organize the work on that, like on Fabricator, but also on Wiki. And so often Weyland is only talked with in regards to Quinn, but actually there are also all the applications for clients, which is important to have good support there as well. And Meben was there. We were so kind to take this part over and organize in this direction. And David Edmondson and me, we will try to cover the Quinn and Plasma part and organize there. All right. Thanks, Roman. Next up in the BOF list is the Sissetmin BOF. Sissetmin, all the things. Here's Ben. Good evening. So we had a very productive BOF, and we kind of started out by going through the list of everything we have. And the very first thing we discovered from this was that people didn't actually realize all the things we have. We have a discoverability problem. And so from there we went and looked at what do we have in terms of pointing people to the things we have, and we discovered that there are gaping holes in it, and it's inconsistent, and all those other sorts of things that go along. So we've come up with a plan now to go through and essentially replace those bits and pieces with something that's a bit more cohesive and actually covers everything. So all the things we have can be discovered and actually used by people because it would be really awesome if people actually used the full extent of the stuff we maintain because otherwise we're just wasting effort for no benefit to the community. After that we moved on to a kind of overview of the various providers we used and it was discovered that we did actually have one or two systems that are personally donated by people rather than being donated by organizations. So we are going to look at, given the status of how the KD community is doing fairly well, moving away from those so that those people are no longer essentially individually donating every month to the community without being part of a program that gets them recognition like join the game. Following on that, from that we had a discussion around api.qed.org which is held together by I think the summary was blue tack bubble gum and a bit of duct tape. We worked through some solutions that could be used to potentially replace that and essentially move us to a situation where things are a lot more easy not only for developers and other contributors to the community to maintain but also to generally from our perspective look after in the long run because the current setup isn't sustainable at all and basically is limping along in its current form. Speaking of discoverability, I discovered there were cool things going on in the nitrox community and fortunately they had a bof about it. Uri? Yeah, so this is our second academy. This is the second time that we attend this KDE event and this year we presented CNX and we presented also and partially showcased one of our new features in the distribution, which is called B-Metal. We also talked about a little bit about Synth. We think that Synth is especially useful for developers because it allows to use Docker images and basically create ISO, put double ISO images with a simple configuration using Travis CI and we also were able to present Maui Project, more updates to it. I think it's very interesting that the KDE community has accepted Maui Project as part of the projects that are under the umbrella of KDE. It's got a lot of attention and hopefully we can see more contributions to it so that we can start to use it way more in our distribution and other distributions. I also talked a little bit about images and if you weren't aware of nitrox we specifically use app images as the main way to obtain new software completely ditching the traditional package management which is why also we have CNX. CNX is basically our operating systems manager which we also release as an app image and hopefully we could present new updates to CNX, Maui Project, B-Metal and Synth whatever we come up next at Next Year's Academy. Alright, thank you, Ordi. Moving on to the next buff room, there's Quinn but you've already talked about Quinn. So let's move on to privacy. Nobody knows who ran the privacy buff. That's private. Yeah, the privacy buff was mostly about forming the team in more advance so actually we're speaking about we want to have a blog post every two months and have also an online meeting on IRC every two weeks to actually catch up and go on with the goal. And then we were discussing a lot of topics where we could improve privacy in our programs and yeah, the time was short and it was shortly before the day trip to stop and go on thinking. Thanks, Sandro. Oh, I just talked to you, didn't I? On the other side of privacy there's all the online accounts integration and I think Dan was running online accounts. Right, so we looked into what online accounts currently are and what we can do with them. We looked into all the possible services we could add into the online accounts. We looked into KPI plugins which all seem to have very advanced account configuration for each of the online services they support so this could be nicely all migrated into K-Accounts. We discussed how we can improve the current UI so it's less horrible, how we can share code with Plasma, mobile because they obviously need some account settings as well and they already have something and finally we agreed that it would be great if we could join some Megasprint again and heck there once we have more ideas. That wraps it up for Wednesday. Moving on to Thursday, I've got a whole bunch of QML workshops that ran all day. So me and Camilo and Dmitri did a session of training about QML just QML first so the very basic concepts and then moved to how to use it with Kirigami. We shown examples and made people do those very simple example Hello World applications on their computers and see what were the main problems that a new user can encounter them. That training session was kind of interesting because at the beginning there were not just KDE people that was also open to students for the university. It was advertised there. The results of that are interesting and mixed. So for all the morning there were around six people from the university, very beginner level developer. They were interested, they have taken notes for all day but kind of felt a bit intimidated by us. So that is definitely one area that we can improve on and is definitely a kind of thing that I would like we try to do on each new academy. We try to involve in kind of training session things as much as external people that we can. If one academy is at the university it's the right environment and maybe also during spring something like that may be organized and so we get better at that and we get better at getting new people. Plasma Mobile continued always. So to be fair we didn't actually use much of this buff because the workshop was still going on. But we mostly hacked on the different various hardware bits and I think most of the buff was actually Kirikami application as you can tell. Alright thanks. Moving on to the next room in the morning we had an internationalization buff run by Albert and Luigi. Yeah, it was mostly run by Luigi but he's not here so I will do it. We tackled so you know there's lots of people that want to use a web page for translations like online translation tool. We know that, we acknowledge that, we also know that there's lots of our current translators that don't want that so we need to make it work for both of the worlds. So yeah, we discussed lots of ways we can do to simplify our current workflow to make it a bit easier so it will be easier to also use from the online tool. Yeah, there's lots of work to do there. Yeah and then we also talked a bit about how it's not very easy to contribute to Qt itself which is not really our area of concern but it is because we're using translations from Qt so it's also good that we have a correctly translated Qt. I talked to Fadi this morning and he says he's willing to improve though if we put enough pressure so we need to find the correct person to talk to and make the things better. Yeah, that was mostly it. Thanks Albert. I see on the schedule a whole long workshop run by Lays on mapping KDE. Yeah, we only use the morning slot because I think that we were able to do that kind of fast. The idea of this mapping was to build a mind map about the KDE community so we could see all the subgroups, working groups, divisions, any kind of that and see where we are kind of missing some effort. So for example, one of the things that we got was that the community working group could connect more with the local working groups like Spain, Brazil and India. And so I invite you all to check out the link on the group. I will put on the both schedule to take a look at the mind maps see if we've missed something, see if we can add something. So you all can see all the structure there and know our community better so we can continue growing. Thank you. And that's how we discover what happens in KDE. All about the apps kickoff, Lydia and Jonathan. We had a session to discuss some of the definitions of our new goal all about the apps, some of the hope for outcomes and then start on all the different tasks which we'll put on a to-do board and create channels for people to communicate and create a bit of a team and hopefully take KDE's apps to a wider audience. Thank you. Bringing audiences to KDE is another topic. We have KDE, no, sorry, K itinerary extractor scripts or digging through Bouchan's inbox. Right. Bouchan desperately wanted to learn how to write K itinerary extractor scripts. So he was perfectly on time and we went through the data types you might encounter there, the tools and the APIs so that at least some people in the both managed to write a few custom extractor scripts during that hour. There's a small slide deck linked in the notes with the stuff we looked at and I think that's it. Do you want to add something? Moving on, there's a flat-packs-and-snaps thing run by young... Now I learned your name. So at the flat-pack-and-snaps booth we mostly discuss flat-pack. We discussed a few topics, one of them was KDE runtime. We currently maintain one version of the runtime with Qt 5.12 which is being updated to Qt 5.12.5 and then we are going to have another version of the runtime which is going to use Qt 5.14 and the new free-stop runtime which was released two days ago and the plan with this runtime is also that we are going to move Qt web engine to a separate extension which will improve build time a lot and the size of the runtime. But right now it's quite big and also usually fails to build in flat-hub because of the web engine and not enough memory and stuff. And then in future, because Qt 6 is going to happen, in next year we will have some experimental Qt 6 runtime with KDE Frameworks 6. So people can easily test their applications against this stuff. It should help them hopefully. Then we went through portal situation. We are actually missing some of the portals. Some are not that important but one actually is and that is printing support in Qt. So we need someone to implement it. It could be a good GSOC project but it would require like a good student for that. And then we fixed some application because we went through all the topics quite quickly. So I think David fixed Falconer on Velland. I've been looking into fixing MIME type as a solution with Ocular in Flatpak. And I guess that's it. Thanks, Jan. After lunch in the same room, we had the enterprise goal discussion regarding KDE in the enterprise. Kai? So we had a two-hour buff. The first hour we collected some feedback from some of our large deployments, like our friends in Munich. Some Kai-offused discussion because network shares are apparently a thing in companies. Some various plasma-related config lockdown, things like that. And the second hour we went through the KDE sysadvent configuration wiki, which moved wikis for some reason. The idea is to make it like a markdown kind of page, like our new HIC human interface guideline page and also use more automated scripted extraction for config keys and things like that so they don't get outdated after a week. And then also the question, how can I deploy our plasma in our company with feature X by default comes up a lot on mailing lists, so that's also something we want to improve in documentation. And rounding out the day in that particular room was Android by Nico. Android sucks, but we want to support it anyway because part of the all about the apps goal is bringing our apps to more platforms and also we want to have it serve as a kind of porting aid toward plasma mobile. And so we talked about Android. First of all, we talked about our integration with fDroid, which has been broken for quite some time now, but it should be fixed now. Next, we talked about some improvements to our Android build systems to make the APKs a bit more lightweight and fix some issues and some apps we have. Then we went through the list of our current applications that are ported to Android. Some don't even build on the binary factor at the moment, so we looked at what's the cause and made a plan to fix them. Others build but don't run fine because of various minor issues and we made a plan to fix those. And luckily some apps like itinerary, OKTrip work perfectly fine on Android. Then we looked at some of the frameworks where we need to put more work into making them good on Android that sometimes involves a bit or larger redesign to abstract the... to separate the implementation from the API. That's something that's mostly relevant for the KF6 times and for some other frameworks we need kind of Android backends. So for example, we want to make Android backends for accessing the calendar and the contacts backend stuff on Android. Then we looked at some apps indicating the ecosystem that are not yet on Android but might be useful on Android. For example, Plasma Phonebook came to mind or other apps such as Cocoa or maybe even Discover with a flat pack with a backend for Android. And then we also looked at some frameworks that are not ported to Android yet but might be useful but only one or two came to mind. Thanks, Nico. After all these exciting developments it's time for a very, very boring session which is Harold's neon fabricator cleanup. It was tremendously boring and so I don't really want to say anything about it. Other than our fabricator board is now in tip-top shape. Progress. After lunch, the KDE student programs, Kaio, and of course all the students who are here. Raise your hands, maybe. Okay, so in the KDE student programs, we could discuss and make some plans for our participation in the Google's programs and we could also make plans for the season of KDE so we could discuss how the promotion will be done and when it will be done. And then in the end, we could have a conversation with some mentors and students that were there about how their projects were and yeah, that's it. I think the students are mostly hiding over there but we should all wave to them and say thank you for your work. Rounding out the buffs in that room that today is Kabuntu with Valerie and Mary. Well, we were a very small group but we were visited by Tobias and I've already written a new story about it at kabuntu.org so that will probably be published tomorrow. And that just about wraps up the buffs for today but I'd like to remind everyone that this is Academy 2019 and 2020 is coming up. That's sort of the inevitability of the calendar and so everyone who is interested in organizing Academy in 2020 please contact the KDE Academy team or the KDE EV board. Thank you all. And we'll see you tomorrow.