

The other option is to use VirtIO with Native Context support as a software based partitioning scheme that is relatively lightweight compared to the mdev approach.
FLOSS virtualization hacker, occasional brewer
The other option is to use VirtIO with Native Context support as a software based partitioning scheme that is relatively lightweight compared to the mdev approach.
The kernel on GitHub is just a mirror - the primary source is on kernel.org
Not just that - modern Androids compile apps in a VM these days to reduce the attack surface of the compiler. You can also push other services into VMs that support the main image. You could even push some vendor drivers into VMs and help keep the main kernel less of a vendor fork fest.
FLOSS projects can only be sustainable if their are enough shared interests able to support it through contributions of all kinds. Fortunately the code is free so that constellation of support can change over time. It’s a shame this particular line of government funding is coming to an end but others can help.
I think the most useful thing for this is hosting repos that suffer from constant DMCA takedowns. Emulators, ad-blockers, site revancers etc.
Magit is one of Emac’s many superpowers.
Care needs to be taken with big orgs like the NHS to not try and boil the ocean with massive IT systems. Concentrating on open interoperability standards allows for smaller more flexible contracts and the ability to swap out components when needed.
Open source licences would be the ideal default although at a minimum the purchasing org should have a licence that allows them (or subcontractors) to make fixes without being tied to the original vendor.