More hardware platforms that can be supported. The potential of a brand new OpenWrt/DDWRT like project for TVs is attractive, especially for Vizio TVs (which are extremely common and their factory software is terrible).

The context here is that (1) Linux allows proprietary drivers so even if they release all the code they're required to release it probably won't include drivers that TVs need and (2) code released by embedded vendors is very low quality so you'd have to spend years cleaning it up.

Linux does not allow proprietary drivers. The fact that people do it anyway is a separate issue.

I don’t know how Linux can function on modern hardware. It requires modules in some cases like Broadcom WiFi that are proprietary.

It is possible to start it on-demand via the command-line. That is how krdp is developed and tested. You will need to pre-authorize krdp to the portal system, though.

That's documented here: https://develop.kde.org/docs/administration/portal-permissio...

Hah, that actually works, thanks!

Is it possible to do the permission-set remotely?

If you can shell in, I don't see why not? It's a command-line thing. It's intended to also be usable for things like Ansible. If it doesn't work, please file bug reports!

KDE Plasma offers two options:

1. KRdp (preferred): a RDP server for KDE Plasma.

2. KRfb: a VNC server for KDE Plasma.

Both should be able to be configured to support your use-case. If they can't, please file bugs!

I think one of the biggest mistakes was not making WebVTT equivalent to Advanced SubStation Alpha (the format of Aegisub). That would have driven basically all the various streaming services to grow support for the things anime subbers have done for years.

No need for a new format, just use ASS itself! https://github.com/libass/JavascriptSubtitlesOctopus

Oracle didn't follow that with DTrace. They changed the license away from CDDL when they integrated it into Oracle Linux.

I've been running Btrfs on Fedora for a decade now (and it's been the default since 2020). I have basically never done any of those things and it's been fine. I've had to do more babysitting with my ZFS systems than I did my Btrfs ones.

The biggest mistake is not having a staging subtree for filesystems like we do for most other drivers.

Oh, that's interesting. Is there any reason it couldn't have just gone under drivers/staging?

I think it's mostly a policy thing? I brought it up a few years ago and the fs developers were not very enthused about the idea.

Pretty much all of it is in mainline modulo the secure boot lockdown patches, which are downstream for all distributions because Linus fundamentally believes those patches do not make sense.

Linux longterm often is missing stuff the RHEL kernel has, because RHEL backports subsystems from mainline with features and hardware support.

It needs to be present in the headers of each file that they took from. Attribution matters and in mixed projects you need that clarification at the file level.

Does the MIT licence text say that? I don't understand it like this. I understand that a copy of the licence should be preserved, not that the licence should be copied into source files.

I think the fork needs to preserve the LICENSE file in the repo and in distributed code (e.g. packages), right? But not replicated as a file header in every blessed file in the repo.

The legacy symbols are still around. It's just that the linker won't use them by default.