Official statement regarding recent Greg' commit 6e90b675cf942e from Serge Semin
Hello Linux-kernel community,
I am sure you have already heard the news caused by the recent Greg' commit 6e90b675cf942e ("MAINTAINERS: Remove some entries due to various compliance requirements."). As you may have noticed the change concerned some of the Ru-related developers removal from the list of the official kernel maintainers, including me.
The community members rightly noted that the quite short commit log contained very vague terms with no explicit change justification. No matter how hard I tried to get more details about the reason, alas the senior maintainer I was discussing the matter with haven't given an explanation to what compliance requirements that was. I won't cite the exact emails text since it was a private messaging, but the key words are "sanctions", "sorry", "nothing I can do", "talk to your (company) lawyer"... I can't say for all the guys affected by the change, but my work for the community has been purely volunteer for more than a year now (and less than half of it had been payable before that). For that reason I have no any (company) lawyer to talk to, and honestly after the way the patch has been merged in I don't really want to now. Silently, behind everyone's back, bypassing the standard patch-review process, with no affected developers/subsystem notified - it's indeed the worse way to do what has been done. No gratitude, no credits to the developers for all these years of the devoted work for the community. No matter the reason of the situation but haven't we deserved more than that? Adding to the GREDITS file at least, no?..
I can't believe the kernel senior maintainers didn't consider that the patch wouldn't go unnoticed, and the situation might get out of control with unpredictable results for the community, if not straight away then in the middle or long term perspective. I am sure there have been plenty ways to solve the problem less harmfully, but they decided to take the easiest path. Alas what's done is done. A bifurcation point slightly initiated a year ago has just been fully implemented. The reason of the situation is obviously in the political ground which in this case surely shatters a basement the community has been built on in the first place. If so then God knows what might be next (who else might be sanctioned...), but the implemented move clearly sends a bad signal to the Linux community new comers, to the already working volunteers and hobbyists like me.
Thus even if it was still possible for me to send patches or perform some reviews, after what has been done my motivation to do that as a volunteer has simply vanished. (I might be doing a commercial upstreaming in future though). But before saying goodbye I'd like to express my gratitude to all the community members I have been lucky to work with during all these years.
Also from that thread.
US law CAN'T apply on foreign ground, period. Nothing can. Just because they can bully their way around that, doesn't mean they are right.
And it should be only fair that Israeli maintainers be removed as well.
They should also rethink their infrastructure policy and whether they still want it on US soil.
This is all wishful thinking, I know, but this just goes to show you how they have absolutely no backbone whatsoever. As if anybody is gonna touch the Linux kernel and jeopardize the safety of millions of systems. We all know that is never going to happen, but they still bent over for the US... so typical... just goes to show you how little backbone everyone has, including Linus.
Oh, and don't get me started on the Russia/Finland history comment...
If the company is in the USA they can restrict who you colloborate with. They also can control what you export as a oftware product under ITAR/EAR rules. It is why when some encryotion work had to be done the devs crossed the border into Canada to work on development, because under USA law encryption code is a controlled export product even if opensource
Then why in the hell was the LF founded in the US? That is something that clearly needs explaining. For example, Sweden is a much better place to do these sorts of things, their software laws are very liberal.
Some of these things need to be rethought if you ask me, this is not something that should be left like this. If no one in the kernel, including Linus, doesn't see a serious problem with "we have to move people around to code", then most of these people are probably braindead... I'm sorry, but if it was me, once I found out I had to move devs around to code, I would have been "fuck this we're moving the foundation".
I agree it might be better elsewhere. (Like how my preference is Protonmail being hosted by a neutral country based company) But so I don't mislead, my encryption example was generic, not specific to linux kernel....however any novel encryption does have to be noted to NSA and other organizarions in the USA. Canada has something similar but it appeared less strigent, and adjustments have been made between the bordering countries. I personally diaagree that encryption should have government hand in it, it solves nothing. A foreign state actor wanting to send encrypted communications to overthrow another entity isn't going to follow software laws anyway.
I also use Protonmail because of this. Sure, the free plan is not really great, but I only keep important stuff, so I don't get over the 500MB limit, I delete or archive the rest.
That may be true, but only if you're a US citizen. For example, my country doesn't have such regulations. In the end, if it's open source, it shouldn't matter whether I report stuff like that to any organization. It's open source, look it up, it's on a git repo online freely for everyone to review the code.
Exactly. As if hacking and DDOSing are legal 😒. It's just throwing money away on some people doing pointless things.
On the other hand, having a ln encryption technologies taskforce makes sense IMO. Watching over what's going on in the open source world regarding cryptography, yeah, that is something that can actually be useful... for the country's cyber-security I mean.