CRA just brings the kind paperwork that physical products have always had to be licensed in the EU (CE marking) to software. Have you seen european companies investing in Open source hardware?
The path of least resistance will be to use homegrown alternatives and sell them to potential investors and shareholders as valuable intellectual property that puts them ahead of competitors.
Not only because that makes perfect business sense, but because this kind of IP is very hard to value fairly, so it will allow for a variety of accounting and tax avoidance shenanigans.
Keeping people safe when it comes to software means first and foremost having good security.
Arduino and RepRap are poster children of open source hardware, and originated in the EU, I think.
For example, CE only prevents people from selling products. For example, I’ve done pilot tests (city wide installations of urban equipment) with devices that, while I knew they’d be compliant, we had done 0 tests.
It’s also fairly trivial and common to cheat at the tests. Most EMC testing is done in conditions that aren’t necessarily the normal operating conditions and with “accessories”.
If anything else fails, aside from medical or safety critical devices, you could always self certify and roll the dice, it’s way more common than what people think.
Take a small-medium sized business (say 5 - 50€ million annual revenue). Perhaps it can fund one library that is critical to it, but no contribution it makes will make a material difference to the trajectory of major products like Linux, or Python.
Not a lawyer, but it also seems to me that if you are a small shop, you might decide to pay, e.g. RedHat for taking on the liability. RedHat can pool these resources to make sure their software behaves as advertised.
As a software developer at a non-tech firm, I can gaurantee this means we will not be able to use any open source software. If we are granted an exception, it will be such that we must maintain a private version of the open source software.
This is simply a no-go for many companies of all sizes. The risk associated here is not something many (any?) legal department will be willing to take on.
If your company is not willing to pay someone (another company ) for making sure the open source software used is actually working properly (and for assuming liability if it doesn't), then it can't use open source software. But then, what does open source lose when losing for profit users that are not willing to contribute back?
That’s clear.
What will happen is that company A will hire company B to do this and assume liability for it. If we set the annual cost of this at 100k, the monthly cost is about 8333 EUR. Let's say company B has 20 customers to protect the security of libImportant, that is 416 EUR per month and SME can afford that. There are OS that are of course used more frequently and that scales much better (i.e. cheaper per month). I actually see a new market niche here and perhaps they will find resourceful entrepreneurs.
For linux you will probably be able to buy a certified Linux distribution for similar costs to Windows which is affordable to a medium sized company that needs certification. However that will only cover your basic OS: linux, ls, basic gnome desktop (but not many applications, just the window manager, a file management, and email client) - probably not a web browser.
However there are a lot of small projects that are not popular enough for anyone to certify like that.
That assumes it is your company to move in the first place. Which is unlikely. So add find a new job to the list of things you need to do.
An example: EU is approving very restrictive legislation about pesticides for use inside the EU but it happily allows importing food grown in other countries using the very same forbidden substances.
If I buy a screw made in the USA, no EU authority can know what's the software used in the machine tool. They can control physical properties, packaging, information... but the process used is opaque.
And I personally think that's a good thing