this post was submitted on 24 Oct 2024
245 points (89.4% liked)

Linux

47866 readers
1340 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] kbal@fedia.io 170 points 2 days ago (2 children)

Later in that thread:

Please accept all of our apologies for the way this was handled. A summary of the legal advice the kernel is operating under is

If your company is on the U.S. OFAC SDN lists, subject to an OFAC sanctions program, or owned/controlled by a company on the list, our ability to collaborate with you will be subject to restrictions, and you cannot be in the MAINTAINERS file.

Anyone who wishes to can query the list here: https://sanctionssearch.ofac.treas.gov/

[–] schizo@forum.uncomfortable.business 128 points 2 days ago (32 children)

Which is exactly what anyone who wasn't wanting to just snort some concentrated outrage knew was the case.

And you can argue as to if OFAC list should apply to things like this or not, but the problem is that the enforcement options for OFAC violations include 'stomp you into the ground until you're powder', most people are just going to comply.

[–] prole@lemmy.blahaj.zone 10 points 1 day ago (1 children)

Oh hey, a reasonable comment here that actually has a decent score... These comments are wild. But given the recent... I'll just say, conspicuously pro-Russian, turn this site seems to have taken in the run up to the election, it's not exactly a surprise.

I'm shocked I didn't get downvoted to shit myself.

It's just that it was VERY clearly either sanctions or a NSL, since the Linux Foundation is in the US and the two things that result in a public entity like that making silent, un-explained changes are, well, sanctions and NSLs and you don't say shit because your lawyer told you not to.

I don't necessarily agree that tossing contributors off an open-source project is in the spirit of the OFAC list, but the problem almost certainly is that they're employed by some giant tech company in Russia.

And, in Russia, like in the US, and Israel, and China, and anywhere else you care to mention, tech companies are almost always involved in military supply chains, since shit don't work without computers at this point.

Which leads to a cycle of being unable to work with Weapons, Inc. and someone works for Weapons, Inc. so now that person can't be worked with either and so your choices are.... comply with the OFAC list, or take a stupid amount of legal risk up to and including angry people with guns showing up to talk to you.

We really don't know the whole story and immediately jumping to "Imperialists bad!" is how certain chunks of Lemmy roll these days.

I think they'd be much happier if they all moved to North Korea and helped achieve the goal of Juche by becoming dirt farmers.

load more comments (31 replies)
[–] SnotFlickerman@lemmy.blahaj.zone 12 points 2 days ago (5 children)

But folks who work for US companies building weapons for Israel are totes okay?

It's honestly fucking wild that an internationally developed open source project has to play by the US government's rules when the US government is out here helping commit genocide right the fuck now.

Like, look in the fucking mirror on this why don't you.

Maybe the better rule is that if you work for a company that produces weaponry for war you shouldn't be allowed to contribute, period.

[–] prole@lemmy.blahaj.zone 8 points 1 day ago (5 children)

But folks who work for US companies building weapons for Israel are totes okay?

Who here said this?

load more comments (5 replies)
[–] Orygin@sh.itjust.works 52 points 2 days ago (1 children)

Wow, I didn't know that being a Linux/open source contributor meant you don't have to follow your country's laws.

It's developed internationally but devs still reside somewhere and have to abide by the rules at that place. Linux in this case being represented by an US entity means they have to follow the gov's sanctions. If you want more or less of those, that's where (the government) you act.

This isn't about them being kicked out, this is about the fact we don't know the process that resulted in this. Was this a decision Linus made after a night coding and thinking about the world? Was the foundation ordered to do it?

It lacks transparency into the process even if the outcome is fine and the way it was done doesn't feel transparent, even if it makes sense not to include Russian coders in the project.

[–] kbal@fedia.io 30 points 2 days ago (8 children)

You may be amazed to learn that there aren't many international sanctions against the USA at this time, but I imagine you could probably get into legal trouble for collaborating with Americans if you're in, I don't know, North Korea maybe.

[–] prole@lemmy.blahaj.zone 4 points 1 day ago

What are you even trying to say here?

Do you think you've unraveled some massive conspiracy simply by learning about the existence of Western hegemony?

[–] AbidanYre@lemmy.world 19 points 2 days ago (1 children)

It's crazy how the US Treasury isn't sanctioning companies for working on US government approved contracts. /s

[–] davel@lemmy.ml 17 points 2 days ago (6 children)
load more comments (6 replies)
[–] davel@lemmy.ml 15 points 2 days ago (1 children)

You may be amazed to learn that the reason there aren’t many international sanctions against the USA at this time is not because the USA is a beacon of peace, freedom, democracy, and national sovereignty. Because the US is very much not that.

[–] Auli@lemmy.ca 1 points 1 day ago (1 children)

Well it’s by far the biggest economy in the world and the whole world uses the tech developed in the US. sanction them and they could cut off your access to technology.

[–] davel@lemmy.ml 0 points 1 day ago* (last edited 1 day ago)

That’s beside my point, but since you brought it up, the US is not the world’s largest economy, and China & Russia seem to be doing alright despite US sanctions, including technology sanctions. The US is no longer the indispensable nation; that ship sailed a while ago.

load more comments (5 replies)
[–] 0x4E4F@infosec.pub 6 points 2 days ago* (last edited 2 days ago)

Maybe the better rule is that if you work for a company that produces weaponry for war you shouldn't be allowed to contribute, period.

This is something I can actually get behind on.

But, you see, there is just one teeency weeency tiny problem with that. They spend trucks of cash on whatever they deem will give them what they want, including funding organizations that they profit from.

load more comments (1 replies)