 Heeey. It’s being worked out, we had some LP deployment thingy. Steve and Brian are working through things and they’ll handoff to me when I start my day tomorrow (UK time) and I’ll take it from there. You’ll start to see things soon. ;) (re @tsimonq2: @utkarsh2102 Respectfully, what's the holdup with opening noble? :))
[02:51] <arraybolt3_wc> Alright, the initial window of the network modifier is now (mostly) implemented, now I just have to create all of the settings windows, the add network window, the remove network window, and their functionality, and then we have an app :D
[02:52] <arraybolt3_wc> Can someone give me back Git access? I'd like to be able to push my current work-in-progress project to Lubuntu's git infra so it can be reviewed/modded/whatever by others (plus just in case something goes wrong and I vanish, nothing is lost)
[02:52] <arraybolt3_wc> I can push it to GitHub if that's not feasible at this time.
 @tsimonq2 Figure out how to make Sitter's ideas work with your patch?
 I'm juggling it :) you'll be the first to know
 
 I apologize for any delays (re @Eickmeyer: @tsimonq2 Figure out how to make Sitter's ideas work with your patch?)
 No worries. Got people pinging about upgrades, it's possible they're already getting the notification about EOL coming but don't have the upgrade path yet. This entire ubuntu-release-upgrader font bug is getting rather annoying, and having to explain it over and over again to people even more so. (re @tsimonq2: I'm juggling it :) you'll be the first to know
 
 I apologize for any delays)
[19:16] -queuebot:#lubuntu-devel- Unapproved: calamares-settings-ubuntu (noble-proposed/universe) [1:23.10.4 => 1:24.04.1] (lubuntu, ubuntustudio)
[19:16] -queuebot:#lubuntu-devel- Unapproved: calamares (noble-proposed/universe) [3.3.0-alpha2-0ubuntu6 => 3.3.0-alpha4-0ubuntu1] (lubuntu, ubuntustudio)
[19:16]  * Eickmeyer gets heart attack from notifications in several channels from that
[19:19] <arraybolt3_wc> so Noble is open but we still don't know the secondary codename?
[19:19] <tsimonq2> That's correct.
[19:20] <arraybolt3_wc> hmph
[19:20]  * arraybolt3_wc continues coding the network editor in the mean time
[19:38] <arraybolt3_wc> And we can now delete networks! \o/
[19:38] <tsimonq2> for network in public_networks; do delete --force $network; done
[19:38] <tsimonq2> "Wtf my WiFi isn't working?"
[19:38] <arraybolt3_wc> >_<
[19:39] <arraybolt3_wc> you aren't supposed to delete ALL of them!
[19:39] <tsimonq2> XD
[19:39] <arraybolt3_wc> Technically you can though :P
[19:39] <arraybolt3_wc> And I haven't implemented the network *creator* yet so...
[19:39] <tsimonq2> hah :D
[19:39] <arraybolt3_wc> But, one more button working :)
[19:40] <tsimonq2> Very nice, keep up the good work :D
[19:40] <arraybolt3_wc> Thanks :) (I'm shamelessly stealing bits and pieces from plasma-nm where convenient :P open-source is awesome)
[19:41] <tsimonq2> shhhhh :P
[19:42] <tsimonq2> I mean, this tweet only has 7800 views :P
[19:42] <tsimonq2> https://twitter.com/LubuntuOfficial/status/1715370926143873310
[19:42] <tsimonq2> No pressure. ;)
[19:43] <arraybolt3_wc> hehe
[22:04] <arraybolt3_wc> Licensing question - what license do we want for lubuntu-connection-editor? I was going to slap on GPL-3.0-or-later since it's compatible with the plasma-nm code I'm horking from and seems like a sane enough choice, but if someone would prefer some other GPL or LGPL license, I can change it quite easily.
[22:05] <arraybolt3_wc> (GPL-2.0-or-later might be preferable, idk)
 *shrug* you're the author, I honestly don't care as long as it can go in the archive and isn't stupidly permissive
 I guess GPL-3 if you can't decide on one
[22:45] <arraybolt3_wc> If there's not a preference, I don't see the value in the extra permissiveness of GPLv2, and I'm a bit more sure that GPLv3 will be compatible with the code I've integrated than GPLv2 (I'd have to do extra checks to see if GPLv2 is viable), so GPLv3+ it is.
 Sounds good