| Thanks for pointing this out, I had forgotten this! Yeah, Red Hat has been rotten for a long time. I don't like it; I think it's been a terrible company for many years; but I do think it's never released non-free software, which was the bit I am mostly concerned about on this particular topic. I do agree that they have no real moral ground to stand on. Forgive me for pointing this out, but given they're one of the organizations that signed the letter... (Though they sort of have more casus belli to than most that signed the letter.) Seriously, though, thank you for pointing this out! I really genuinely appreciate it (and also appreciate that you're civil here). Ah, you stealth-edited; give me a second to read that one. > otherwise IBM and Google would never have had a seat. Google has never had a seat at anything other than OSI, and IBM only purchased one. > "If you work for a company that makes software that can kill people, your ethics don't line up with ours" hasn't been a principle either - Obviously didn't claim this. I pointed out Garrett worked for a proprietary software company that made proprietary software that kills people. Specifically, I noted that this was worse than normal proprietary software, because if you're going to have the lives of others in your hands, they should at least know the rulebook you're playing by. > RMS in fact has advocated for multiple militaries to use free software This is consistent with everything else I've said. I personally dislike militarized forces to the point of being skeptical of most veterans, but proprietary software doesn't make sense for a military any more than using American bombs would make sense for North Korea. |
I'm referencing the GCC steering committee - IBM (actual IBM, not just Red Hat, mostly because they support GCC on their mainframes) and Google (presumably for gold, gccgo, etc.) have been involved for many years. (I don't mean they have seats on the FSF board or anything, that may have been unclear. I just mean their employees have leadership positions in a flagship GNU project, and at least for those two employees, their involvement in GCC is even part of their day job.)
I see your point about proprietary software that has the risk of killing people when it goes wrong, but what I'm claiming is that this is a sensible first-principles argument that is being newly introduced. When Red Hat contracts for the US defense apparatus - their largest customer - they know full well they're supporting proprietary and classified code, whose intended purpose is killing people, running on RHEL. (And given that RHEL's business model is support, I would seriously doubt that they never see/access/work on the proprietary code - I would bet they have engineers with clearance to help out with that code.) I think you can make an equally-sensible first-principles argument that this, too, is incompatible with the principles of the free software movement.
But we haven't made that argument, and we've been fine with Red Hat for years, and we've been fine with IBM for years (who has customers that are so distasteful that they had to negotiate an exception for JSON's "This software shall be used for Good, not Evil" license :) ), etc. I'm actually super interested in having that discussion and seeing where it leads, because I think there hasn't been much discussion of free software ethics in the last many years. But I think we can't retroactively apply it to decide who really is able to be a voice for the free software movement and who isn't.