With SUSE in the private-equity shop window, another crucial part of sovereign infrastructure is once again at risk. We hear: “Surely this can’t be allowed?!” and “Surely this shouldn’t be possible?!” or “Why don’t we stop it?”
Well, nice sentiment… but what exactly should be done, and by whom?
Should the government compete with private equity? Should we create EU rules that restrict investments and acquisitions? Should we designate companies as national or EU software heritage, or as national infrastructure? Should we treat digital infrastructure like utilities and, in turn, establish frameworks that safeguard security and stability? Should governments simply handle digital infrastructure themselves, now that it has all become so uniform?
And how far do we go with potential protective rules in a world that is fragmented and maintained internationally across multiple layers? Think of crucial libraries and components with contributors from the US or China. Is that even realistic?
Once again, it is a real shame that SUSE is being snatched away from under our noses. But telling a supplier that they are the sole or de facto supplier to governments seems more like an incentive for acquisition than for stability. So more is needed: a different and more sophisticated relationship than that of supplier and customer. One that does not stand in the way of commercial success, while safeguarding stability for governments.
Standardisation may also be one avenue. In other words, a stepping stone towards interoperability and interchangeability. Creating an EU standard that software, hardware, and suppliers must comply with.
Again: how far do we go with that? How much will such measures help, and how much might they cause stagnation in a world with the fastest turnaround of products and services?
A reaction to this post (NL) on LinkedIn: https://www.linkedin.com/posts/servaasschrama_digitalsovereignty-suse-eurostack-activity-7457368626661232640-3lb5?utm_source=share&utm_medium=member_desktop&rcm=ACoAAABDErgBXIsWT6rIF46X4gcyUxpBbrP_irI