If you have reasonable arguments why it should be enabled by default beyond “Oh! But it is s-o-o-o-o c-o-o-o-l!”, by all means, submit bug report. Or even better, branch, modify and send request to merge you changes.
Please note that people do not really like it when a default changes. They probably use the default as such for years and when a default changes they will be the victim of unwanted actions!
For me the default is what openSUSE delivers me already for years. Not what is happening in other distros or what happens upstream.
You do not quite seem to understand this. But when people run their system since years to satisfaction and they have it configured there where they thought they wanted to deviate from the default (the one that is there on installation, not the one in far remote upstream), it will hit them heavy when a configuration value changes from one moment to the other because the default they use (often without knowing) has changed.
The only thing one could do to avoid damage done by changing defaults is by always configuring every parameter that exists and never trust on defaults. I would not like such an environment.
The Plasma developers only have a view on their desktop environment. But openSUSE/SUSE has a view on a complete set off different distributions. The Plasma updater does not fit the needs of all distributions. Thats why openSUSE decided to use specialized built in tools and mechanisms to keep the distro up to date. There is no need for a 3rd party DE updater from the Plasma team when tools for distribution updates/upgrades exist…
This is the exact topic what is discussed here. The plasma-notifier and Discover are no qualified tools to update Tumbleweed (or any other distribution which has its own updater tools). Thats why some additional features are disabled because they meddle with proper distribution update/upgrade management.
I see in various places about offline updates discover-5.27.7> fgrep -r "Offline" * | less which is tied in with PackageKit, but to me it looks like it’s upstream whom disable (But I’m probably wrong?)
You need to understand that openSUSE is a do-ocrity, if you have an itch for something as already pointed out, submit your fix to the package. If it’s a really a bug (If you started a bug report to one of my packages with “I have a grievance…”, I would most certainly close as "Won’t Fix) report it https://en.opensuse.org/openSUSE:Submitting_bug_reports
Offline updates means “system update mode”. I recommend the usage of “system update mode” provided by systemd: # man systemd.offline-updates
Use OpenSUSE Leap, update your machines with self made systemd services and shell scripts in system update mode. Deliver all software packages (rpm) from our own packet repository. Build your own packet repository (YUM repository). Howto:
Work with patches (zypper lp and patch-info) and forget OpenSUSE Tumbleweed.