I prefer to pass on this, not much time and I don't have problematic machines anymore to test. However, apparently there is a better solution for broadcom than it was before when I had the issue packaged in bcmwl-kernel-source.
Could we seed it?
https://packages.ubuntu.com/disco/bcmwl-kernel-source

Why in https://phab.lubuntu.me/w/lubuntu-dev/new-code/ this appear to be C++? It could be done in Python to.

What's SSO?

I understand the issue with wireless drivers (Broadcom comes into mind) but graphic cards?
I mean if there are graphic chards drivers necessarily needed (ie nouveau doesn't work) calamares wouldn't start, am I wrong?
Besides Broadcom, any other drivers you are aware of?

regarding galternatives...
https://forum.lxqt.org/t/lxqt-config-on-debian-recommends-galternatives/698/2

The w/o gnome is the protocol, the with gnome is the GUI that I think is like another tab in the network-manager-gnome

I still think the best option would be to use network-manager-gnome for configuring but I don't know if we can disable nm-applet from autostart. Nm-tray can already connect to an existing VPN
Is not the programming/development that bothers me, it is the maintenance

Why only open VPN? Network-manager-gnome has support for all of the below, pptp Is also used a lot. I think we have it in live seed
network-manager-fortisslvpn-gnome/disco 1.2.8-2 amd64
network-manager-fortisslvpn/disco 1.2.8-2 amd64
network-manager-iodine-gnome/disco 1.2.0-3 amd64
network-manager-iodine/disco 1.2.0-3 amd64
network-manager-l2tp-gnome/disco 1.2.10-1 amd64
network-manager-l2tp/disco 1.2.10-1 amd64
network-manager-openconnect-gnome/disco 1.2.4-2ubuntu1 amd64
network-manager-openconnect/disco 1.2.4-2ubuntu1 amd64
network-manager-openvpn-gnome/disco 1.8.10-1 amd64
network-manager-openvpn/disco 1.8.10-1 amd64
network-manager-pptp-gnome/disco 1.2.8-2 amd64
network-manager-pptp/disco,now 1.2.8-2 amd64 [instalado, automático]
network-manager-ssh-gnome/disco 1.2.8-1 amd64
network-manager-ssh/disco 1.2.8-1 amd64
network-manager-strongswan/disco 1.4.4-2 amd64
network-manager-vpnc-gnome/disco 1.2.6-2 amd64
network-manager-vpnc/disco 1.2.6-2 amd64

lxqt-config recomends galternatives

In T15#665, @tsimonq2 wrote:

How's it look now?

I agree that the 3 first are needed, if only those where cpp an not python, it would be lighter.
Not sure what xapian does, will investigate.

In T15#660, @rikmills wrote:

Ah, you had a software-properties-drivers-lxqt.desktop as well!

In T15#648, @rikmills wrote:

In T15#647, @hmollercl wrote:

Now we don't have menu entries for it, don't know why.

Did you add software-properties-lxqt.desktop to a .install file?

Now we don't have any menu entries, don't know why.

The proceses that pops up consuming memory, that are not lxqt related are:
python3 /usr/share/system-config-printer/applet.py
python3 /usr/share/unattended-upgrades/unattended-upgrades-shutdown --wait-for-signal
python3 /usr/bin/networkd-dispacther --run-startup-triggers
python3 /usr/share/apt-xapian-index/update-apt-xapian-index-dbus

found out that network manager also does the crick of loading all the icons (the system tray and the ones that appear when clicking over the tray to show the available networks) at the same time. Since the dialog is light background and the panel dark, the best solution might be to load them separately and use non-symbolic for the tray and symbolic for the available network list.

This is what I found on symbolic icons
https://wiki.gnome.org/Design/OS/SymbolicIcons

not sure why they use -symbolic icons, is tehre some kind of convention? I couldn't find anything in here https://specifications.freedesktop.org/icon-naming-spec/latest/ar01s02.html

On the user-friendliness, problem is that network-manager would need to support a lot of connection types. In case of network manager-gnome it supports (w/o -gnome is the protocol with -gnome is the gui):
network-manager-fortisslvpn-gnome/disco 1.2.8-2 amd64
network-manager-fortisslvpn/disco 1.2.8-2 amd64
network-manager-iodine-gnome/disco 1.2.0-3 amd64
network-manager-iodine/disco 1.2.0-3 amd64
network-manager-l2tp-gnome/disco 1.2.10-1 amd64
network-manager-l2tp/disco 1.2.10-1 amd64
network-manager-openconnect-gnome/disco 1.2.4-2ubuntu1 amd64
network-manager-openconnect/disco 1.2.4-2ubuntu1 amd64
network-manager-openvpn-gnome/disco 1.8.10-1 amd64
network-manager-openvpn/disco 1.8.10-1 amd64
network-manager-pptp-gnome/disco 1.2.8-2 amd64
network-manager-pptp/disco,now 1.2.8-2 amd64 [instalado, automático]
network-manager-ssh-gnome/disco 1.2.8-1 amd64
network-manager-ssh/disco 1.2.8-1 amd64
network-manager-strongswan/disco 1.4.4-2 amd64
network-manager-vpnc-gnome/disco 1.2.6-2 amd64
network-manager-vpnc/disco 1.2.6-2 amd64

Not quite with the spirit of this task but usefull.
Currently nm-tray is the only status icon that is dark over dark with papirus, making it difficult to see. That's because the icons it is using are the "symbolic" If you change it to non-symbolic that will be solved. The only problem is tha when clicking the icon there appear a listo of options with icons (like active connections) and that list has a light background and now that the icons are light they don't see well in that case, but the text is dark so it can be read.
Final solution should be to change symbolic icons to none symbolic and make the colors (background and fonts) of the list change with the theme.

I understand that all that is already on default. It would be good to test it, needs to be on bare metal.
Or should we also put that as our own default in case upstream changes it?

remeber we added qapt-deb-installer for .deb

https://phab.lubuntu.me/D1 added tap to click.
Any other option should be changed?

I have the solution in the code here https://code.launchpad.net/~hmollercl/+git/software-properties but I don't know how to propose merge

when running software-properties-qt w/o root privileges (bypassing the control)
Traceback (most recent call last):

File "/home/hmoller/discoMod/swProp/software-properties/softwareproperties/qt/SoftwarePropertiesQt.py", line 433, in set_update_automation_level
  SoftwareProperties.set_update_automation_level(self, softwareproperties.UPDATE_INST_SEC)
File "/home/hmoller/discoMod/swProp/software-properties/softwareproperties/SoftwareProperties.py", line 197, in set_update_automation_level
  self.set_modified_config()
File "/home/hmoller/discoMod/swProp/software-properties/softwareproperties/qt/SoftwarePropertiesQt.py", line 585, in set_modified_config
  SoftwareProperties.set_modified_config(self)
File "/home/hmoller/discoMod/swProp/software-properties/softwareproperties/SoftwareProperties.py", line 502, in set_modified_config
  self.write_config()
File "/home/hmoller/discoMod/swProp/software-properties/softwareproperties/SoftwareProperties.py", line 646, in write_config
  f = open(periodic, "w")

PermissionError: [Errno 13] Permission denied: '//etc/apt/apt.conf.d/10periodic'

requirements of root permision was before my interbention as can be seen in line 105 in https://git.launchpad.net/software-properties/tree/software-properties-qt and commit https://git.launchpad.net/software-properties/commit/?id=20ab26e195747cec8256f5cb3b2b1cf827b69ffe

does Kubuntu want to have software-properties-qt?
currently the .desktop should only be build for lxqt.
https://git.launchpad.net/software-properties/tree/data/software-properties-qt.desktop.in
line 7:
OnlyShowIn=LXQt;

I don't think is the best strategy. Between 18.04 and 19.04 there are a lot of different programs. I think the best strategies is to look if all the mimetypes of 18.04 are present and the ones that are not add. It with the new program