Can someone explain what the guy's action accomplished? If you yank your code from the internet, and people have backups of it, and it was under the Apache license, it seems to me that people can just restore the code and keep working with it as if nothing happened. The license is perpetual, no? And that's not just a technicality - if FOSS licenses were revocable by the author at any time, only idiots would use FOSS in their business...
He removed his repository because it was used by a company that he thinks it did something he disliked. I don't know why it matters, at least in the grand scheme of things. For him it probably matters due to his personal views and it'll probably matter for those who align with his views (assuming they know about that move).
In any case, anyone is free to do with their code whatever they like. If you depend on anyone else's code keep in mind that you do not have control over them and any expectations you may have about their actions may not match theirs, so take that into consideration when making those dependencies.
Seth is a big deal in the Chef community, so it's important to understand that. In fact, he's a big deal in the devops community.
What he did was make a statement. He made it clear to the Chef _company_ that he can not,non good conscience, contribute code to organizations that he feels are working with extremely bad actors. This is his way of protesting. Chef is able to (and in fact already has) ignored him and restored a copy of his code and formed it under a new name. (Citation needed but I believe that was a statement from Seth I'm Twitter.)
To everyone snubbing Seth for doing this, let's go "Nazi" with it. If Chef did a deal with the Aryan Nation and FOSS contributors pulled their core and support, would people feel the same? Probably not, right? Well, to many, what ICE is doing is _literally_ along the lines of what the Nazi party did. (I'm not asking that anyone agree with that sentiment, just that they acknowledge that it exists.)
So, Seth exercised his right to free speech and right to protest by publicly pulling support for an organization that he has helped significantly. This is a loss for the Chef org and the Chef community. It has also been quite effective because this isn't the first place where I've seen this conversation and it won't be the last, in the next few days.
It’s the only logical conclusion. Any other would result in inconsistencies and uneven application. One cannot continually evaluate and determine worthiness (as defined by you) of all users.
Moreover this program began under the Obama admin. So the decision itself is internally inconsistent.
Even more ironically, it comes from a Google employee, when Google is so much widespread, that it's guaranteed to be working with morally questionable actors left and right; or (according to many people) being /the/ morally questionable actor.
I originally thought so too, but based on the CEO's blog post, it sounds like they are more involved with ICE for this project than simply licensing their product to an independent contractor: https://blog.chef.io/2019/09/19/chefs-position-on-customer-e...
On this case, I don't think your Law requires children to be imprisoned away from their parents, nor that it requires that illegal immigrants be imprisoned instead of deported. If that is really the case, the blame falls entirely on the people enforcing it.
When my parents went to jail, I didnt go with them. There are obvious logical considerations both sides are ignoring here. While seperation is clearly not good, the alternatives may be worse in some cases, as they were mine.
> I apologize for the disruption to your workflow. I will be happy to restore the old repository and gem versions if Chef cancels their contract with the agency.
Great, take something out on me because of your personal politics!
I, for one, look forward to a future of navigating politicized open-source constraints of each creator.
And of course, the creator of Chef-Sugar works for Google.
I think it's reasonable whatever one's view. He made it. He can pull it. This is literally what this freedom is all about. I don't understand when the personal expression of developers of free software became constrained by some kind of nebulous corporate responsibility.
I suppose that would make it an empty gesture devoid of practical consequence then?
Looking through the commit history[0], he doesn't even look to be all that prolific as compared to other contributors. One would imagine those folks would keep on keeping on in some fashion.
That "day" never really existed; you always own the consequences of your actions, even if you choose to pretend you don't.
Seth, to his credit, is doing what he can about his. Legally, there isn't much. But if a minor inconvenience--and it is minor because Chef is already busily scrubbing his name from "chef-sugar-ng", including removing him from the cookbook's authors, they can get their replacement just fine--alerts members of the Chef community to their ratshit behavior, that's a positive. Because some, who do not hold amorality as a virtue as is en vogue in these parts, will probably take exception to it, too, and they should know.
You didn't pay for the software, so there is no service-level agreement. The software could be pulled at any time, for any reason, or no reason at all.
I contribute to FOSS, have a number of small projects ballpark of [1,000, 10,000) users. I guarantee I disagree with a non-trivial part of those folks, politically. I don't put in constraints to deny them because of that. That's the world I want to live in.
It is a bit ridiculous. Are people going to start pulling things from projects because they find out that FOSS is used heavily by the intelligence community?
If an author of a free software believes that it is against his own morals to indirectly assist some organization that they see as immoral then, yes, they have the freedom to stop working on that software as there is no obligation on their part to continue doing so.
I should have clarified my point a bit. I'm not debating ones prerogative to do it. But we as nerds know the things we make can and are used by "bad"* actors but typically say it's better for the common good so we should keep it. Things like encryption, heavy math libraries in the world of nuclear physics, rocket science, VPNs, etc.
So when we discover one bad person using our software and subsequently yank it, aren't we being a bit hypocritical?
* I quote that because not everyone agrees that DHS and ICE are bad actors and want to avoid a political tangent
YMMV, but to me there's a difference between directly creating financial benefit for the owners of a largely closed software ecosystem--and Chef in practice is a largely closed software ecosystem, it's single-source and they're doing their damnedest to squeeze money out of their users right now--and more general open-source publishing.
It's their prerogative to do that if they so choose. If you don't like it, don't rely on it. Get commercially licensed software where this can't happen or write your own.
> The license must not discriminate against any person or group of persons.
> 6. No Discrimination Against Fields of Endeavor
> The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
---
Being potentially used by organizations you don't agree with is what open source entails.
There also appears to be nothing wrong in the FOSS model of taking the last published version and forking it... and releasing that.
A FOSS license allows an organization you dislike to continue using your software, but it doesn't require that you continue working on and providing that software on any specific way (there is the requirement in GPL to provide on request for a limited amount of time but it doesn't specify method and that can be done via - e.g. - email).
Others can pick it up from where you left and continue, of course.
In this case probably that the author removed all files from the repository. But if someone finds a copy: Nothing. It was (as far as I can gather) under an open-source license and people continue to have all the rights associated with that.
This is ridiculous. It’s unsustainable. There is no way you can audit all your users to determine how law abiding, ethical, moral and whatever other measure you want to use.
It’s a bit of immature posturing.
If I need something and I can’t buy it directly I’ll go to a third party who will buy it for me. So it’s kind of futile anyway.
Imagine if Bernie wins and then everyone who doesn’t like socialized medicine (physicians, etc., go on strike — oh, my bad, they wouldn’t be allowed). Or big pharma said, we’re not selling to government, they are telling us to depress prices, we disagree!
> Or big pharma said, we’re not selling to government, they are telling us to depress prices, we disagree!
Big pharma has said this many times to many governments. When Brazil started to negotiate, we had to invalidate patents so somebody would sell the drugs.
The pharma industries were acting like perfect assholes, denying their product to people that need it for strong-arming them into unreasonable prices. But that's entirely dependent on the details, they could be as well just be negotiating a fair price and the description above wouldn't change a bit.
The government was well within its right to invalidate the patents for protecting its people. That again is dependent on the details, it could be an antieconomical action against the freedom of initiative and still have the same description. The fact that those same pharma companies currently get more profit than they did at the time, by selling a much larger amount of medicine (for a lower unitary price) is strong evidence that the government was right.
Moral of the story: do not do business with Google because you can’t tell when some random employee of theirs will decide to pull the plug on you. Or maybe you’re just collateral damage in their country’s internal political squabbles. Either way you have no recourse, because Google.