Email or username:

Password:

Forgot your password?
33 comments
Andy H3
What was the stated rationale for this move by the community?
@LaF0rge
Robert Schwebel

@LaF0rge Thanks, Harald, for this perceptive analysis! While "There IS no politics in Open Source" (said by one of the core kernel maintainers many years ago) was always meant ironical, the issue shows how far daytime reality has moved away from the fundamental rights and values, as written down in the Open Source definition, UN Charta, Grundgesetz and other constitutional documents. For me it shows clearly that it is really time to take side of those fundamentals in a more energic way.

🐈‍⬛🐾

@LaF0rge hmm consider: employee might do contributions on company time, working on things important to said company. if the company is engaging in support of warcrimes or whatever, I think it is valid to restrict contributions from said employee.

Personally I don't want any company in the "defense" industry to do with anything in my software stack. I think their morals are rotten and I do not trust them to make decisions, as their objectives stray too far from my own.

LaF0rge

@maris what I fail to see is any evidence. Where is the public record that shows the detailed analysis for each of the removed entries? Like "Joe Doe is currently an employee of Evilcorp [as seen in this LinkedIn profile], the company is listed in this (linked) version of that embargo list". That could all go into the commit message of that one removal. Like it was done, it appears more like people having a mail.ru account were removed because they use that email provider...

🐈‍⬛🐾

@LaF0rge I definitely agree on the lack of transparency

Wilfried Klaebe

@maris On not wanting contributions from the "defense" industry: that will quickly devolve into a question of where to draw the line. Samsung builds tanks and firearms. "[T]he U.S. Army is the single largest installed base for Red Hat Linux". Would you exclude RedHat? Why/why not?

@LaF0rge

🐈‍⬛🐾

@wonka samsung is a conglomerate with multiple departments (some of which you probably should exclude), redhat is a huge consulting company with customers distributed in all sectors.
we should have discussions with all kind commercial influence in oss, though.

a company like Rheinmetall or anduril should definitely be excluded. no second thoughts.

Adrian Vovk

@LaF0rge The law makes no distinction between employees of banned companies working on their own time versus on company time. That's the legal basis of the move.

And frankly, I wouldn't want that distinction. The companies on the list are there for a reason: they're the ones building the tech used to commit the war crimes. The drones and missiles used run Linux. They can, b/c it's FOSS. But allowing the same people who make the weapons killing Ukrainians participate in our communities is on us.

LaF0rge

@AdrianVovk again I'm not seeing the chain of evidence in that commit. If I find something that violates a technical spec, then my commitlog would contain a reference to which specific section of which spec says what. Why not have the same level of commit log quality here? Why are we satisfied with "some undisclosed lawyer gave advice to do this" as follow up to an email thread...

penguin42

@LaF0rge @AdrianVovk At least if the lawyer wasn't allowing them to say it, then at least it could have said that, something like 'Our lawyers are telling us...but aren't allowing us to give details, we're working on it.' type of thing would have been much better.
I disagree with you over the companies/individual thing though - the mailmap translates between addresses, and when working for companies developers normally say - the copyrights they use are normally company not personal.

Adrian Vovk

@LaF0rge Yeah the announcement could have been handled better

Adrian Vovk

@LaF0rge Companies pay their employees to contribute to FOSS if and only if it benefits the companies in some way. Russian defense contractors don't contribute to Linux out of the goodness of their hearts. Letting them keep contributing means they keep benefiting

The people that work for these companies but contribute in their free time don't have my sympathy too. Their day job is still building the tools to kill innocent people, and if all that costs them is their hobby then they got off easy

LaF0rge

@AdrianVovk the freedom of FOSS is the freedom to use it for any purpose. I never really liked that, but licenses that would discriminate against certain use cases [like military] are neither compliant to free software definition nor open source definition. For decades that was the mantra.

Lars Marowsky-Brée 😷

@LaF0rge @AdrianVovk That is still the mantra and why they don't censor Palantir, Rheinmetall, Lockheed ...
The US and the EU are flexing their weight (not just when it comes to warmonger Russia), and organizations are legally required to comply and won't - can't, really - be publicly discussed.
And of course it's, in many ways, hypocritical. (And impacts individuals negatively at least, like all sanctions.)
But the OSS world can't escape Conway's Law.

LaF0rge

@larsmb @AdrianVovk do you have any references to laws that prevent the public debate about sanctions? Since when can we not debate and question or even challenge public policy?

Lars Marowsky-Brée 😷

@LaF0rge @AdrianVovk Sure, we can and should. But I don't see that as a decision the LF and its associates could have done any different, given that they're bound by law.
What I meant is that no business will publicly discuss their reasoning behind this. The legal departments would throw a fit.
I'd love for sanctions to have FLOSS exemptions, but I'm not sure how realistic that is.

Lars Marowsky-Brée 😷

@LaF0rge @AdrianVovk And very few orgs indeed will come clean with "well the government asked us to so we can continue to get their money".
Some countries (Australia, US?) have actual secrecy laws IIRC.

(I need to add a disclaimer here that this is my very personal take, not representative of or informed by my employer, where I'm not in the loop about such decisions anyway.)

LaF0rge

@larsmb @AdrianVovk In a better world, LF should exist to serve the Linux kernel development community, and not the other way around. And I guess it should rather be registered in Geneva, next to the ITU and other international organizations.

Adrian Vovk

@LaF0rge The freedom to use for any purpose is not the same as the freedom to participate in development.

CountZero

@AdrianVovk @LaF0rge

>Russian defense contractors don't contribute to Linux out of the goodness of their hearts

1. citation needed

2. can we stop this "defense contractor" bs? Baikal produced some MIPS and ARM-based SoCs for internal market, including SOHO segment. Russian MoD bought some of these, just like any other customer, and that's about it. *Real* Russian defense contractors operate under very strict NDAs and they would never ever make their efforts public. Let alone public for American NGO aka Linux Foundation, they'd be prosecuted for that.

3. this particular developer got his maintainer's status not for his Baikal upstreaming work but for volunteering work on projects unrelated to his employer and in his free time. This is pretty clearly described in his LKML post, which you apparently skipped (but decided to make judgements anyway)

@AdrianVovk @LaF0rge

>Russian defense contractors don't contribute to Linux out of the goodness of their hearts

1. citation needed

2. can we stop this "defense contractor" bs? Baikal produced some MIPS and ARM-based SoCs for internal market, including SOHO segment. Russian MoD bought some of these, just like any other customer, and that's about it. *Real* Russian defense contractors operate under very strict NDAs and they would never ever make their efforts public. Let alone public for American NGO...

Peter N. M. Hansteen

@czero @AdrianVovk @LaF0rge While individual contributors might decide to contribute to a free software project "out of the goodness of their heart", no commercial entity, whatever their business actually does. (defense or other sector, no matter)

Rather, they see the positive potential of utilizing the combined efforts of other developers as well as their own in maintaining and improving whatever it is they make their money from.

:neocat_scream: kittens!

@LaF0rge this is a symptom of corporate takeover of Linux. No sanctions target Linus or the foundation directly, but American companies seemingly want to avoid toxic association with sanctioned Russian companies.

The common people suffer when powerful people fight.

Hendi

@LaF0rge did you think about the protection this gives to russian maintainers? Russia might nudge or force those maintainers to do something for its hybrid, low level war. They are no longer a target for this.

:neocat_scream: kittens!

@dg3hda @LaF0rge "fun" fact: contributing to Linux is technically a crime in Russia

LaF0rge

@dg3hda I believe pretty much any intelligence service of any country has the power to "nudge" anyone either way - if they'd really want to. And who says that there aren't various "sleeper maintainers" under false English names and gmail.com email addresses in the MAINTAINERS file... I think this is all security theater.

Hendi

@LaF0rge well possible, but still not counteracting this protection.

Ronja

@LaF0rge I largely concur with your opinion, except for this bit:

“[…] passport, their employer or their place of residence”

Ignoring the whole Linux clusterfuck for a moment, why do you feel like employer should be a protected category?

My feelings: We must not discriminate against properties one can’t control. Usually who you work for is something you can control. If one works for a company I deem sus, why should I not extend that judgement to it’s employees that freely choose to associate?

LaF0rge

@ronya I don't really see how the employer matters *except* in cases where the maintained code is something that employer has instructed the developer to submit (like a device driver of a device made by said employer). Developers are not some kind of zombie/property/droid owned by their employer. I would find it an insult if I was reduced to that role/hat. Maybe it's different in today's corporate Linus world. When I grew up people were kernel hackers first, no matter who happened to employ them

Ronja

@LaF0rge In regard to the merits of their patches and this whole Linux compliance & complacency fuckup : Ack.

However, your blog sounds like you find it morally problematic to break ties with people based on their choice of employer. Why is that? Why should $community not say: "Your day job stands for something incompatible with our communities values. Hence, you are not welcome here, even though you have merit."

Is that really what you are saying, or am I misunderstanding that part?

Ronja

@LaF0rge FWIW: I work at Google, so there are plenty of chaos communities that would be happy to use such reasoning against myself ^^\

LaF0rge

@ronya I think a peoject/community could of course have such a policy / determination, yes. But then I didn't see any such decision-building or policy with some consensus before this incident. My apologies if I missed it. I also didn't see any reporting on adressing the affected developers.

MysticBasil 🇺🇦

@LaF0rge Should you as a German resident have been excluded from contributing to some tech project developed by the Allies, if it were 1942 now? Or vice versa, having some American resident excluded from his contribution to developing, e.g. Enigma machine, used by Germans? How about contributions from a murderer, ReiserFS anyone? It is not about someone’s past, the war is raging right now, for fucks sake! If morals mean nothing to you, at least consider security.

Go Up