Chef's company blog about its DevOps automation software, open-source licensing, its acquisition by Progress, and its contract with ICE.
HN links it mainly for the 2019 controversy over Chef's ICE contract, citing the CEO's position post and a later update backing off the stance.
As far as I know, not quite.
GitLab modified their customer acceptance so that it gives them an option to refuse a client, saying that they will reach such a decision on a case-by-case basis: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/32614/diffs
...while Chef's CEO openly said that they will not renew their contract with ICE and CBP, as well as to donate the equivalent revenue of their current contracts to charities that help people impacted: https://blog.chef.io/an-important-update-from-chef/
> After deep introspection and dialog within Chef, we will not renew our current contracts with ICE and CBP when they expire over the next year. Chef will fulfill our full obligations under the current contracts.
Well, Rails does not have a good track record with scaling. Memory requirements if nothing else will be a big hurdle to come by regardless if you have SOA, in my experience.
Back in the day not many organizations survived on Ruby/Rails and many of them moved over to Erlang or Java just to deal with resource issues.
https://blog.chef.io/2013/02/15/the-making-of-erchef-the-chef-11-server/
Not sure what is up with Ruby nowadays. JRuby was always an interesting option though.
Indeed that is likely but I wonder why didn't they at least require a Developer's Cerificate of Origin [0] that kernel.org uses. This is really lightweight (just append one line to git commit message) and supposedly provides a minimum legal base for the change. IANAL.
[0]: https://blog.chef.io/introducing-developer-certificate-of-origin
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-engagement-in-the-public-and-private-sectors/
Chef's official stance remains unchanged. Their blogpost: https://blog.chef.io/2019/09/19/chefs-position-on-customer-engagement-in-the-public-and-private-sectors
The CEO of Chef responded to this with a blog post: https://blog.chef.io/2019/09/19/chefs-position-on-customer-engagement-in-the-public-and-private-sectors