[02:21] <arraybolt3[m]> Hey, finally back.
[02:22] <arraybolt3[m]> My take on Falkon - please, no. Snap-ified Firefox is better. For all the talk about Falkon being lightweight, it sure ain't on my systems. It's slow. Firefox is much snappier in my experience. Also, Falkon used to have one or more memory leaks - is that still a problem?
[02:24] <kc2bez[m]> arraybolt3[m]: It has seen many improvements. I see regular releases from them. I am not sure when you tried it last. 
[02:25] <arraybolt3[m]> Last I tried it was in a VM with KaOS. It was awful.
[02:25] <arraybolt3[m]> And that was fairly recently.
[02:25] <arraybolt3[m]> (Like, a couple months ago or so.)
[02:25] <arraybolt3[m]> Does it just not like VMs?
[02:25] <kc2bez[m]> Not sure.
[02:26] <kc2bez[m]> Probably best to give it a fair try on Lubuntu.
 I also have wanted to like falkon for a while but found myself disappointed as some sites tend not to work on it and have just been using the snap version of firefox
[02:27] <arraybolt3[m]> OK. I'll try it on bare metal and see how it acts. (And KaOS was somewhat slow in a VM as a whole, so maybe it was the fault of the OS.)
[02:27] <kc2bez[m]> lubot: That is unfortunate. 
[02:29] <arraybolt3[m]> Another one we might take a look at (if it's still maintained) is Midori. It's Chromium based, so it should have good website compatibility if I'm not mistaken.
[02:30] <guiverc> I'll aim to load falkon on a live session (daily) & explore & see how it is for what I'd do with it (~today; i recall some web site issues long ago when it was on our dailies pre return to firefox long ago in cosmic? disco? i forget) .. falkon is Qt5 which I think we should use over any GTK one
[02:31] <arraybolt3[m]> guiverc: Good point about Qt vs GTK. And Firefox is the only app that we ship as a Snap, right? Getting rid of Firefox would let us get rid of Snap, which, like someone pointed out, would give us positive attention from bloggers. Plus the built-in adblocking helps add a layer of security, which sorta makes up for the loss of security by using an unsnapped browser.
 "Another one we might take a look..." <- Midori doesn't appear in Kinetic. Looks like the last time it saw an update was Focal. :(
[02:36] <arraybolt3[m]> kc2bez[m]: Bah. OK, then I guess it's Falkon or Firefox. Or Lynx. We could try Lynx. (jk)
[02:37] <kc2bez[m]> Or links...
[02:37] <kc2bez[m]> w3m maybe 
[02:38] <arraybolt3[m]> If we want really lightweight, let's just go with curl. People can parse the Javascript in their heads.
[02:45] <arraybolt3[m]> Another thing we'll need to test with Falkon is how well it works (or doesn't work) with ARM. If we switch Web browsers, and then Falkon isn't happy with ARM, we're gonna make all our Raspberry Pi users mad.
 "guiverc: Good point about Qt..." <- Let me add a little bit of history here that some people may or may not know...
[03:20] <tsimonq2> Back when snapd was first introduced, I was absolutely against including that by default in Lubuntu. This was towards the beginning of my tenure as Release Manager 
[03:21] <tsimonq2> I attended a Technical Board meeting in which the classic members of the Ubuntu Foundations Team and I discussed the rationale for this decision
[03:22] <tsimonq2> Their argument does have merit, that Canonical has invested a significant amount of time into developing this platform. I was unwilling to budge until some of the major issues were fixed 
[03:23] <tsimonq2> Fast forward to today, I think some of the core issues have at least been addressed, but there are still some issues. I'm definitely not opposed to shipping snapd by default to make it easier for the user to choose their software
[03:23] <tsimonq2> I just think we should take a serious look at which applications we ship as a snap and closely monitor their footprint. Firefox seems to fail all intuitive tests 
[03:24] <tsimonq2> I understand that it has to do with unpacking a squashfs and setting up revisions with their respective mounts but what I don't understand is why it takes a fraction of the time for Flatpak and AppImage to open the same exact codebase but with different packaging 
[03:25] <tsimonq2> As always, I think we should do what is best for the user. I don't think a browser taking 30-60 seconds to load on a brand new computer fits under that criteria, but we also have to be certain that Falkon is an upgrade, not a regression 
[03:26] <tsimonq2> We should also continue to evaluate our options. If there's a compelling reason to switch default applications, we should know the advantages and disadvantages before we make the switch 

[04:20] <arraybolt3[m]> Simon Quigley: For me, I don't care how much time or money someone invested into a platform. I care if it works. My experience with Snap has been mostly bad, except for Firefox, and like you mention, Firefox takes just that little bit too long to load. I've several times thought, "Hey, did my button click not register or something?", and then it popped open. So while I fight for Snap when it comes to security, secretly, I'd love
[04:20] <arraybolt3[m]> to see it be gone.
[04:20] <arraybolt3[m]> Until it's fixed, anyway.
[04:21] <arraybolt3[m]> As for Falkon, my problem with it is that it has a somewhat similar problem to the Snap Firefox - the opening page takes looooong to load. On Firefox, the opening page is there right from the get-go whenever the window finally pops open. But Falkon, the window snaps onto the screen right quick, but the thing feels laggy.
[04:22] <arraybolt3[m]> Plus, the default search engine is Duck Duck Go, which supposedly has privacy benefits, but in my experience, it's quite a bit slower than Google.
[04:23] <arraybolt3[m]> Now, I've not given Falkon a fair test recently yet, so these problems might have been fixed, but if not, I think Falkon will slow a user down worse than Firefox. I can live with a sluggish start and then fast performance thereafter. I don't like a fast start with subsequent crummy performance.
 "Might have to double check..." <- What's the standalone Qt file? I do want to try Qt 6, since I just got a comment on the Qt bug report suggesting that I do that (I believe).
 "We should also continue to..." <- This is exactly the reason I mentioned it.
[10:15] <kc2bez[m]> I knew the switch to snapped Firefox was going to happen well in advance. When main Ubuntu switched the end of cycle before we had reservations that it was too close and the issues were rehashed. It was decided that the flavors would all switch the next cycle (the LTS). A cycle later and the issues are still being worked on. Some are solved, many don't impact us. We don't have gnome extensions and we don't have the nifty plasma browser
[10:15] <kc2bez[m]> integration. Neither of which work with the snap. 
[10:19] <kc2bez[m]> The start time might not be a big deal to us but it is to some and certainly impacts lower end machines more. I don't see that ever going away for the bigger applications unless they start doing some caching in idle time or something. The compression algorithm can only take you so far. Flatpak and appimage don't have that problem because they don't compress anything. They trade the disk footprint for the speed. 
 "The start time might not be a..." <- Good points - again the users can always choose to install Firefox if they  wish..I personally prefer Firefox for my use but having Falkon as default np fo me
[13:59] <LeoK[m]> I am installing Falkon on a test machine via "Discover" and it says it is a snap package i.e distributed by snap...
[14:14] <kc2bez[m]> Weird, maybe snap is selected as the preferred source? 
[14:16] <LeoK[m]> kc2bez[m]: Could be ..ran quickly and surprised how much it is like Firefox...
[14:17] <LeoK[m]> Might even be a convert..running youtube videos about 250K less memory
[14:20] <LeoK[m]> Yes snap preferred by default in Discover settings 
[14:23] <kc2bez[m]> You should be able to toggle that to look at the archive first.
[14:34] <LeoK[m]> Unable to change the default (shaded out) in Discover via graphic interface
 Need to retest this in a clean install (re @lubuntu_bot: (irc) <kc2bez[m]> You should be able to toggle that to look at the archive first.)
[14:41] <kc2bez[m]> That makes sense 
 Sensible now and then...mostly then..
 Fresh install - unable to disable snap as a source ..it is shaded out though not default (the make default button is available)
 At the same time the user can change all the other source setting in "Discover"
[14:56] <LeoK[m]> And of course np installing falkon via cl
[14:57] <kc2bez[m]> That is a strange one. Seems like a bug?
[14:58] <LeoK[m]> Yes I want to wait for next daily (as we have many updates pending) and will then file a bug if need be
[15:01] <kc2bez[m]> Sounds good. FWIW I am able to change it in jammy
[15:06] <LeoK[m]> kc2bez[m]: can unselect snap?
[15:07] <kc2bez[m]> Yes. Basically selecting a different source as default unselects snap.
[15:10]  * kc2bez[m] uploaded an image: (92KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/ogSulaHqzTNPRtLIMJZJMTRw/Screenshot%20from%202022-06-06%2011-09-46.png >
[15:11]  * kc2bez[m] uploaded an image: (92KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/vPvFhNjcZEeOxgYyeLgqxMMh/Screenshot%20from%202022-06-06%2011-09-46.png >
[15:11] <LeoK[m]> yes on same page - however falkon always appears as snap even in jammy
[15:11] <kc2bez[m]> ah, I see
[15:12] <LeoK[m]> And i cannot deselect snap in either version jammy or kinetic
[15:12]  * kc2bez[m] uploaded an image: (146KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/xgjyAqQLREusjnAEZAWMcYWN/Screenshot%20from%202022-06-06%2011-12-26.png >
[15:14]  * LeoK[m] uploaded an image: (132KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/pBJMgdyPUShfzQhdsVGKtYoL/screen.png >
[15:15] <kc2bez[m]> I wonder if those updates are holding you up. It might need to update the apt cache.
[15:15] <kc2bez[m]> That is strange though.
[15:15] <LeoK[m]> updating..
[15:19] <LeoK[m]> strange indeed..
[15:20]  * LeoK[m] uploaded an image: (84KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/MzNWSScwBYNqjSsPrDhbIioM/screen2.png >
[15:20] <LeoK[m]> âfter update jammy
[15:21] <LeoK[m]> and here from discover settings in jammy
[15:22]  * LeoK[m] uploaded an image: (182KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/YpZxriKYUfQpQqVfrshxaXIb/screen3.png >
[15:22] <LeoK[m]> as you can see i cannot deselect snap as an option
[15:23] <kc2bez[m]> The archive is the selected source in your screenshot. If you click on falkon after your search what do you see?
[15:24] <kc2bez[m]> I don't think you can disable snap completely from there, you have to remove snapd to do that I think.
[15:25] <LeoK[m]> In jammy as in above screen shot (from the archive) but not in kinetic
[15:26] <LeoK[m]> Ok Dan ..will check this better in Kinetic after next daily iso..think jammy is no problem
[15:26] <kc2bez[m]> Sounds good. I don't have a kinetic VM handy but I will keep an eye out too.
[15:27] <LeoK[m]> thanks Dan..
[15:27] <kc2bez[m]> Thanks to you too!
[16:23] <tsimonq2> Good morning everyone!
[16:23] <LeoK[m]> Yes good afternoon!
[16:23] <tsimonq2> Good news :)
[16:23] <tsimonq2> https://launchpad.net/ubuntu/+source/xdg-desktop-portal-lxqt/0.2.0-0ubuntu1
[16:23] <tsimonq2> https://wiki.ubuntu.com/ProposedMigration
[16:24] <tsimonq2> That's a bunch of useful info on the process, but ISOs should be building today or tomorrow.
[16:24] <tsimonq2> If anyone else sees a different reason why it's stuck, let me know
[16:24] <LeoK[m]> Nice
[16:24] <kc2bez[m]> I will keep an eye on it.
[16:25] <tsimonq2> Generated: 2022.06.06 15:31:20 +0000
[16:25] <tsimonq2> $ date -u
[16:25] <tsimonq2> Mon Jun  6 04:25:16 PM UTC 2022
[16:25] <tsimonq2> so should be running soon I'd hope?
[16:26] <kc2bez[m]> This is pretty close to the time it normally shoots out.
[16:26] <LeoK[m]> usually finished around 17:15 utc give or take a few min.
[16:29] <tsimonq2> Sounds good.
[16:29] <tsimonq2> I'd honestly be surprised if xdg-desktop-portal-lxqt is a candidate but it doesn't all migrate
[16:30] <tsimonq2> Btw if you guys see my keyboard go crazy soon, we have two new members of the Quigley family :)
[16:31] <LeoK[m]> Great news Simon!
[16:31] <tsimonq2> Not children, yet :)
[16:31] <tsimonq2> Just some cute kittens
[16:32] <LeoK[m]> Keep them off your keyboard
[16:33]  * tsimonq2 uploaded an image: (174KiB) < https://libera.ems.host/_matrix/media/r0/download/linuxdelta.com/oZaqiFvMGnBaUJUTCBLfJyDp/Snapchat-1263402176.jpg >
[16:33] <tsimonq2> Juno and Milo :)
[16:33] <tsimonq2> LeoK[m]: Trying... lmao
[16:35] <tsimonq2> 8 weeks old and litter trained, got them for free from my uncle :)
[16:35] <tsimonq2> anyway
[16:35] <tsimonq2> </cat rant>
[16:35] <tsimonq2> :)
[16:55] <LeoK[m]> ISO build failed 
[16:55] <tsimonq2> Still all needs to migrate and settle down
[16:56] <kc2bez[m]> Yup, waiting on britney is painful sometimes.
[16:56] <LeoK[m]> Into each life a little rain must fall..
[17:44] <tsimonq2> https://discourse.lubuntu.me/t/calamares-3-3-early-preview-please-test/3382
[17:45] <tsimonq2> Leo K guiverc Dan Simmons arraybolt3 ^^^^^^^^^^
[17:47] <kc2bez[m]> Nice, I will give it a whirl when I can.
[18:39] <arraybolt3[m]> Simon Quigley: Got it. Is it in the daily or -proposed?
[18:44] <kc2bez[m]> arraybolt3[m]: In a ppa
[18:44] <tsimonq2> -proposed ;)
[18:45] <kc2bez[m]> Which thing? :P
[18:48] <kc2bez[m]> Hah, it is in proposed. Life on the edge ;)
[18:55] <arraybolt3[m]> The Calamares installer, I mean. Proposed?
[18:56] <tsimonq2> Yeah
 "Hah, it is in proposed. Life..." <- ;)
[18:56] <arraybolt3[m]> Simon Quigley: Congratulations on your new kittens. Consider unplugging your keyboard while afk - some of the most interesting screens my computer has ever made happened thanks to a keyboard sleeping kitty.
[18:56] <arraybolt3[m]> (Like, did you know that the KDE screen locker can break? Me neither, until Cloudy slept on my keyboard.)
[18:58] <tsimonq2> arraybolt3[m]: Thanks. Yeah, laptop will be shut lol 
[18:59] <arraybolt3[m]> Alright, I think I've got a good testing checklist made - let me know if I missed anything. https://pastebin.com/tECgcHVY
[19:00] <kc2bez[m]> Zfs probably isn't possible 
[19:01] <arraybolt3[m]> Alright, then some other random FS in the manual partitioning screen.
[19:01] <arraybolt3[m]> XFS maybe?
[19:01] <kc2bez[m]> That should work fine.
[19:02] <arraybolt3[m]> Oh, I did forget, also add a baremetal install, both alone and with Windows alongside.
[19:07] <tsimonq2> I'm willing to bet the stack will migrate on the next Britney run.
[19:08] <tsimonq2> See also: https://phab.lubuntu.me/w/release-team/testing-checklist/
[19:09] <arraybolt3[m]> Nice, that's a way better list.
[19:10] <kc2bez[m]> tsimonq2: Yeah, that pretty much sums up everything we need. guiverc did a great job with that.
[19:10] <tsimonq2> I agree
[19:10] <tsimonq2> amd64 cala built in -proposed
[19:10] <tsimonq2> go for it, test :)
[19:10] <arraybolt3[m]> I see him and Leo also devoured the whole entire list. Alright, going in!
[19:12] <kc2bez[m]> So there is a new thing we can mess around with if we want, we can have the erase option but choose a file system in a dropdown, like the swap thing.
[19:12] <arraybolt3[m]> Dan Simmons: Can that be used to replace the custom partitioning steps, and then I'll just throw in an extra custom partitioning testcase?
[19:14] <kc2bez[m]> Essentially I think we could use simplify it for those that don't want to do a manual install just for something other than ext4
[19:14] <kc2bez[m]> If there is interest we can tweak the cala settings for that.
[19:16] <arraybolt3[m]> OK. I think it sounds like a good feature to use. The bios-grub notice that appears when you use manual partitioning was kinda scary and tough to figure out, so anything we can do to keep users out of manual partitioning without overloading the installer is a good thing IMO.
[19:17] <kc2bez[m]> https://github.com/calamares/calamares/blob/calamares/src/modules/partition/partition.conf#L147
[19:19] <arraybolt3[m]> Looks good. I'll add it to the testing.
 "I'm willing to bet the stack..." <- This made it https://launchpad.net/ubuntu/+source/xdg-desktop-portal-lxqt/0.2.0-0ubuntu1
[19:43] <arraybolt3[m]> Houston, we have a problem. Updating the live ISO from -proposed... well, here's the screen:
[19:43]  * arraybolt3[m] uploaded an image: (493KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/yvFafmGVCYRAdqszKBsPMJAZ/IMG_20220606_144316.jpg >
 "This made it https://launchpad...." <- Right, that was the prerequisite for lxqt-metapackages.
[19:45] <tsimonq2> Did you do a full update from -proposed?
[19:45] <tsimonq2> Something to know about -proposed is that updates need to be installed selectively.
[19:46] <arraybolt3[m]> Yep. Added -proposed, then sudo apt full-upgrade.
[19:46] <kc2bez[m]> arraybolt3[m]: You only need the one package or is that from your calamares install
[19:46] <tsimonq2> You should really only install the LXQt stack from -proposed or you will be pulling in Much Garbage.
[19:46] <arraybolt3[m]> Oh. Umm...
[19:46] <kc2bez[m]> oh yeah, don't do that
[19:46] <tsimonq2> :)
[19:46] <arraybolt3[m]> Didn't know that.
[19:46] <tsimonq2> Live and learn. It looks like a VM anyway.
[19:46] <kc2bez[m]> all good, live and learn
[19:46] <arraybolt3[m]> Well, hey, that'll save me ~5 GB of Internet data. (Yep, VM.)
[19:46] <tsimonq2> ha, jinx :)
[19:47] <kc2bez[m]> :D
[19:47] <tsimonq2> arraybolt3[m]: apt-cacher-ng
[19:47] <arraybolt3[m]> Simon Quigley: I'll take a look at that, looks like something I could use. My data is infinite, but my speed, not so much so.
[19:49] <arraybolt3[m]> I'm used to it being best practice to update before install to make sure everything's working great, so I didn't know full-upgrade from -proposed was a bad idea. It worked several times before! Oh well.
[19:51] <kc2bez[m]> Proposed has all sorts of stuff in there and things are very much in a state of flux, it can bork pretty hard.
[19:52] <kc2bez[m]> This is some pretty good reading on the subject: https://wiki.ubuntu.com/ProposedMigration
[19:52] <arraybolt3[m]> Well, I never test on production (I have a dedicated test laptop and use a lot of VMs), so when things go wrong, all I really care about is fixing it so that they go right, not recovering my data.
[19:52] <kc2bez[m]> Good plan
[19:56] <arraybolt3[m]> OK, problem two. Added -proposed, installed just Calamares, ensured it was the right version, double-clicked the icon, and... nothing. Dug into the desktop file, found the command, and ran it in a terminal, and now I'm getting an error. I'll pastebin it and send it.
[19:58] <arraybolt3[m]> https://pastebin.com/LpDbNTZm
[19:59] <arraybolt3[m]> I also tried the "export $(dbus-session)" or whatever it suggested, by adding it to the command line before the Calamares part of the command, and it gave the same error.
[20:00] <kc2bez[m]> Just try this `sudo -E calamares -D6`
[20:00] <arraybolt3[m]> OK.
[20:00] <arraybolt3[m]> Same error.
[20:02] <kc2bez[m]> hmm, that isn't good
[20:03] <arraybolt3[m]> I did "sudo -E bash", then "export $(dbus-launch)". And I got this:
[20:03] <arraybolt3[m]> dbus[6296]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/999" is owned by uid 999, not our uid 0
[20:03] <arraybolt3[m]> But then I did "calamares -D6", and it launched.
[20:04] <kc2bez[m]> Really, interesting.
[20:04] <arraybolt3[m]> It's not looking hopeful, though - I've got a spinning icon that keeps counting down from 5 to 0 over and over, and a blank spot where the Lubuntu "Welcome to the next universe" thing should be appearing.
[20:05] <arraybolt3[m]> It's letting me try to install, though, so I'm giving it a whirl.
[20:05] <kc2bez[m]> sure, go for it.
[20:06] <tsimonq2> arraybolt3[m]: https://github.com/calamares/calamares/issues/1974
[20:07] <arraybolt3[m]> That's exactly the screen I got, almost!
[20:07] <arraybolt3[m]> Ah, fantastic. Installation failed. Boost.Python error in job "fstab".
[20:08] <arraybolt3[m]> Oh, I see it, it's might be our config's problem. "name 'ssd_extra_mount_options' is not defined"
[20:08] <arraybolt3[m]> https://pastebin.com/1GVfE584
[20:11] <arraybolt3[m]> Oh dear, but ssdExtraMountOptions exists in fstab.conf.
[20:14] <arraybolt3[m]> It looks like they moved where config options go or something. It appears they removed "ssdExtraMountOptions" from fstab.conf, looking at the difference between 3.2. x stable and the default branch on GitHub.
[20:14] <arraybolt3[m]> https://github.com/calamares/calamares/blob/calamares/src/modules/fstab/fstab.conf
[20:19] <arraybolt3[m]> What I find even weirder is that I can't find the commit that removed a bunch of stuff from fstab.conf. Looking through the commit history, it's like it just... vanished? Maybe I'm not looking close enough?
[20:22] <arraybolt3[m]> Agh, I was on 3.2.x while looking at the commit history... 🤦‍♂️
[20:26] <kc2bez[m]> Looks like we need to parse this: https://github.com/calamares/calamares/commit/72240d0d598ccaa4f6da34e81fe3cbcd2d57b1e2
[20:26] <arraybolt3[m]> And it's the "merge work3.3 branch" commit that killed it. The one you just linked.
[20:26] <arraybolt3[m]> So now how do we see the commit history in that?
[20:27] <arraybolt3[m]> I can't find the "work-3.3" branch in Calamares anymore.
[20:27] <arraybolt3[m]> (If it was ever there in the first place)
[20:27] <kc2bez[m]> It is squashed and merged
[20:28] <arraybolt3[m]> A simple "ctrl+F" on the page reveals that "ssdExtraMountOptions" seems to have just been thrown out altogether.
[20:28] <arraybolt3[m]> So... great. Now what?
[20:28] <kc2bez[m]> I have to run for a few. I will read through it a little later.
[20:30] <arraybolt3[m]> I guess we may have to just overhaul our config files now that things have changed. I bet that's not the only area that's had serious modifications. We may have to recreate our whole config from scratch.
[20:30] <arraybolt3[m]> I vote for forking Calamares 3.2.x Stable into our own installer. (jk)
[20:31] <kc2bez[m]> We might. As long as the only thing that is broken is our config I don't worry too much.
[20:31] <kc2bez[m]> Negative on the forking cala though 
[20:32] <arraybolt3[m]> Right, that was meant to be a joke.
[20:32] <kc2bez[m]> I know. I was just going on the record ;)
[20:32] <arraybolt3[m]> OK, good. I was worried maybe I sounded serious LOL
[20:44] <tsimonq2> The tl;dr from -release is that the LXQt stack may not migrate without some hints 
[20:49] <arraybolt3[m]> Hey, should I take a swing at the Calamares config rewrite?
[21:06] -queuebot:#lubuntu-devel- New binary: libfm-qt [amd64] (kinetic-proposed/universe) [1.1.0-0ubuntu4] (lubuntu)
 "Hey, should I take a swing at..." <- Sure. 
[21:39] <tsimonq2> https://launchpad.net/ubuntu/+source/lxqt-session/1.1.1-0ubuntu2
[21:39] <tsimonq2> Please test if you have a Bluetooth mouse.
[21:40]  * arraybolt3[m] brandishes wireless... USB... mouse...
[21:42] <tsimonq2> https://discourse.lubuntu.me/t/qa-needs-testing-issue-tracker/3376
[21:42] <tsimonq2> Updated
[21:44] <tsimonq2> If someone wants some low hanging fruit while I'm gone, please turn this into an SRU: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1966774
[21:45] <tsimonq2> https://wiki.ubuntu.com/StableReleaseUpdates
[22:29] <arraybolt3[m]> Hey, so far the rewriting of our Calamares settings is going very well. I think I'll probably have it finished by tonight or earlier. I'll stick it on my GitHub, unless someone else has any objections or ideas.
[22:33] <kc2bez[m]> arraybolt3[m]: Well a PR with ours would be stellar. 
[22:34] <kc2bez[m]> I can guide you through that if you want.