 Hi, everyone. Welcome to the boss wrap-up for July 25th, our second day of boss. I'm going to be calling all of the boss organizers up one by one to tell us what they achieved today, what goalposts they've set, and what goalposts they've passed. I'm starting through 2.2, which all day was getting in the applications first, and open QA, open QA sounds like a handle to tell us so fast. So, we've spent the entire day talking about here. We've started off discussing our experience with the Ubuntu LTS as a base, which turned out somewhat favorably. People enjoy the stability that LTS offers for us as developers. It's been a bit of a challenge because naturally as our user space software progresses we need to sort of let the libraries catch up and doing that in a consistent and non-regressive manner is a bit of a tricky topic. That being said, we decided to prepare for the move to 18.4, which is going to be the next Ubuntu LTS release coming out in 2018. We've also talked about snapping, which is containerizing bundling applications into isolated instances, more or less, which should allow us to update applications in a much more regression-free environment and also in a portable sort of scenario. So, we're definitely looking at that, and we actually have active plans to do application releases as snaps moving forward. So, I don't know what the next application release is. It's something, 17.12, something like that. Yes, 17.12 should probably be entirely snap-based unless we encounter big showstoppers there. Then we talked a bit about OpenKey, looked at our current tech for OpenKey. It's working well for our primary use case, which is ISO validation for the application testing. There's still lots of stuff to be done. That's something to do. We've also looked at ARM builds, incorporating the builds of Plasma Mobile into the Neon Scope as there is a vast overlap between the two projects. I'll say that in order to conserve big resources and also management, there's a bit of activity going on in folding the two into one big project that builds 64-bit Intel architecture and ARM architecture at the same time. We've also looked a bit at how our infrastructure behaves and how Plasma releases work in the context of our infrastructure, as well as on the RAM. There are some reminders to be made, but nothing particularly interesting there. We've also looked at a bit of the user experience side. Currently, we are having trouble with actually allowing people to install additional languages after the initial installation of the system. There's a bunch of stuff that needs engineering there. Also, a big topic is driver installation, driver management, so users can install proprietary drivers rather than free drivers. If they do so, choose. Again, there are lots of engineering needed there. We've also talked about Calamaris, hopefully a future installer going to replace the root-based installer called Ubiquiti. We have gone into great detail. There's a bunch of improvements that need to be made architecturally in order to facilitate the stuff that we wanted to do, which is a more concurrency workflow that should offer quicker installation and also a configuration during the installation itself, which would be really awesome. To close out the end of the day, we've then done a GBG key signing off where we went around in circles and looked at each other's IDs, and hopefully so designed each other's keys so that should be awesome too. So, that's it from me. Yes, thank you. Point three was much more varied, interesting, I'm sure. Because it had the shine and value, it was full of fun. We're going to discuss about Calam programs, which are with coding, we've got some work for them, it's a lot of query. We discussed about how this year's program went for us, how the changes were made, who were some of our core programs, should we have helped us or not. We asked the participants and mentors for the suggestions on how to improve our, how to improve our mentoring programs and how to improve our work flow. And there were some nice suggestions and there were also some last points with which we have worked upon. So, yeah, that's pretty much it. There was a Weyland boss and Dave is going to tell us about Weyland. There was a Weyland boss, where we invited people to make out for one-to-one plasma work Weyland to test around, see what works, see what might not work. Mostly things seemed good, we found a one-to-one system to fix, found a staff, to fix a few people's principal set-ups, or to fix their very important Python and Gamerain, and we've worked on practically fixing a lot of things, including some quite difficult problems. It's kind of precious that you don't want to talk about, generally, but since we were face-to-face, it was a good moment to do so. It was mostly improving different languages. Also, we were talking about merging and a bunch of repositories that we have split at the moment, which hopefully can help get new developers at some point. That was the biggest thing, besides bearing it picky issue. We applied it in general, and the integration that we put up on global configuration. There's some challenges with all of course this configuration for plasma and system settings that we need to address. And another important setting we were introducing is like a user-assisted white kid switch that disables not only the entire data submission, but also all the infringements that you might want to make with it, because there are some good services for organizations that want to disable that for the entire network. We got the infrastructure, we worked with systems to get this deployed on KD servers, so we can actually... And finally, starting with a discussion on individual applications of the old model and of him, we'll bind KD white policy on what we want to track or what we're allowed to track, how we review dance, so kind of the code of telemetry conduct. Well, it makes sense that yes, as he came to you, ensure that this is all up to our entire systems. Yes, that's basically it. That's the future for the microplasma here on Plasma Desktop. We also discussed some of the complexities of the background issue that Microsoft is facing. And we discussed on some of the cool skills that we could add to Microsoft like screenshots and make a generic media player still. Also, in the discussion was a bit about the privacy issue, so creating a message that belongs to users that it uses Google STT. So yeah, that's about it. Thank you. We'll get it together at the end of today. Yeah, okay. So we talked today about some of the short-term, medium-term and long-term vision that we want to accomplish for Plasma. And obviously, Plasma has a graphic environment so we have to think about this quite often. And so we developed some goals and some things that we have to do going forward that our teams want to go with. So expect a lot of change and a lot of feeling too comfortable is not going to happen. We're going to ask you to put up with us a lot and so we hope for your cooperation. Rather than that, thank you. We mostly discussed about how we need to learn about what the people who actually bought the device need to know more about the kind of companies that would be interested in doing an experience such as that we need to continue talking to people, but maybe there are smaller manufacturers that would be interested in the whole point of us thinking about it is whether we should continue doing this or not. We've been discussing about whether we should actually get group of hardware manufacturers or acceptors together or much like our advisory board, we should discuss it again. But I think that the conclusion is more or less that it would be a good idea to do it again at some point maybe not yet. There's also some places where we could be improving making sure that the hardware is exactly what we want and to make sure that processes that the company has in place are up to our expectations but we can do that, especially because like I said, we don't want to do it now really again, but maybe in a year or maybe five years. But then there's improvement and we'll do that and where it goes. Conqueror is dead. Long live Conqueror. You might want to be more detailed than that. Basically I've been reviving a little bit the effort of Conqueror lately, making it work with Web Engine and the idea initially for this both was to figure out what we want out of Conqueror. And then I learned that there is an existing Qt Web Engine based browser called Capsula, which is actually quite polished as a lot of stuff and my temptation now is to simply drop Conqueror completely and use Capsula and actually we talked to the Capsula maintainer on IRC so right now it's a GitHub project and he's open to the idea of moving that to the community and we also jokingly suggested to change the name actually sex to Conqueror okay with the idea if we're okay with it that can just relax but before you can relax we have Dan and Hindi Bob right so we discussed some of the tasks that we are currently working on and we are planning to work in the future we cleaned up our static cleanup, our wiki pages which are horribly outdated. We already talked about our effort to get contact for windows built, hopefully that will get soon folder made KDPim work on Wayland so we just need to fix the lines and we can work on Wayland now we also focused on our developer story so we want to make it as easy as possible for new developers to start working on KDPim it's not easy given the amount of repositories and the dependencies between them so we want to make their lives easier and hopefully attract new users to think that we will be also merging streaming the exchange support which currently is done by some guide github so we will be merging into KDPim runtime so that all our users will have a chance to use Microsoft Exchange we also finalized the KML user serving and we'll be publishing it very very soon and we talked about the plans for the Randa Spray in September so it will be in the morning soon and Thomas can tell us something about the main topics that we the main topic that we had was of what would need to be done in order for being portable to Kirigami so that we can then also have it on mobile the name discussion also came up and we came to the conclusion that we maybe should brainstorm on a new name which the design group is going to do and then we discussed a bit about things like should we to the play integrating services like Spotify and also currently it does play from YouTube and you can live from YouTube and then we discussed because of the legal implications and how we could still use YouTube and it would not be a legal gray area because we want the player to be back into all distributions which we also talked a bit about how it could be integrated with Mycroft and about how debuts could be used to for example offer a KRunner plugin so that you could from KRunner directly start playing music Assistant Scarlett to come forward those of you who are filming the Academy User Satisfaction Survey and with Levin they named you in a previous level the years are completely random QML application I'm sure and the button will be pressed to reveal the winner and the winner is Franklin Wang who wants to rock with Casbot catch the bus and be quick