It sets a precedent of banning maintainers and other contributors from nations in the Global South and nations declared enemies of NATO. This goes against open source philosophy, and this will lead to China and other nations needing to develop their own sovereign forks or kernels from scratch.
It’s similar to the US working to ban RISC-V to stop China from using an open source instruction set to become more technologically sovereign. Restricting open source software from NATO’s enemies is essentially NATO shooting themselves in the foot in the long term. NATO is sanctioning an enemy, so the enemy is incentivized to build alternatives to tech they lost (which can be forked easily), and then the alternatives become popular and challenge NATO’s tech, which is not competing where over 30% of manufacturing industry exists, which leads to NATO’s tech and industry crumbling as it cannot dominate the market like it was able to before and further accelerates the Empire’s decline.
This is a good comment on this thread that explains the long term consequences more comprehensively than what I did: https://hexbear.net/comment/5541448
https://hexbear.net/comment/5541326
I learned Hyperbola is moving to its BSD derivative kernel, HyperBK, on this thread, and it will be GPL.