Goodbye from a Linux Community Volunteer
A long-time Linux kernel maintainer from a Russian company has been removed from the official MAINTAINERS file, likely due to Western sanctions, prompting a public farewell email and intense debate over how it was handled. Commenters largely accept that legal and compliance pressures can force such decisions, but criticize the opaque process, harsh public remarks, and perceived hypocrisy, warning that this could erode trust in Linux governance and deter contributors from sanctioned or non‑G7 countries. Some foresee more regional forks or alternative projects as open source collides more directly with geopolitics.
Emotional reactions & perceived unfairness
- Many commenters find the goodbye sad and moving, emphasizing the scale of unpaid contributions and the abruptness of the removal.
- Core complaint: the how, not the what — no advance warning, no public thanks, and harsh public remarks are seen as lacking basic decency.
- Others downplay the impact, noting that only maintainer status was removed and contributions via normal patches remain possible.
Legal, sanctions, and possible causes
- Widely assumed backdrop: sanctions (ITAR, OFAC, Executive Order 14071, etc.) and “compliance requirements.”
- Some infer that legal counsel or authorities pushed for broad removal of Russian-affiliated maintainers (especially those tied to sanctioned companies like CPU vendors for the Russian military).
- A few suggest “warrant canary”-style brevity in the commit message and say lawyers explicitly told project leaders what to do.
- Motives debated: legal risk management vs. espionage fears vs. political hostility; the actual legal necessity is viewed as unclear.
Communication style, politics, and CoC
- Strong criticism of aggressive replies that invoke nationality, history of Russian–Finnish conflict, and “Russian trolls/paid actors.”
- Some argue this contradicts the project’s own code of conduct (harassment-free, regardless of ethnicity/nationality). Others argue decisions target employers, not nationality.
- There is concern that kernel decisions are no longer purely technical but politically filtered.
Impact on open source and non‑G7 developers
- Several expect reduced participation from Russian and Chinese developers, and more regional forks or heavy patch sets (possibly BRICS-side kernels).
- Some see this as a “shot across the bow” for all developers outside the G7, pushing interest toward *BSD or projects not tightly tied to US/EU entities.
- Others say this is just the reality of operating under national laws; open source never implied a legal vacuum.
Open source vs. open governance, and politics
- Debate over whether FOSS is inherently political (user freedom, resistance to control) vs. primarily about code sharing.
- Distinction made between open source licenses (still intact) and project governance (centralized and susceptible to state pressure).
- Historical analogies (e.g., WWI anti-German sentiment) and double-standard accusations (e.g., Huawei, Israel) are raised, with no consensus.
HN moderation and meta‑discussion
- Multiple comments note heavy flagging and rapid de-ranking of related submissions, seen by some as users avoiding flamewars and by others as “rug sweeping.”