this post was submitted on 24 Oct 2024
277 points (90.4% liked)

Linux

48364 readers
1027 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
[–] LeFantome@programming.dev 20 points 1 month ago

Let’s just say this properly ok so that 70 percent of the commenters here might better understand.

Association with some of the people previously on the kernel maintainers list was putting the Linux kernel at risk. The risk was that European, American, and other users may be prohibited from using it. The risk was that entities such as the Linux Foundation could be held in contempt of sanctions and sanctioned themselves. That could mean financial damage or even a full stop to operations.

If the kernel were sanctioned, every entity, individual or company, could be put at risk.

Association with sanctioned individuals put every other maintainer at risk. Being listed together in the maintainers file put many innocent people in extreme jeopardy.

So, let’s say this properly ok…

Some of the maintainers were removed to defend the Linux kernel and the many, many entities ( individual and corporate ) that use it. They were removed to protect the other maintainers and the people and companies that they associate with.

The Linux Foundation, being American, may have been particularly at risk. But “moving” the kernel does nothing. The contributors and maintainers are still wherever they are. Linux users are equally economically dependent on the US and Europe regardless. The issue are the international sanctions. My country has issued them too ( neither American or European ). And blaming the counties that issued the sanctions, instead of blaming Russia, is a very interesting morale position to take ( not getting into that here ).

My first reaction was to have a problem with how this was done. However, once you acknowledge the association, any interaction, collaboration, or communication becomes even more problematic as you KNOW that you are working with sanctioned individuals. So, doing it simply and succinctly was probably best.