 Okay, most urgent, we need two volunteers. Yeah, what are we supposed to do? Is this a big project? Is this a small project? Take notes. Send them to Danny and Mova, and they will be seen weekly. I would suggest making a copy. Yeah, I was about to take a copy. Whatever you like. I do not care. As long as somebody takes a note. You can take UI or whatever you want. Why there is no XMPP? Use whatever you like. Who is volunteering? You? No? Yes? I can volunteer. Actor. And somebody... What were you like? And somebody who is in the INC, and the room general, and it just works whether there is anyone who likes to comment or has a question to the audience. Maybe it's not that I want to... Can we just copy the latest from Dolby to LSE? No, it's about taking questions now. If somebody is now in the INC and wants to ask something, so somebody who is right now in LSE... It's supposed to be LSE. LSE, yeah. Are you the one who is naming the LSE? Yeah, that's LSE. Okay. Okay, thank you. Okay, we have a mobile of Lastia and Morial, which was amazingly well visited by the people, and we had a really brief discussion, and it turned out that as far as I can say, there are three directions where people think about dead-end mobile devices, and all of them have advantages, disadvantages. There is one direction, mainly using hardware that works well with Stepian. So, for example, open hardware or hardware that is not too much locked down. That is like the Libre M5, we will see later more of that, or the Pyra handheld or the GPD pocket, which you see right now, this is running on the GPD pocket, this slide. I will show it to you, which is also a kind of mobile device and so on. So, this is hardware either made for use with free operating systems or at least not locked on. The disadvantages of this is, of course, those devices are very few and they are expensive. So, yeah, we are excluding most people in the world with just the surprise tech. Then there is the idea of putting dead-end on normal mobile devices, on Android devices, which there are billions of, but it's technically hard because they're locked down, and my personal opinion is it gets worse every year. So, but if we would succeed with it, that would be also very nice. Most of the time it wouldn't work at all or you have to stay with the old common. And the third idea that came up last year was to enhance the scope of Debian to make a kind of Debian Android. Not Android GNU, Linux, Android, non-GNU, Debian, non-GNU, Android, I don't know. Also a very nice idea, but also has drawbacks like we would have to follow one single company policy because otherwise you would go away from mainstream Android and it wouldn't make sense anymore to do this at all. So, these are the three directions. As far as I know, the only thing that improved since last year was the first one with special devices. And we had on the mailing list comments that nobody really worked further with Debian work on Android devices. There was also a remark about the Germany that it really does not run Debian in a meaningful way. So, that is what I would like to start with and maybe we can already start with your slides if you like. So, there is a presentation about the progress of tourism. So, what did you guys learn from the open moco experience? Any lessons learned? Last year, I think most people did not want to talk too much about it because there are so many hurt feelings. But, yeah, lesson learned. There are many different opinions about this. I can't really repeat all that. There were some things, but it was much too early. There was a lot of politics going on. There was also the Nokia disaster with the N72900 and so on. Maybe somebody else could comment. No, just adding the canonical phone also was discontinued. Maybe we should have some lessons learned from that. Have some retrospective. Are there any news about the Nio 900? The Nio 900. The Nio 900. How do you know the crypto currency, Nio? I asked the Nio 900 guys about this before Tocon. I mentioned one of them is working on the second prototype and the other two people are affected by health issues. By the way, the slides are running on this small machine which practically is also mobile-wise. It's a PC. It's called GPD Pocket. It's a normal PC and 64 cores, 8-bit of RAM. So installing Debian on it is quite easy. Debian installation is relatively easy on this one. No arm stuff and so on. So we have already some mobile devices running at the end. Excuse me. Do you have any documentation for installing Debian on the GPD? Because I have you moon too. Okay, I didn't see. Because there is a many patch on the kernel and so on. Okay, thank you. You should not have any X dependencies to be used in the case for apps to be mobile-oriented. The old environment that's already been set up to have a lot of disk encryption, mainline stable kernel, because that's the main point. But we wanted to get it based on all the action we want without the mainline and support. So we just go with the mainline. And we are focusing on base apps because it's possible to have a big one. So it's like holding a surround that it hasn't been called. That's going to change so probably. They set their own CI. It's enforced only. What's left for QRS is to build raw images which are the ISO images. What's left need to move packages being built by the team or when they care, which is a raw infrastructure for QRS. It's great to fly. Mathias Kuhn, who is the exit. Yeah, the right image format. Yes, raw image instead of vice. So it needs complete transition to QRS. There's not that much as long as based on your own images and outstanding issues. Okay. Also in Q-Work, obviously that's very important when you have a handheld device. Not so far in good methods, for the real and support, can be written in partial upstreams. We don't Q-Work it being accepted. And we are the rules. We are the rules in Q-Work. And the end result is a pretty good, well-balanced setup for technology by the guy who is doing SU AID. That's like I3, the real version of I3. The OS key is being packaging SU AID to build boards. What's the additional chased need to be upstream. Some in progress. Some is to be done. I think recently we've got some new inputs changes in connection with QRS. We had more than 50 demo keyboard but the proper pretty new the other four that typically have custom layouts because of my pre-frozen build on, they had that interesting input for time on their phone with no Asian input at release though, unless we're gonna be with health, and so I encourage all the people to take note of the fault for the Western. So they did a lot of badging of real roots at the Western, function errors, many irritation, and I also wanted to go to full screen so we were actually working out it's a big six image barrier to actually test how the phone updated that can come on a daily basis at this point. Or actually a board was merged, a combata has been added, and bringing up a full-grown session is the point of the team. What's left, attached integration board, so we're gonna, there's no touch work you can't use touching or touch device when you run the image. Once we switch the gas, we attach some continuous might be submitted for nice and again, a link to the policy through. At the end of the year's interest, the Lit-Handy Library, which is written by our leader, Winter, it's a used, developed user interface for mobile devices with GTK, and I think Peter recently uploaded with handy tool that we also added also that I can play with it. Then I went to expand the column, developed for call apps and I was using a last name, what's left for us, we just need to be added, like for continuous gestions and board to library GTK. Plus four, because GTK3, it's not really ready for mobile and it needs a lot of mobile work to be in a shape. I'll send issues again, we'll link to it. At the ultimate environment, that's so far too, how the machine has been made available to the community to develop on board before their board ship and their board's full ship, I think by the end of August or September. Ability to cross build ARM-5X on an x86-4 station has been added and implemented into GNOME Builder to support the Libre 5 project. So yeah, we have a lot of code push than a great absent relation with GNOME Builder, which is gonna be needed to actually make life easier for our developers on the Libre 5. Yours and Flaplike Go Stories has been set up for storing apps, flatpacks for the dead board of phone, what's left, we can add some for the Libre 4 and of course for GTK4, and some relevant pages could be moved out to be handy and put into GTK4. Still need better recommendations, examples to guide developers to make it for the deaf, there are some of the main conditions, there are two free example apps that we can find inside the Libre Candy and I think some music player who recently was born at the Libre Candy, which was fantastic. The application I've developed for Plasma is also needed. So yeah, we have a collaboration with Plasma, obviously it was seen through the phone campaign and Plasma had their own Plasma moment. This encryption has done so far in a ton of general security discussions usually around the Libre key and smart card. The Libre key is made with collaboration with the Mitro key vehicle, I think the German vendor and the other making the keys to UB keys. Once left, they can investigate and implement all this encryption in US hardware security device, so that's probably a Libre key to unlock the encryption key, but at release it's probably gonna start with only passwords, that's what you want actually from a phone. You'll see for them, more firmware uploaded for more with wood, to measure some of the theorem of loss, that for, you think of that, which is most recent one, is now booting with the EM crap, some, and we have got some major subsystem board, Serial, EM, NC, Ethernet, SDS, the IOI, the IOI to C, the NIC, and that, so this is gonna be by far the most intense work to get it on because we're gonna use IMX8, which is just recently released, but we're not alone in this. German based company, Megatronix, is doing a lot of mainlining, and while I think they're not gonna be able to catch up with 480 and 490 interaction, we already have changes, it's most likely gonna be a kernel 5.0 or 420, what are the links to this to call it, and that's gonna be most likely the kernel is gonna be used on the graph 5. But I want to put the door in so you can see. Yeah, so anybody lucky, you're gonna see at the end of the slideshows, all the main list and all the channels you can join and ask questions, but they also have inside, Debbie and the relevant person for the point team, and that's Gido Ginter, along with Debbie and the rest of her. Yeah, so base applications through, is gonna focus on few applications and the release date, because as said, like trying to hunt down Google Play Store is gonna be impossible and will be used to be tried. Calls, obviously, the most important part of the phone. That's why we can establish an end phone calls without having, because current phones don't support it. Use the live handy dialer, changes have to be much upstream for the current phone drive, all to be able to ship dev kits and phones with a different phone for the current test demand. Well, I slept ringtones called Instagram integration, no contact, and there's an old phone screen, so I lost the left. I'll send the issues in again here. We chose to go with, I'd be finding an omelet for the browser, which is easier because it's less cold and we already have upstream relations, we're already doing changes, porting, and I don't, I think we approach on-surface Firefox and they're not too really interested in the moment to actually port Firefox, so nicely built. So, with that so far, that using these changes have been more downstream to improve the usability of small screens. And what's left, finishing that in window, have many more with upstream to fix the great, the issues, the great impact, it's a bit more of a no-bam, we can actually test no-bam on the virtual machine, so it was just non-contacts, not much. In the real context, we've calls in Kiri, phone team decided to go with Kiri as a email provider for the Libre Monolee State, I think that most outstanding issue for the Kiri is that it currently doesn't have GBG support, but I think it's gonna be implemented before the release. You know, settings, so, yeah, we have some planning, small-card discussion with AppSync, Qualdeck, if anybody was at Qualdeck, they had a chance to actually talk to the phone team, I think most, if not all, of the phone team was there. What's left, they had the ability to set up a SIM card, they had settings for smart card, a different key. Then so far, made mobile friends, they must let the board run through now because they're currently using the Western tournament, or hopefully they can afford tactics. Fractal, so we have a collaboration with Matrix People, which was our main point of how to use forward messaging, calling people, and Fractal is the GTK app client for the Matrix, and there was a Fractal AppS in the main, a tourism and Fractal that was put together, and there's an effort to implement the end-to-end encryption in Fractal's launch, and Fractal actually hired Fractal, developer to work exclusively in that, and he stopped doing it tomorrow. What's left, they investigated to come up with a plan forward and implement the end-to-end encryption in Fractal, and do the messages. Not so far, POC featured with Fractal backhand to make a lot of protocols, as well as SMS text and sender size messages in more than a year. What's left, finalized with Fractal planning and forwarding results in the phase, and we can see the outstanding issues. Why Lit Purple? Yeah, why Lit Purple? Nobody knows. Yeah, that's the phone team who made the decision on that, I'm not sure why. So, can you explain a little bit about the problem with Lit Purple? I mean, Lit Purple. Not really. I said I'm not part of the phone team, so I don't know who they were seeing. As far as I understand, Lit Purple is basically, if you ever use the Pitching, it is the Lit Purple is the backend library of Pitching. And Lit Purple actually supports SMS messages, and sometimes, if I remember correctly, they even support the phone calls, actually. Again, there is a camera done so far, not the one that's left to investigate cheesy, but how I've chosen is to be made mobile friendly to it in the image integrated with the camera component. The thing is, at least as far as I know from the phone team that cheese doesn't need to be either really adopted, of course, it's much different to use the phone cameras than the latter cameras. Another long calendar done so far through the image and then make it mobile friendly, shouldn't be too hard, I think. And then there's LibreFind team, which is, I guess, what's most interesting to you, instead of listening to me. So, you see the Indian Blists, public archives, you can join them all, and I guess the most easy way would be to join the Matrix channels. Community LibreFind is the main point for everyone to end up, if you want to discuss phone team, the phone team community purists is where I am and Matiasi is another purist of all of us. Community purist is... Purism, try to make services that are all ethical, so we don't end up, the end goal of purist is to actually have integrated unified solutions for social networking, such as Mastodon, diaspora, you have your own email client, to have the next log as against, like, Google this and those kind of things. So basically giving all alternatives to current proprietary and community general is, of course, the general talk. And I think that would be all. Thank you for that part of the phone team, so I really don't know that much, and the status updates are basically gathering all the points that we post on the purism blog posts, so anybody wants to read more details, there's a lot of blog posts around the phone team. One question, why do you create a new build system? What was there that you could not use existing ones, or what drove you to create this, you know, called LaNikia, maybe developers here, he can. So LaNikia is not a build system, it's more something like Launchpad, where you can, which manages the packages that are coming into the archive, which is able to distribute jobs to workers to build images when there are new packages that are relevant and to do all kinds of these things. And to kick off transitions in case there is a transition going on or something else is detected and to communicate with RSE channels and to have some kind of integrated database which holds all the information on the system. Like going into detail would actually be out of scope for this session, but we can talk about it later a bit. But in general, it's very much comparable to something like Launchpad that Ubuntu uses, but without the bug tracking and without the project management approach that is also in Launchpad. And yeah, that's basically it. It's like since last year, I follow a little bit the development of the Pyro handheld. Last year I had a prototype with me. This time I asked the developers again whether I can have one, but they didn't respond at all, but to my request, but I follow their forums and so on, because it was crowdfunding and they have 400 euro from me, so I really want that they are successful. And for those who don't know, the Pyra will be a gaming console. Practically it's an ARM-based mini computer with four USB ports, two SD ports, lots and so on. And it comes with Debian by default. My personal hope is that they will release first 500 devices later this year. And I'm at the second batch, or the second 500 of the Pyra. It also has a touch screen, so I'm pretty sure that the current Debian UI software will run really bad on it, but the software made by tourism will be really cool for it. So probably they will have some advice, but we will have to wait for the software by tourism to make it really work. And also I follow a little bit the zero form because I have my board at home. There's not so much progress. They evolved a little bit with the hardware. The new USB port is not only for charging, but before that you came up with a serial connection on it, which is nice for hacking. I believe you may have been going to the U-Boot with the USB now, but I don't have it now. So I do not know how it's going on. And they also had some progress on their Python-based UI library. The zero phone is really a little bit different. They don't have a casing right now, and it has a very small display, 6GB, I don't know what pixel or whatever. For me, with my age, it's already unreadable, so I probably will never really use it. But last time I had the prototype with me, and you remember maybe you were sent more real that we were able to connect the Wi-Fi and that you could add to install something. It's around not at the end, but Rasmian. It's a Raspberry Pi zero-based, down-phone style. It's a smartphone because it runs the notes, but it's a down-phone because it has only back-and-white small display, and the idea is that you can make some phone calls, there's some S and whatever to install that no graphical interface. Does anybody know more about other devices with the microphone? Nobody knows? Nobody knows, guys? That's the Gemini VDA. This is the microphone. This is Rasmian, which is kind of broken, but it's on the front of the Android and you can put it in as well. There's also the Plasma Mobile app for it. If you don't forget about it, and Plasma Mobile already has the adaptive user interface. We have here Kirigami project. They also released the image so we can play with it, and on the first day I actually saw the Nexus 411 Plasma Mobile, so it's kind of half-finished project, but it's currently much further forward compared to the example of the Kirigami app, their code base is much, much larger. So anybody who wants to play with Plasma Mobile? Does anybody know about progress or non-progress of the Helium project? We talked about that last year. I think it's an adaptor library between Linux user land and proprietary drivers or something like that. The live hubris is a library that's used for having Linux run basically on Android devices and what's good about projects such as Linux 5 is that we just trash the entire library away. So Helium is actually still very much alive. Even closer, okay. So Helium is still going on. It's basically a combination of different lower level, different middleware pieces that were just packaged together with, as far as I know, an Ubuntu base, and I think it's very much maintained by the KDE people still and by some other stakeholders, but I don't have any deep insight into it. I think PostmarketOS is also maybe using it, but yeah, I think it's still alive. At some point, it's running Android apps. There's Shashik. It was developed at this point a year ago, but there's also the Endbox project, which is actually not. And it's quite heavy, I think, for the phone usage, but Purism is actually pushing the Endbox into Debian, so we sure already have pieces in Debian. Chris Landland, he was working on it and he's now actually supportive of the developer who's actually doing the packaging of Endbox. So Endbox can run Android apps, but it's still quite heavy for the phone usage. It adds about progress or non-progress of mobile apps. Already a lot, well, last year we didn't know about Purism planning their Libran 5 because they announced it one week after that pump. It was a really nice surprise then to get it, and I immediately put some money into it. And I think they got two and a half million, right? So more than double than it was planned to start. Yeah, yeah, yeah. Okay, 2.1, so really nice success. So I think that a lot of people are already interested in having a phone that does not run Android like I already have. So a very small market niche that's probably picking up. Okay, what else do people like to discuss? So no, I've been... Use the mic. Use the mic. Use the mic. I think one of the really interesting projects that's come out in the past year is the Post Market OS. They're basically an Alpine Linux derivative and they're working on mainlining a whole bunch of Android devices and they're trying to basically be what Debian could have been if we'd focused on that sort of thing. And so I think it's worth looking at what they're doing if you're not familiar with it already. I have a question about the Purism Libran 5 hardware. How bad is the firmware blob situation? Oh yeah, we're down to one mic now. I'm not very precise on this part because not for the team but I think they have the modem baseband, something blob is going to be needed but they're actually separating it from the main CPU and there was a blog post from Bob Hamm I think about it so you can check into details more on the Purism blog. Thanks. I just realized it's not Debian but nobody's mentioned Replicant yet which is the free version of Android that has the non-free drivers removed. And just a quick update on that is that they're having, they could really use some help because there's a number, there's one very severe bug that's been open for quite a while that prevents a lot of SIM cards from being recognized and another issue is that with the deprecation of the 3G network basically none of the supported devices will work within a pretty short period of time because no currently supported devices have 4G or LTE. Okay, officially we are out of time but we can probably have some minutes more. One thing we said last year, if I remember correctly, we wanted to use a tag in the backtracking system for mobile related bugs. Remember, we talked about that and I think I entered two bugs also with the tag if I remember correctly but I did not even check whether that went on or something. I need to recheck and I forgot about it until now. I think we agreed on having that so that one can easily find mobile related bugs in our BTS that can be from kernel to user interface issues. Now with this small PC here, I find a lot of issues with UIs that are pretty horrible on the small screen, especially nowadays where a lot of small screens have a high resolution. That's a really bad thing for most of classical UIs. Of course, in mobile we have to think about both directions, both a small display with a low resolution and also with a high resolution. Of course, it should work in any case and currently I believe most UIs work in no case. Probably we need to file a lot of bugs against applications. Also, it would be worthwhile to mention the OsmoCom project, which is a project that's actually doing at least trying to do a lot of implementations, making code for what's needed for mobile communication like GSM and other things. We are focusing here completely on devices. There is also... There was some work to bring Debian on ebook readers, but I read something about it, but I forgot details. That are mobile devices too, even if they have no mobile network or something, but if there's anybody here who knows more about it... No, okay. Is there anything we as Debian should do, must do where we can work as a project on mobile? We have the mailing list, everybody knows that. We have the ISC channel, everybody knows that, Debian mobile. Yeah, that's it. I have a bad idea. I don't have any relationship about the iOS Joebreak project stuff. Okay, just interesting fact, because they are also used in DPKG. Yeah, the iOS is CDR. They use DPKG. Yeah, funny. Okay, then that's it for this year, and let's look about the program. We will all have a library M5 in our pocket, right? The pyre will be out even before. So our pockets will be completely out there by different devices. Thank you.