this post was submitted on 23 Oct 2024
114 points (100.0% liked)

technology

23313 readers
129 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 4 years ago
MODERATORS
 

Perhaps one of the more surprising changes in the 6.12-rc4 development kernel was the removal of several entries from the kernel's MAINTAINERS file. The patch performing the removal was sent (by Greg Kroah-Hartman) only to the patches@lists.linux.dev mailing list; the change was included in a char-misc drivers pull request with no particular mention.

The explanation for the removal is simply ""various compliance requirements"". Given that the developers involved all appear to be of Russian origin, it is not too hard to imagine what sort of compliance is involved here. There has, however, been no public posting of the policy that required the removal of these entries.

An early comment likely pins down the prevailing institutional pressures leading to this decision

What's the deal with an international project adhering to what is obviously a decision of the US government?

Hint: The Linux Foundation (which notably employs Greg KH and Torvalds, and provides a lot of the legal and other infrastructure for this "international project") is based in the US, and therefore has to follow US laws.

This is pretty fucked up. Like, we might see the kernel forked in the coming months/years.

See also: Phoronix: Linus Torvalds Comments On The Russian Linux Maintainers Being Delisted

you are viewing a single comment's thread
view the rest of the comments
[–] grandepequeno@hexbear.net 3 points 3 weeks ago* (last edited 3 weeks ago) (5 children)

So, banning maintainers who are russian means what in the long term? What were they contributing before?

[–] itsraining@lemmygrad.ml 8 points 3 weeks ago (2 children)

This is the list of contributors that got removed according to a popular russian Linux web community.

  • Abylay Ospan *@netup.ru, drivers for DVB-systems NETUP PCI, HELENE, ASCOT2E, HORUS3A, LNBH25 & CXD2841ER
  • Alexander Shiyan *@mail.ru, port for ARM/CIRRUS LOGIC CLPS711X
  • Dmitry Kozlov *@mail.ru, PPTP and GRE DEMULTIPLEXER drivers
  • Dmitry Rokosov *@sberdevices.ru, EMSENSING MICROSYSTEMS MSA311 driver
  • Evgeniy Dushistov *@mail.ru, UFS file system
  • Ivan Kokshaysky *@jurassic.park.msu.ru, Alpha architecture loty
  • Nikita Travkin *@trvn.ru, ACER ASPIRE 1 controller drivrer
  • Serge Semin *@gmail.com, BAIKAL-T1 platform, base drivers for MIPS systems, drivers for BAIKAL-T1 PVT, DESIGNWARE EDMA CORE IP, LIBATA SATA AHCI SYNOPSYS DWC CONTROLLER, NTB IDT, SYNOPSYS DESIGNWARE APB GPIO, SYNOPSYS DESIGNWARE APB SSI
  • Sergey Kozlov *@netup.ru, drivers for DVB-systems NETUP PCI, ASCOT2E, HORUS3A, LNBH25 и& CXD2841ER
  • Sergey Shtylyov *@omp.ru, drivers for LIBATA PATA, RENESAS R-CAR SATA, RENESAS SUPERH ETHERNET & RENESAS ETHERNET AVB
  • Vladimir Georgiev *@metrotek.ru, MICROCHIP POLARFIRE FPGA driver
[–] grandepequeno@hexbear.net 3 points 3 weeks ago (1 children)

So they're no longer allowed to do what in regards to these systems? Do they not have access anymore to the things they built? Or is it that now there's a russian "branch" of these and a not russian "branch" that they both have access to?

I'm literally in IT and I don't know this shit lol, such a dummy

[–] itsraining@lemmygrad.ml 4 points 3 weeks ago

Apparently they have just been removed from the MAINTAINERS file for now but it is not yet known if this will have any implications for their ability to send patches for inclusion in the kernel. If the latter proves to be the case, some of the drivers might end up unmaintained until another person gains enough trust to become a maintainer. This will surely affect support for the Russian BAIKAL processors, for example.

Apparently the removed contributors can return only if they provide some sort of "documentation" (not specified which though). They can still work on the kernel, but now they are not able to directly merge changes into the codebase, they can only send patches which may or may not be accepted. Or they could organise and create an independent Linux kernel fork which they would have to keep up to date by merging code from the upstream.

This much I understood from the news and comments.

load more comments (2 replies)