Chef Blog
blog.chef.io · Company blog · on HN since 2016
Chef's company blog about its DevOps automation software, open-source licensing, its acquisition by Progress, and its contract with ICE.
What HN saysHN 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.
22HN people shared it
7linked it in comments
15stories submitted
655story points
6 years agolast shared
2016people per year2026
Most-shared posts
- 1Chef CEO Defends Contract with ICE5 people · 75 points · first shared 2019 · 107 comments on HN
- 2Update from Chef2 people · 251 points · first shared 2019 · 259 comments on HN
- 3A Personal Message from the CTO2 people · 4 points · first shared 2019 · 1 comments on HN
- 4Chef to be acquired by Progress1 people · 169 points · first shared 2020 · 143 comments on HN
- 5Chef extends open-source licensing to all its software1 people · 119 points · first shared 2019 · 61 comments on HN
- 6No I won’t tell you what DevOps is. Tell me what you want to achieve instead1 people · 23 points · first shared 2016 · 10 comments on HN
- 7Habitat Builder Released1 people · 4 points · first shared 2017 · discussion on HN
- 8What DevOps Means to Me1 people · 3 points · first shared 2020 · discussion on HN
- 9Chef.io on ICE1 people · 3 points · first shared 2019 · 1 comments on HN
- 10Manage Secrets with Chef and HashiCorps Vault1 people · 1 points · first shared 2016 · discussion on HN
- 11United States immigration and professional work visas1 people · 1 points · first shared 2017 · discussion on HN
- 12Why “Why-Run” Mode in Chef Is Considered Harmful1 people · 1 points · first shared 2018 · 1 comments on HN
- 13Chef's Stance on Texas SB6 “Bathroom Bill”1 people · 1 points · first shared 2017 · discussion on HN
- 14Introducing developer certificate of origin1 people · first shared 2021
- 15The making of erchef the chef 11 server1 people · first shared 2019
What HN people wrote when they linked it
Boulth6 · 2021-04-12
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
input_sh · 2019-12-04
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/diff…
...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.
thiefmeister · 2019-09-24
They have some update. (looks like they are backtracking their original statement.)
https://blog.chef.io/2019/09/23/an-important-update-from-chef/
huntaub · 2019-09-20
The CEO of Chef responded to this with a blog post: https://blog.chef.io/2019/09/19/chefs-position-on-customer-engagement-…
montypythonxxx · 2019-09-20
Chef's official stance remains unchanged. Their blogpost: https://blog.chef.io/2019/09/19/chefs-position-on-customer-engagement-…
nofinator · 2019-09-20
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-…
StreamBright · 2019-04-28
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-serve…
Not sure what is up with Ruby nowadays. JRuby was always an interesting option though.