Several Russian developers lose kernel maintainership status

Original Article ↗ Hacker News Discussion ↗

Several Linux kernel maintainers with Russian email addresses or ties to sanctioned Russian companies have been removed from the official MAINTAINERS file, cited only as a response to “various compliance requirements.” Commenters debate whether this is a necessary legal or national security safeguard against potential state coercion, or an overreaching form of collective punishment and de facto discrimination that undermines the ideal of open, global collaboration in free software. Many also criticize the lack of transparency around the legal basis for the move and worry it sets a precedent for politicizing key infrastructure projects based on geopolitics.

Scope and Reason for the Change

  • Many commenters focus on a recent commit removing several Russian-linked maintainers from the Linux MAINTAINERS file, justified in the commit as meeting “compliance requirements.”
  • Explanations debated:
    • Legal/sanctions compliance (EU/US export controls, broad Russia sanctions).
    • National security risk reduction (avoiding coercible maintainers in Russia).
    • Overly conservative “lawyer-driven” self-censorship to avoid unclear sanctions liability.
  • Exact legal basis is unclear; maintainers refer to advice from lawyers but do not share details, which several commenters find troubling.

National Security vs. Discrimination

  • Pro-removal arguments:
    • Russian state is seen as willing and able to coerce citizens via threats to them or their families.
    • High-value targets like the kernel justify removing “low-hanging fruit” (maintainers in Russia / sanctioned orgs).
    • This could actually protect those individuals from state pressure by removing their leverage value.
  • Critical views:
    • Any maintainer anywhere can be bribed or coerced; focusing on one nationality is arbitrary.
    • No documented case in major OSS of such state-coerced backdoors; some call the scenario speculative “movie-plot” thinking.
    • Some liken it to nationality-based discrimination or a new McCarthyism, and ask why similar logic isn’t applied to US, Chinese, Israeli, etc. maintainers.

Sanctions Ethics and Effectiveness

  • Some strongly support harsh sanctions, even explicitly endorsing broad pain on the Russian populace as leverage against the regime.
  • Others argue sanctions mostly harm ordinary people, especially in authoritarian states where public pressure is weak.
  • Comparisons made to US-led wars, coups, and other countries’ abuses; accusations of Western double standards.

Open Source Governance and Trust

  • Concerns:
    • Non-transparent removal process, vague criteria (“compliance requirements”), and no clear avenue for appeal or reinstatement.
    • Fear this will deter non-Western maintainers and drive projects away from US jurisdictions and infrastructure.
    • Some see it as evidence that the “borderless, apolitical” open source ideal is over.
  • Counterpoints:
    • Open source only guarantees code access and forkability, not inclusive governance.
    • If people dislike the decision, they are free to fork the kernel or build alternative governance structures.

Practical and Future Implications

  • Questions about impact on other projects and distributions with Russian maintainers.
  • Noted that some removed maintainers simply had .ru emails despite living/working elsewhere; perceived as inconsistent.
  • A minority suggest moving to formally verified microkernels (e.g., seL4) to limit the impact of kernel backdoors regardless of politics.